Support, privacy and terms are not afterthoughts. App stores ask for them, and users look for them the moment something goes wrong.
When you submit an app to the App Store you are asked for a privacy policy URL and a support URL. Many teams scramble for these at the last minute and end up linking to a bare email address or a generic page.
What we put on every app page
- Support: answers to common questions first, then a clear way to reach a person.
- Privacy: what the app stores, where it is kept and how to delete it.
- Terms: the rules for using the app, in plain English.
- Contact: a real address for bugs, ideas and questions.
For apps that have their own website, these pages live there. For apps that do not, they live on ours, at addresses that never change, because the store listing and the app itself both link to them.
Write them from the code, not from a template
A privacy policy should describe what the app actually does. We write ours by reading the code: which data is stored, which services it talks to, what happens when you delete your account. If the app changes, the policy changes in the same pull request.
The best support page is the one someone finds before they need to email you.