How to add a privacy policy — step by step, including the AI clause

A privacy policy looks like a formality you copy from a neighbour. Then your app gets rejected in review, and it turns out the copy described somebody else's services while your AI provider isn't named anywhere.
Apple now spells this out in its own line: disclose where personal data is shared with third parties, "including with third-party AI", and get explicit permission first. So if your app sends user text to a model, that has to be said in words.
Six steps below, after which you'll have your own policy instead of someone else's.
Step 1. List what you actually collect
Not from memory — from the facts. Open three places:
- your database tables — which fields get filled with real people's data;
- third-party scripts on the page — analytics, support chat, maps, fonts;
- server logs — IPs and user agents are almost always sitting there.
Write one "why" next to each item. Anything with no answer, delete right now. It's the cheapest way to halve your future policy. What counts as personal data in the first place: what is personal data.
Step 2. Write down everyone the data travels to
Every external service that sees user data has to be named. A typical small project:
- hosting and database;
- analytics;
- email sending;
- payments;
- your AI provider — if you forward the user's text, files or voice to it.
Number five is the one people forget, and it's exactly what app stores now look for. Be concrete: "the text of your message is sent to our AI provider to generate a reply; under our plan the provider does not use it to train models" — and only if that's true for your plan. Check the provider's docs: consumer chat and API have different rules.
Step 3. Write the six mandatory blocks
GDPR Article 13 lists what a person must learn at the moment you take their data. It's a convenient skeleton — it covers most other regimes too:
- who you are — a name and a contact;
- why — the purposes, and the legal basis you're relying on;
- who you share with — the categories of recipients, your list from step 2;
- whether data leaves the country — if your hosting or AI provider is abroad, say so;
- how long you keep it — a period, or the rule that determines it;
- what rights the person has — access, correction, deletion, portability, withdrawing consent and complaining to a regulator.
Write it in your own words and keep it short. Two screens someone will actually read beat ten pages of template nobody opens.
Step 4. Give it a permanent address
The policy needs a URL that doesn't change and opens without a login: example.com/privacy. Not a PDF in cloud storage, not a Notion page, not a screenshot.
Boring requirement, practical reason: other people will link to it — the app store, the payment provider, your emails. If the link moves, everyone's mandatory item breaks at once.
Step 5. Put the link where people look
- On the site — in the footer on every page, and next to any form that asks for data.
- In an iOS app — Apple wants the link both in the App Store Connect field and inside the app in an easily accessible place. Usually "About" or "Settings".
- On Google Play — a link in the listing and in the app is required if your app touches sensitive data or targets children. In practice it's simpler to always have it.
- In the sign-up form — as a link next to the button, not grey small print at the bottom.
Step 6. Add a date and an update rule
Put "Last updated 25 August 2026" at the bottom. Then the rule is simple: you connect a new service, you update the policy the same day. Added an AI feature, swapped analytics, started taking payments — all triggers.
What you end up with
A /privacy page where someone finds, in a minute: who you are, what you take, why, who you pass it to, how long you keep it and how to delete it. The link sits in the site footer, in the store listing and inside the app. And you can honestly answer a reviewer asking where the user's data goes.
The one mistake that voids all of it
Copying someone else's policy wholesale. You get a document listing services you don't have and staying silent about the ones you do.
That's dangerous from both ends. A store reviewer compares the policy against the app's actual behaviour — a mismatch shows immediately. And for a user, a gap between promise and fact is worse than no promise: a promise can be held against you.
Use someone else's document as a table of contents, and fill the content from your own steps 1 and 2. While you're at it, run the pre-launch security checklist: your policy promises the data is protected — let that be true.
Can I use a policy generator?
As a draft, yes — it won't forget a section. But you'll paste in your own service list from step 2 by hand: no generator knows which AI provider you wired up or what you send it.
Does a one-form landing page need a policy?
If the form collects an email, yes. Collection has begun, so you need both a basis and a notice to the person. GDPR and most national laws agree here: the document must be published and reachable.
What do I write for retention if I don't know?
Write a rule, not a number: "while you have an account, plus 30 days after deletion in case you want it back". That's more honest than a made-up "5 years" and easier to actually follow.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





