Privacy policy or terms of service — which one do you actually need

Two documents nearly everyone files under "boring formality". They're actually mirror images: one is demanded of you by law, the other you write for yourself.
And if you have to choose — time for one only — it matters a lot which is which.
Two documents, two different questions
A privacy policy answers the user: what do you do with my data? It's an obligation towards the person and towards the state. You're not negotiating — you're reporting.
Terms of service answer something else: on what rules are we dealing at all? It's a contract. What's allowed, what isn't, what happens on a breach, what you're not liable for.
Everything else follows from that.
Side by side
- Who requires it. The policy: the law. GDPR Article 13 requires you to tell people what you do with their data, and many national laws additionally require a published processing policy reachable by anyone. Terms of service are required by nobody — that's your own choice.
- Who it protects. The policy protects the user. The terms protect you.
- What's inside. Policy: what data, why, on what basis, who you share with, how long you keep it, how to delete it. Terms: rules of use, payment and refunds, prohibitions, limitation of liability, your right to ban a violator and to shut the service down.
- Is it negotiable. The policy isn't — it's a statement of facts about your processing. The terms are a deal: the person accepts them by clicking "Sign up".
- When you need it. Policy: the moment the first email is collected. Terms: when money, user-generated content, or a way to harm other users appears.
- What happens without it. No policy — complaints, an order from a regulator, a rejection in app review, friction with payment providers. No terms — you formally have no right to ban a toxic user, and a refund dispute won't go your way.
The policy: the law looks here first
The threshold is lower than people think. You become a data controller not at a thousand users, but when your contact form accepts its first email.
In many countries there's a second obligation stacked on top — a filing with the data-protection regulator before you start processing. In Russia, for example, the list of exemptions from that filing was cut sharply back in September 2022, so it now applies to almost all processing. Plenty of people build for years without knowing.
Good news: the policy is a short document. Six blocks and an hour of work, if you honestly listed your services. Step by step: how to add a privacy policy.
Terms: the only place you get to say no
Nobody requires terms — which is exactly why people skip them. Then the ordinary happens:
- a user uploads someone else's content, and the complaint lands on you;
- somebody scrapes your service with a hundred parallel scripts, and no rule anywhere forbids it;
- a customer demands a refund on an annual subscription in month eleven;
- you want to shut the project down, having never formally limited your obligations.
All of that is settled by a couple of paragraphs written in advance. Not retroactively: rules a person never accepted don't apply to them.
A minimal version fits on one page: what the service is, what's forbidden, how payment and refunds work, that you don't guarantee uptime, that you may ban for violations, and that you may change the terms with notice.
Who needs what
No fence-sitting:
- A landing page with an email form. Policy required. Terms not needed.
- A free app with no accounts and no analytics. Collect nothing, need nothing. But check your logs and counters — you usually do collect.
- A service with sign-up. Both. Login means accounts, and accounts mean rules of behaviour.
- Anything with payments. Both — and here the terms matter more, because refunds and subscriptions without them become an argument with no footing.
- An app in a store. Both. The store demands the policy link directly, and without terms of use you can't moderate user content.
- A service with an AI feature. Both, each with its own clause: in the policy, that the user's text goes to a model provider; in the terms, that model answers can be wrong and the human makes the call.
Can I merge them into one document?
Technically yes, practically don't. Different people read them at different moments, and stores and payment providers ask for a separate link to the policy specifically. Two pages are simpler than one full of caveats.
Which first, if there's only time for one?
The policy. It's legally required, the app store and the payment provider will ask for it, and it takes an hour. Write the terms next week — before your first paying user.
Do I need terms if the product is free?
Useful if there are accounts or user-generated content. Free doesn't stop spam, doesn't stop someone scraping your database, and doesn't remove the need to ban somebody.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





