AppFoyer: the compliance pages every app store asks for

Building the app is the part you wanted to do. Then the store asks for a privacy policy URL, a support URL, an account deletion URL, and — if you show ads — an app-ads.txt file on a domain you control. None of that is why you started, and none of it can be skipped.

AppFoyer exists for exactly that gap. It gives a mobile app a hosted, store-compliant website — home, privacy policy, terms, support, account deletion and app-ads.txt — without you owning a domain, running a server, or writing a backend.

We built it for our own dictionary apps first. Around 110 Android builds and an iOS app, each needing the same handful of pages, each needing them again whenever a store changed its mind.

Where a website is actually required

It is easy to assume a small app does not need a site. The store review queue disagrees, in specific places:

• Google Play requires a privacy policy URL for every app, and a reachable account deletion URL for any app with accounts — the page must be findable from outside the app, not only from a buried settings screen.
• Apple App Store requires a privacy policy URL on every listing and a support URL that resolves to a real page. A blank page or a dead link is a rejection.
• Ad networks — AdMob, AppLovin, Unity and the rest — read app-ads.txt from the developer website in your store listing. Get it wrong and your inventory quietly loses authorized-seller status, which shows up as lost revenue, not as an error message.

Every one of these is a URL. Not a landing page, not a brand, not a marketing site — a URL that returns a real page when a reviewer or a crawler asks for it.

What you get

Five pages and an ad file, each one written for what the stores actually check:

• Privacy policy — generated from your app's real SDK list. The editor asks which analytics, ad and crash-reporting SDKs you use, and the built-in checklist keeps flagging the page until every placeholder is replaced with something true.
• Terms of service — a plain template covering use of the app, purchases and liability. Apple's standard EULA is linked when your app sells anything.
• Support page — the support URL both stores ask for: your contact address and the basics reviewers look for.
• Account deletion — the page Google Play requires. A user submits a request, AppFoyer records it and notifies you. You perform the deletion in your own systems; AppFoyer never touches your users' data and never claims to have deleted anything on your behalf.
• app-ads.txt — presets for AdMob, AppLovin, Unity and others, with line-by-line validation. Served as plain text with no redirect, which is what the crawlers require.

Alongside them, a compliance checklist that tells you what is still missing and why a given store wants it, so "am I done?" has an answer other than resubmitting and hoping.

Two ways to get there

If you use Claude Code, install the AppFoyer plugin and say "make this app store-ready." The agent reads your actual codebase — your manifest, your dependency list, your SDKs — and drafts every page from what it finds. You review, correct anything it got wrong, and publish.

If you would rather not, the web form takes six fields and gives you a live URL. Same pages, same checklist.

Either way the pages are yours to edit afterwards. Nothing is locked behind the agent.

What it costs

There is a free plan, and the important part is what is not on it: nothing a store requires sits behind a paywall. Every page above, the checklist and app-ads.txt are all on the free plan. It covers one published app and email notifications, which is the whole job for a developer with one app in the store. Signing up takes an email address — no card.

Above it are Pro and Advanced. They sell scale, not compliance: more published apps, a custom subdomain of your choosing instead of a generated one, and Telegram and Slack alongside email for deletion notifications. If you ship one app, the free plan is not a trial — it is the product. See appfoyer.com/pricing for the current plans.

One honest caveat

AppFoyer generates documents from templates and from what you tell it about your app. That is not legal advice, and it does not pretend to be. If your app handles health data, children's data, payments, or anything else with its own rulebook, have a lawyer read what you publish. What the tool removes is the blank page, the hosting, and the question of which URL goes in which store field — not your responsibility for what the page says.

Try it

If you have an app waiting on a privacy policy URL, it is a few minutes of work: appfoyer.com. There is also a product tour if you want to see the dashboard before signing up.