What privacy policy and terms do you need before launching an AI-built app?
Short answer: Before you take sign-ups or payments, you need two pages: a privacy policy that lists the personal data your app collects, who else touches it, where it is stored and how people can have it deleted, and terms of service that set the rules for using the app. An AI-built app usually sends data to more companies than its owner realises (an AI model provider, a database host, a payment processor, an email sender), and every one of them belongs in the privacy policy. This is practical information, not legal advice: have a lawyer read the final pages if you handle payments, health, children's data or customers in the EU.
You are about to put real sign-ups or payments on an app an AI tool helped you build, and you want to know which legal pages you need and what to put in them.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The short version: write the privacy policy from a list of facts about your actual app, not from a generic template. Most of the pages that rank for this search are generator tools that ask you a few questions and produce standard text. That text will not know that your app sends customer messages to an AI model, or that your database sits in a particular region. Those are the lines that go wrong, so this article gives you the list of facts first and the template second. For the wider launch picture, see whether a vibe-coded app is production ready.
Which pages you need, and when
| Page | What it does | When you need it |
|---|---|---|
| Privacy policy | Tells people what data you collect, why, who gets it, how long you keep it and how to delete it | Before anyone signs up or enters any personal data. App stores also require it. |
| Terms of service | The rules for using the app, what you promise, what you do not, how accounts can be closed | Before sign-ups, and before payments |
| Refund and cancellation terms | What happens when someone stops paying | Before taking payments. Often a section of the terms. |
| Cookie notice | Explains tracking tools in the browser | If you use analytics or ad tracking. See is website visitor tracking allowed under privacy law. |
| AI use note | Says which AI providers see user data | Any time user content goes to an AI model. Put it inside the privacy policy. |
The terms are your protection. The privacy policy is a promise. That difference matters, because the US Federal Trade Commission (FTC), the national consumer protection regulator, says companies must keep the privacy promises they make, and a policy that says one thing while the app does another is the real risk. A short, accurate policy beats a long one that does not match your app.
What the rules actually ask for
I am not a lawyer, so here is what official sources say, in plain words.
- Apple App Store. Apple's review guidelines say every app must link to its privacy policy in App Store Connect and inside the app. The policy must say what data the app collects, how it collects it and all uses of it, confirm that third parties get the same protection, and explain retention, deletion and how a user can withdraw consent. If the app lets people create an account, it must also let them delete the account inside the app. Apple also says you must clearly disclose when personal data goes to third-party AI and get explicit permission first. If you are heading to the store, read what to do when an AI-built app is rejected by the App Store.
- Google Play. Google requires a privacy policy link in Play Console and in the app, hosted at a public web address (not a PDF), with developer contact details. Even apps that handle no personal data need one. Play also has a Data safety form that you must fill in accurately and keep consistent with the policy.
- EU and UK (GDPR). GDPR is the European data protection law. Article 13 lists what you must tell people when you collect their data: who you are, why you collect it and your legal basis, who receives it, whether it leaves the EU and under what safeguards, how long you keep it, their rights to access, correct, delete and move their data, their right to complain to a regulator, and any automated decision-making. It applies if you offer your app to people in the EU, wherever you are based.
- Children. In the US, the FTC's COPPA Rule covers apps directed at children under 13, and general apps that know they are collecting data from under-13s. It requires a clear privacy policy and verifiable parental consent. If kids are a possible audience, ask a lawyer before launch.
Other US states have their own privacy laws, and some require specific wording or opt-out links once you pass certain user numbers. If you serve customers in a particular state or country, check that regulator's page or ask a lawyer.
The facts an AI-built app must disclose
Go through this list before you write a single sentence. Each item is a question about your real app.
- What personal data do you collect? Name, email, password, phone, address, payment details, files, messages, location. Check the sign-up form and every other form in the app.
- Which AI providers receive user data? If the app calls an AI model through an API (the connection software uses to send requests to a service), user text may leave your app. OpenAI, which makes ChatGPT and sells API access to its models, says on its developer pages that API data is not used to train its models by default and that abuse-monitoring logs are kept for up to 30 days. Other providers have different terms. Read your provider's data page and repeat what it says. Do not guess.
- Where is the database, and who hosts it? Many AI builders store data in Supabase, a hosted database service. Supabase's documentation says the region you choose decides where your primary project data is stored, and lets you pick a region such as Europe. Name the host and the region in your policy. If your app was built by an AI tool, open the project settings and look. Do not assume.
- Who takes payments? Stripe, a payment processor that handles card details so you never store them, is common. Say that payments are handled by the processor and that you do not store full card numbers. This is true only if you truly never see them, so check your code.
- Which email or messaging service sends your messages? Name the category and the company.
- Which analytics, error-tracking or advertising tools run in the app? Each one is another recipient of data.
- Sign-in method. If people log in with Google or Apple, the policy should say so.
- How long do you keep data, and how does someone delete it? Pick a real answer: for example, deleted on request within 30 days. Then build the delete button or the email process so that it works.
- Selling or sharing data for advertising. For most small apps this does not happen. Say so only if it is true.
- Who is the company, and how do people contact you? A real name, address if required, and a monitored email.
If answering these takes you more than an hour, that is a finding by itself: the app is more complicated than you thought. A security checklist will surface the same gaps from the other side.
A fill-in privacy policy template
Copy this structure, replace the brackets with your real answers, and delete anything that does not apply. Keep the sentences short.
1. Who we are [Company legal name] runs [app name]. Contact us at [monitored email]. 2. What we collect We collect: [list from fact 1]. We collect it when you [sign up / pay / upload / message us]. 3. Why we use it We use your data to [run your account / process payments / send receipts and support replies / improve the app]. [EU users: our legal basis for each is contract, legitimate interest or consent.] 4. Who else handles your data - [Database host], stores app data in [region]. - [Payment processor], handles payments. We do not store full card numbers. - [Email service], sends our emails. - [AI provider], receives [the text you submit to the AI feature] to produce results. [Whether the provider trains on it, per its own terms.] - [Analytics tool], measures how the app is used. 5. International transfers Your data may be processed in [countries]. [Safeguards, if you serve the EU or UK.] 6. How long we keep it [Retention period for each type of data.] 7. Your choices and rights You can ask to see, correct, export or delete your data by [button or email]. We reply within [timeframe]. [EU and UK users may also complain to their data protection regulator.] 8. Children [App] is not for children under [13 or 16]. We do not knowingly collect their data. 9. Changes We will update the date below and tell you about material changes by [email or in-app notice]. Last updated: [date]
Section 4 is where AI-built apps fail. Fill it in from the real project settings and code, not from memory.
Terms of service essentials
Terms can be short. Cover these points:
- Who can use the app and the minimum age.
- Accounts: people keep their login private and you may suspend accounts that break the rules.
- What users own: they keep ownership of what they upload, and give you permission to store and process it to run the service.
- Acceptable use: no illegal content, no attacking the app.
- Payments: price, billing period, renewal, cancellation and refunds, spelled out the same way your checkout says them.
- AI output: if the app produces AI-written results, say they can be wrong and the user should check them before relying on them.
- Limits on your liability and which place's law applies. This is the part to ask a lawyer about.
- How you end the relationship: how a user can leave and what happens to their data afterward.
Terms only help if people actually agree to them. Use a tick box or a button that clearly says the person accepts, and keep a record of when. See how to make customers accept your terms with a checkbox for the setup.
The legal side of a launch checklist
- Privacy policy written from the facts list, live at its own web address, linked in the sign-up screen, the footer and (for stores) the store listing.
- Terms of service live and accepted with a recorded tick box before account creation.
- Delete-my-account works from inside the app, and a deletion request actually removes the data.
- Every third party in the app is in section 4 of the policy. Open the project and count them.
- The policy matches the app: same data, same providers, same retention. Re-check after every new feature.
- Refund and cancellation wording in the terms matches the payment page.
- If you serve the EU or UK: legal basis chosen, data location stated, a contact for rights requests.
- If children could use it: lawyer reviewed, or the app clearly excludes them.
- A named person checks the privacy inbox.
- Technical go-live items are done too: moving the app to production and putting it online under your own domain.
Mistakes I see most
- Pasting a generator's text without editing section 4. The policy then says nothing about the AI provider or the database.
- Promising what the app does not do. Writing "we never share your data" while an analytics tool and an AI model both receive it.
- No working delete path. The policy says users can delete their data, but nobody built the way to do it.
- Copying a competitor's policy. It describes their app, not yours.
- Forgetting your own team. If a staff member pastes customer details into a public AI chat, that is a separate risk. An AI usage policy covers it.
What it costs
A generator subscription is cheap. A lawyer's review of two short documents costs more, but it is a one-off. Price depends on your country and the lawyer, so ask for a fixed quote for reviewing two documents against your facts list. The legal pages are a small share of the cost of building and launching an app. For the full picture, see what an AI app costs to develop.
How I'd approach this
I would do the facts list first, because it takes under an hour and it is the part nobody else can do for you. Then I would use a generator or the template above for the wording, edit section 4 by hand, and pay a lawyer for a short review if the app takes payments, serves the EU, or could be used by children. I would not launch with a policy that I cannot match to the app line by line.
If you have an AI-built app that needs the legal pages, the security checks and the technical launch steps done together, that is what a Go-Live Plan Audit is for: it checks what stands between your app and real users and gives you the list. Blur Studio fixes and finishes start around $1,500, if the audit shows the app needs work.
Questions people ask
Do I need a privacy policy if my app is free?
Yes, if it collects any personal data, even an email address. Apple and Google both require a privacy policy link for store apps, and Google says even apps that handle no personal data need one. Free does not remove the duty.
Can I use a free privacy policy generator for my AI-built app?
You can use one for the structure, but it will not know which AI provider, database host or payment tool your app uses. Edit the section on third parties by hand from your real project, and ask a lawyer to check it if you take payments or serve the EU. See the template above.
Do I need to mention the AI tools my app uses?
Yes, if user data goes to them. Apple's guidelines say you must clearly disclose when personal data is shared with third-party AI and get explicit permission first. Name the provider, say what data it receives, and repeat what the provider says about training and retention. For your own team's use of AI tools, see the AI usage policy template.
Does GDPR apply to a small app outside Europe?
It can. GDPR applies when you offer your app to people in the EU, wherever you are based. Article 13 lists what you must tell them, including data location, retention and their rights. Check the official text or ask a lawyer about your case.
Do I need terms of service as well as a privacy policy?
Yes for any app with accounts or payments. The privacy policy is a promise about data. The terms set the rules of use, payment and cancellation terms, and limits on your liability. Make sure users agree with a recorded tick box, as in this guide.
Where should the privacy policy link go?
On the sign-up screen, in the footer, and in the store listing if you publish to the App Store or Google Play. Apple wants it inside the app in an easily accessible place. Google wants a public web address, not a PDF. Part of getting the app live is covered in moving an AI-built app to production.
What if my app is used by children?
Treat it as a special case. In the US the FTC's COPPA Rule covers apps directed at children under 13 and requires a clear privacy policy and verifiable parental consent. Speak to a lawyer before launch.
More in this topic: Problem solving: AI-built and no-code apps (26 guides) →
Sources
- Apple, App Store Review Guidelines (5.1 Privacy)
- Google Play Console Help, user data and privacy policy requirements
- GDPR Article 13, information to be provided
- FTC, Complying with COPPA: Frequently Asked Questions
- FTC, Privacy and Security business guidance
- Supabase docs, regions
- OpenAI API docs, data controls