App Store · Google Play
The privacy policy URL your app store asks for
Both stores ask for a link to a privacy policy, and both check that it opens. This is what the field wants, why submissions fail on it, and how to have a working address in a few minutes.
What the field actually wants
A public web address that returns your privacy policy to anyone who opens it. No login, no cookie wall, no PDF download, no redirect to a page that asks for an account. Apple guideline 5.1.1 asks for the link in App Store Connect AND inside the app itself, which is the half people miss; Google shows it on your store listing. It has to keep working after the app ships, because the listing keeps pointing at it.
Why submissions fail on it
Almost always for a reason that has nothing to do with the wording: the link 404s, it points at a page behind a login, it was a Google Doc whose sharing changed, or it lives on a domain that expired. A reviewer who cannot open the page does not read the policy — they reject the build.
Where to host it
Anywhere that gives you a stable public URL you control. A page inside your own marketing site works. What does not work well is a document-sharing link, a note-taking app, or a free host that puts an interstitial in front of the page — all three are common causes of a rejected link.
Keeping it true after you ship
A privacy policy describes what your app does with data, so it stops being accurate the moment the app changes: a new analytics SDK, a new login provider, a new AI feature — which needs its own disclosure and consent step, not a line added to this one. The URL staying up is the easy half. The hard half is remembering to update what is behind it, which is why it is worth having somewhere you can edit in one place rather than in a file you have to redeploy.
Before you submit
- The URL opens in a private browser window, with no account and no app installed.
- It returns a page, not a download.
- It names what data your app collects and why, in your own words.
- It gives a way to contact you.
- It is the same address you can keep for the life of the app.
Questions
- Can I use the same privacy policy for two apps?
- You can reuse the wording, but the policy has to describe the app it is linked from. Two apps that collect different data need two policies, and giving each its own URL also keeps a change to one from silently changing the other.
- Does it need to be in every language my app supports?
- The stores ask for a working URL, not for translations. A visitor who reads the policy in a language they do not speak is served badly, though, so translating it is worth doing where a market matters to you.
- Is a generated policy enough?
- A template gives you a structure and reminds you of sections people forget. Whether the result is right for your app, your jurisdiction and what you actually do with data is a question only you, or a lawyer, can answer. We are not a law firm and this is not legal advice.
Get a privacy policy URL in minutes
Publish one app free, with a stable address you can keep and edit whenever the app changes.
Free. No card.
We help you publish and maintain your legal and support pages. We are not a law firm and we do not guarantee regulatory compliance.