AppForShareCreate a free account

Privacy policy, support and account deletion pages, written from your build

Pro for one app. Team for every app, on your custom domain

The App Store asks for a privacy policy URL and a support URL. Google Play asks for a privacy policy and, for apps where people make an account, a way to ask for deletion. Many small teams end up writing these at the last minute on a page that does not match what the app collects.

Store pages give each connected app three plain pages. A form is prefilled from your newest build: permissions in plain words, your iOS usage reasons and the services we recognise in it. You check the answers, publish, and the listing editor puts the addresses in.

Example

Store pages, Shop for iOS and Android

  • Privacy policyappforshare.io/p/shop-x7k2/privacy, published
  • Supportappforshare.io/p/shop-x7k2/support, published
  • Account deletionDraft, not published yet
An AI draft is a draft: review it with your own advisor.

Made for

  • Solo developers and small teams publishing their first app
  • Agencies that ship apps for clients who have no website
  • Teams whose privacy page has fallen behind the app

What it ends

  • A privacy page written once and never matched to the app again
  • No support page, so the support URL points at a home page
  • A rushed account deletion page the week of a Play review

How it works

  1. Step 1

    Answer the form

    Developer, contact email, website, country, the kinds of data the app collects and why, other companies' services, retention, children under 13, deletion steps and support answer time. Permissions, iOS reasons and about 25 recognised SDKs, such as Firebase Analytics, Crashlytics, AdMob, OneSignal, Sentry and RevenueCat, come prefilled from the newest build.

  2. Step 2

    Draft and publish

    Our templates write the pages from your answers. You can ask AI for a privacy text draft (1 AI action), or use your own plain text. The public pages change only when an Owner or Admin presses Publish.

  3. Step 3

    Fill in the listing

    In the listing editor, "Use my store pages" fills the support and privacy policy URLs of every App Store language in one click. For Google Play it fills the Website field and shows the privacy and deletion addresses to paste in Play Console, App content.

Written from your answers and your build

The pages say what you tell us and what the build shows: each permission with your reason, the data kinds you pick, the services in the build and how a person asks for deletion. The form is prefilled from the newest build of the app each time you open it.

The AI draft is labelled "a draft, review it with your own advisor". Sentences that claim compliance or store approval are removed from it, and it is never published on its own.

Plans and the address

Pro covers one app: one bundle ID, so its App Store and Google Play app count once. Team covers every connected app, and serves the pages on your custom domain when it is live. Pages are not indexed by search engines and carry no AppForShare chat.

If the plan stops covering a page, it stays up 30 days, you get one email with the date, then it stops answering; it comes back with the plan. From the CLI, appforshare store-pages lists and publishes them; the MCP tool get_store_pages reads them.

Good to know

Questions

Which apps can have store pages?
Apps of a connected App Store Connect or Google Play account. Pro covers one app, Team every app.
Can I write my own privacy policy?
Yes. Use your own plain text with headings and lists instead of the template; HTML is not accepted.
Does Google Play read the URLs automatically?
The Play API does not set the privacy policy or deletion URLs, so the listing editor shows them for you to paste in Play Console, App content.
Is this legal advice?
No. Review the pages, and the AI draft in particular, with your own advisor.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

More features