A working policy URL
Both stores reject a submission without a reachable privacy policy. The page has to stay up, and what it says has to match what your app actually collects.
Answer a short questionnaire and get a Privacy Policy and Terms of Service in eight languages, published on your own domain with HTTPS. Everything the App Store and Google Play ask for, in one link.
No credit card. Your page is online the moment you publish.
Every app needs the same three things. Writing them from scratch takes days, and copying someone else's policy describes their app — not yours.
Both stores reject a submission without a reachable privacy policy. The page has to stay up, and what it says has to match what your app actually collects.
A template written for a different product is worse than none: it promises things your app doesn't do and stays silent about what it does.
A gist or a shared doc works until it doesn't — no HTTPS on your domain, no version history, no way to show what the policy said last month.
Documents, a landing page, your domain and analytics — one panel, one flow.
Answer plain questions about what your app collects. The wording, the sections and the regulations follow from your answers — you never draft legal text.
Every app gets a page with your name, icon, description and store links — in your colours, your logo and your font. Not a template with a logo pasted on.
You start on yourapp.legalpage.site and can connect yourapp.com whenever you like. Certificates are issued and renewed automatically.
One publish generates the documents and the whole site in eight languages. A visitor from Berlin reads German; search engines are told about every other version.
Every publish is kept. See exactly what the document said last month, and restore any earlier version across all languages at once.
Page views, visitors and countries — counted without cookies and without storing IP addresses, so this page needs no consent banner of its own.
Name, icon, platform and store links. That is your landing page finished.
About twenty questions: what you collect, which SDKs you use, whether you show ads. Preview the document as you answer.
Your page goes live on your subdomain. Copy the URL into App Store Connect and Play Console and carry on building.
Not a shared page with your name on it. Every app renders with its own colours, logo and font, on its own address.
The documents are generated in every language at once, so a visitor who opens /es/privacy reads Spanish rather than a translated-looking English page. Each version is linked with hreflang, so all of them get indexed.
You see how many people read your policy and where they came from. We do it without following anyone around.
No. LegalPage fills a reviewed template using your answers, and every document says so at the bottom. If you operate in a regulated market or handle children's or health data, have a lawyer read it before you publish.
The document covers what both stores ask about: what you collect, why, who you share it with, how long you keep it and how a user can reach you. You paste the link into App Store Connect and Play Console like any other policy URL.
Yes. Add one CNAME and one TXT record, and the certificate is issued for you. Until then your page lives at yourapp., which works just as well for store review.
Publishing creates a new version and keeps the previous one. The page shows the date it was last updated, and you can restore an earlier version in every language at once.
No. Page views are counted with a hash of the request that is thrown away daily, so nobody can be followed between days and no IP address is stored.
Nothing while we are in beta. If paid plans arrive later, everything you have already published keeps working.
LegalPage generates documents from a template — it is not a law firm and the result is not legal advice. Have your documents reviewed before you rely on them.