Guide
Privacy policy vs terms of use: do you need both?
Short answer
A privacy policy is a notice that tells people how you handle their personal data, and data protection laws usually require one. Terms of use are a contract that sets the rules for using your site and limits your liability; they are usually optional but protective. Most websites and apps that collect any personal data or take payments need both.
What each document does
| Privacy policy | Terms of use | |
|---|---|---|
| What it is | A notice about personal data | A contract with users |
| Legally required? | Usually, if you collect personal data | Rarely as such, but needed to rely on a liability cap, acceptable-use rules and payment terms |
| Who it binds | You (you must do what it says) | You and each user who accepts it |
| Main contents | Data collected, purposes and legal bases, sharing, transfers, retention, security, rights, contact | Eligibility, accounts, acceptable use, user content, payments and refunds, IP, disclaimers, liability, law |
| How users see it | Linked wherever data is collected and in the footer | Accepted at sign-up or checkout, and linked in the footer |
| When to update | When you collect new data, add a provider or change retention | When features, prices or rules change |
Laws that require a privacy notice
- UK: the UK GDPR (Articles 13 and 14) lists the information you must give people. See the UK GDPR privacy policy template.
- EU: the GDPR has the same requirement and can apply to non-EU businesses that target people in the EU.
- UAE: Federal Decree-Law No. 45 of 2021 (PDPL) requires controllers to inform data subjects; the DIFC and ADGM have their own laws. See the UAE privacy policy template.
- US: California's CalOPPA requires commercial websites that collect personal information from California residents to post a privacy policy, and the CCPA and other state laws add rights notices. See the US privacy policy template.
Why terms of use are worth having
- They cap your liability (Legal Drafter's template: the greater of 12 months of payments and AED 500, GBP 100 or USD 100).
- They let you suspend users who abuse the service, scrape it or upload unlawful content.
- They set subscription renewal, cancellation and refund rules.
- They protect your content and brand and grant you the licence you need to host user uploads.
To be enforceable as a contract, terms work best when users actively accept them, for example with a checkbox at sign-up. A privacy policy does not need acceptance: it is information, and it is good practice to link it at the point where data is collected.
Do not merge them
Putting the privacy policy inside the terms makes it look like users "agreed" to data uses, which is not how most data protection laws work: consent, where needed, must be separate and freely given. Keep two documents and link them to each other.
FAQ
Does a website without accounts need a privacy policy?
Usually yes, if it has a contact form, analytics or logs IP addresses, all of which involve personal data.
Can I use one template for both?
No. They have different purposes and legal rules. Legal Drafter has a separate privacy policy and website terms template.
Do I also need a cookie policy?
In the UK and EU you need consent for non-essential cookies; many sites explain cookies inside the privacy policy, as Legal Drafter's template does, plus a consent banner.
Templates for this
Draft any of them with a guided form; party details stay in your browser.