App privacy policiesContracts & Legal Documents

Privacy policy template for a mobile app

Usually ready in 15 minutesRevisions includedQuality check
Packages
Payment protectionDetails
  • Revisions within the package are free.
  • If you do not respond within 3 days of delivery, the work is accepted automatically.

The money is reserved when you pay and released only once you accept the work.

Privacy policy template for a mobile app

Example result

Example for the Standard package

Privacy policy for a walking challenge app

What the app collects (checked with the developer)

DataWhyShared with
EmailAccount and loginNobody
Step countChallenges and leaderboardsNobody; read from Apple Health / Health Connect only with permission
Push tokenRemindersFirebase Cloud Messaging
Crash reportsFixing bugsFirebase Crashlytics

No ads, no location, no selling of data.

Policy outline

  1. Who we are and how to contact us
  2. What we collect and why (the table above)
  3. Health data: used only inside the app, never for advertising
  4. How long we keep data: deleted 30 days after the account is closed
  5. Your rights (GDPR for the EU, CCPA for California)
  6. Children: the app is for users 13 and older (16 in some EU countries)
  7. Changes to this policy

Excerpt

Health data. With your permission, StepQuest reads your daily step count from Apple Health or Health Connect. We use it only to show your progress in challenges. We never use health data for advertising and never share it with third parties.

Notes

  • Answers for the App Store privacy labels and the Google Play Data safety form match the policy word for word
  • A template, not legal advice: review by a lawyer is recommended before launch

Delivered

The policy in English as a web page and in-app text, plus the filled store forms.

Client: StepQuest, a walking challenge app for iOS and Android with users in the EU and the US Task: a clear privacy policy that matches what the app really collects and the store privacy forms

The client and all details are made up.

About this service

App stores ask for a privacy policy link before your app goes live, and reviewers compare it with the permissions and SDKs the app uses. We write a policy that covers what an app typically touches: device identifiers, location, camera and contacts permissions, push tokens, crash reporting, ad networks and in-app purchases. The text also explains how users can delete their account and data, which both Apple and Google now expect.

What is included

  • What you getA privacy policy for your app as text you can host on a web page and link in App Store Connect or Google Play Console, with a checklist for the store data forms. You also get it as a Word (.docx) file. It is a template, not legal advice: have a lawyer check it for your country before release.
  • Permissions explainedLocation, camera, contacts, notifications
  • SDKs and partnersAnalytics, ads and crash tools named
  • Account deletionHow users remove their data
  • Children and ageAn age section if kids may use the app
  • Store form checklistPoints to match in the store data forms

How it works

  1. 1
    BriefYou list permissions and SDKs
  2. 2
    DraftingWe write the policy around your app
  3. 3
    DeliveryYou get the text and the store checklist

What we need from you

The app name and developer, platforms, the permissions it requests, the SDKs inside (analytics, ads, crash reporting, payments) and whether users create accounts.

We will ask you:

  • Which permissions does the app request?
  • Which SDKs or services are built in?
  • Do users sign up, and can children use the app?

Compare packages

PackagesBasic$15Standard$35Premium$69
What is includedApp privacy policy up to 3 pagesPolicy with deletion and consent textsDetailed policy with clause notes
Deadline1 day2 days3 days
Revisions123
Documents1 app privacy policyPolicy, deletion steps, consent linesPolicy, deletion steps, consent lines
Lengthup to 3 pagesup to 6 pagesup to 10 pages
Review checklistYesYesYes
Clause notesNoNoYes
Order BasicOrder StandardOrder Premium

Payment protection

You pay when you order, but the money is released only for accepted work.

  • Fixed priceThe package price does not change after you pay.
  • The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
  • Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
  • Free revisionsAsk for changes within your brief as many times as the package allows.
  • Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
  • Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
How it works →

Questions and answers

Can I use one policy for iOS and Android?

Yes, if the app collects the same data on both. If an SDK runs on one platform only, we say so in the text.

Will this get my app approved?

The policy removes a common reason for rejection, but review also checks your data forms, permissions prompts and the app itself, which we cannot control.

Where do I put the policy?

On any public web page, even a simple one, then add that link in the store listing and inside the app settings.

Did not find your answer?

Packages