Free GDPR Privacy Policy Template (Copy-Ready)
Updated November 11, 2026
A GDPR privacy policy template is a privacy notice that already contains every disclosure Articles 13 and 14 of the GDPR require: who the controller is, what data you collect, the purpose and lawful basis for each use, recipients, transfers outside the EEA, retention periods, data subject rights, and how to complain. Jump to the free template, replace the bracketed text, and delete lines that don't match how you process data.
What Articles 13 and 14 Require, Field by Field
Article 13 applies when you collect data directly from the person, through a form, checkout, or cookies; Article 13(1) makes the information due when the data is obtained, so link the notice from the form itself. Article 14 applies when you get it from someone else, such as a partner or a client who shares their staff's details. A GDPR notice must contain:
- Controller identity and contact details (Art. 13(1)(a)). Your legal entity name, address, and a working email, plus your EU representative under Article 27 if you are based outside the EU.
- Data Protection Officer contact (Art. 13(1)(b)), only if you have appointed one.
- Purposes and lawful basis (Art. 13(1)(c)) for each processing activity, not one basis for everything.
- The legitimate interests pursued (Art. 13(1)(d)) wherever you rely on Article 6(1)(f).
- Recipients or categories of recipients (Art. 13(1)(e)), such as your hosting provider, payment processor, and email platform.
- Transfers to third countries (Art. 13(1)(f)) and the safeguard used, with a way to get a copy.
- Retention period, or the criteria that set it (Art. 13(2)(a)).
- Data subject rights (Art. 13(2)(b)): access, rectification, erasure, restriction, objection, and portability.
- Right to withdraw consent at any time (Art. 13(2)(c)), where consent is your basis.
- Right to complain to a supervisory authority (Art. 13(2)(d)).
- Whether providing data is required by law or contract, and what happens if someone refuses (Art. 13(2)(e)).
- Automated decision-making and profiling covered by Article 22, with meaningful information about the logic involved and the consequences (Art. 13(2)(f)).
Article 14 drops field 11 and adds two more: the categories of personal data you hold (Art. 14(1)(d)) and the source of the data, including whether it came from publicly accessible sources (Art. 14(2)(f)). Under Article 14(3), you must give this notice within one month of obtaining the data, or earlier if you contact the person or disclose the data first.
How it must be written. Article 12(1) requires concise, intelligible, plain language. The EDPB-endorsed Guidelines on transparency under Regulation 2016/679 (WP260 rev.01) flag "We may use your personal data to develop new services" as poor practice. Say what actually happens: "We use your order history to recommend products on your account page."
Copy from your Article 30 record. Its fields 30(1)(b) to (f) hold the purposes, data categories, recipients, transfers and erasure time limits the notice needs, so the two never disagree.
Worked example: check one sign-up form
A German shop's newsletter form says: "We use your email address to send our weekly newsletter, based on your consent. Unsubscribe at any time. Our email provider stores it in the US under the EU-US Data Privacy Framework. We delete it within 30 days of you unsubscribing." Against Article 13:
- Purpose and basis, 13(1)(c): present.
- Recipient, 13(1)(e), and transfer, 13(1)(f): mechanism given, provider unnamed. Name it.
- Retention, 13(2)(a), and withdrawal of consent, 13(2)(c): present.
- Controller identity, 13(1)(a), rights, 13(2)(b), and complaint right, 13(2)(d): missing. Link the full notice beside the form.
Lawful Basis: One Worked Example for Each
Article 6(1) lists six lawful bases. Article 13(1)(c) requires the notice to pair every purpose with its basis, so choose one per purpose before processing starts.
- Consent (6(1)(a)). A visitor ticks an unticked box to join your newsletter. Article 7(3) makes withdrawing as easy as giving consent, so every email needs an unsubscribe link.
- Contract (6(1)(b)). You use a customer's shipping address to deliver the order they placed.
- Legal obligation (6(1)(c)). You keep invoices for the period your national tax law requires, even after a customer asks for erasure (Art. 17(3)(b)).
- Vital interests (6(1)(d)). A safety app shares a user's location with emergency services. Most websites never use this basis.
- Public task (6(1)(e)). A public university processes enrolment data to run its courses. Private businesses rarely qualify.
- Legitimate interests (6(1)(f)). You keep server logs with IP addresses briefly to detect fraud and attacks. Name the interest itself, as Article 13(1)(d) requires ("detecting payment fraud", not "improving our services"), and keep a written balancing test for Article 5(2) accountability.
Health, biometric, religious, and other special-category data under Article 9 needs an Article 9(2) condition, such as explicit consent, on top of the Article 6 basis. If you offer online services directly to children and rely on consent, Article 8 requires parental consent below age 16, which member states may lower to 13.
Data Subject Rights and Response Deadlines
- Access (Art. 15): a copy of the data and details of how it is processed.
- Rectification (Art. 16): correction of inaccurate data.
- Erasure (Art. 17): deletion on the grounds in Art. 17(1), subject to the Art. 17(3) exceptions such as legal retention duties.
- Restriction (Art. 18): a pause on processing while accuracy or an objection is checked.
- Portability (Art. 20): data in a structured, machine-readable format, where processing is based on consent or contract and carried out by automated means (Art. 20(1)(a)-(b)).
- Objection (Art. 21): to processing based on legitimate interests or public task (Art. 21(1)), plus an absolute right to object to direct marketing (Art. 21(2)-(3)).
- Automated decisions (Art. 22): not to be subject to solely automated decisions with legal or similarly significant effects.
Deadlines. Article 12(3) requires a response without undue delay and within one month of receiving the request. You can extend by two further months for complex or numerous requests if you tell the person why within the first month. If you won't act, Article 12(4) requires you to say so within one month, with reasons and their right to complain. Under Article 12(5), responses are free unless a request is manifestly unfounded or excessive, in which case you may charge a reasonable fee or refuse.
The separate objection notice. Article 21(4) requires the right to object to be presented clearly and separately from other information, no later than your first communication with the person. Most free templates bury it in the rights list; the template below gives it its own section.
Transfers Outside the EEA: What to Name
If any recipient stores or accesses data outside the EEA, including US cloud, email, and analytics providers, Article 13(1)(f) (and 14(1)(f)) requires the notice to state:
- The country or region, for example the United States.
- The Chapter V mechanism: an adequacy decision under Article 45 (such as those for the UK, Switzerland, Japan, and the EU-US Data Privacy Framework of July 10, 2023, which covers only US companies certified under it); Standard Contractual Clauses under Article 46, using the 2021 set adopted in Commission Implementing Decision (EU) 2021/914; Binding Corporate Rules under Article 47; or, in limited cases, an Article 49 derogation.
- How to get a copy of the Article 46 or 47 safeguards. Check each provider's data processing agreement for the mechanism it actually uses.
Copy-Ready GDPR Privacy Notice Template
Fill in the brackets, choose between the options separated by slashes, and delete sections that don't apply, such as automated decision-making or the EU representative.
Privacy Policy for [Company Legal Name]
Last updated: [Date]
1. Who We Are
[Company Legal Name] ("we," "us") of [registered address] is the controller of your personal data for [website/app name]. Contact us at [privacy@example.com].
[If applicable: Our representative in the EU under Article 27 GDPR is [Representative name, address, email].] [If applicable: Our Data Protection Officer can be reached at [dpo@example.com].]
2. Personal Data We Collect
- Data you give us: [name, email address, billing and shipping address, account password, messages you send us].
- Data collected automatically: [IP address, device and browser type, pages viewed, cookie identifiers].
- Data from other sources: [categories of data] from [source, e.g. payment provider, business partner, public registers].
3. Why We Use Your Data and Our Lawful Basis
- To create and manage your account and deliver what you ordered: performance of a contract (Art. 6(1)(b)).
- To keep invoices and accounting records: legal obligation (Art. 6(1)(c)).
- To send newsletters and set non-essential cookies: consent (Art. 6(1)(a)).
- To secure our services and prevent fraud: legitimate interests (Art. 6(1)(f)). Our interest is [keeping our systems and users safe].
4. Who Receives Your Data
We share personal data with [hosting provider], [payment processor], [email service], and [analytics provider], who process it only on our instructions, and with authorities where the law requires it. We do not sell your personal data.
5. International Transfers
[Provider name] processes data in [country]. We rely on [an adequacy decision / the EU-US Data Privacy Framework / Standard Contractual Clauses] for this transfer. To request a copy of the safeguards, email [privacy@example.com].
6. How Long We Keep Your Data
- Account data: while your account is open, plus [X months].
- Invoices and order records: [X years], as required by [tax law].
- Marketing data: until you unsubscribe or withdraw consent.
- Server logs: [X days].
7. Your Rights
You have the right to access, correct, and erase your personal data, to restrict its processing, and to receive it in a portable format. Where we rely on consent, you can withdraw it at any time without affecting processing that took place before. To exercise a right, email [privacy@example.com]. We respond within one month, extendable by two months for complex requests, in which case we will tell you why. You can also complain to your local data protection authority [or name the lead authority].
8. Your Right to Object
You can object at any time to processing based on our legitimate interests, on grounds relating to your situation. You can object to direct marketing at any time, and we will then stop using your data for that purpose.
9. Do You Have to Give Us Your Data?
[Name, email, payment details] are needed to [complete a purchase]; without them we cannot provide the service. Everything else is optional.
10. Automated Decision-Making
[We do not make decisions about you based solely on automated processing.] / [We use [system] to [decision], based on [logic]. This means [effect for you]. You can ask for human review.]
11. Children
Our services are not directed at children under [16 / the age set in your country], and we do not knowingly collect their data.
12. Changes to This Policy
We post changes here, update the date above, and notify you of significant changes by [email].
Prefer answering questions to editing brackets? You can build a GDPR-structured policy with the free generator, then work through the GDPR compliance checklist for the obligations a privacy notice doesn't cover. If you're based outside Europe, first check whether the GDPR applies to your company at all.
Frequently Asked Questions
What does a privacy notice need to include?
Under GDPR Article 13, it must include your identity and contact details, any DPO's contact details, the purposes and lawful basis for each use, your legitimate interests where relevant, recipients, transfers outside the EEA, retention periods, data subject rights, the right to withdraw consent and to complain, whether providing data is required, and any automated decision-making.
What are the 10 requirements of GDPR, the European Union's privacy framework?
The GDPR has no official list of ten requirements. Ten commonly cited obligations are: a lawful basis, a transparent privacy notice, honoring data subject rights, records of processing (Art. 30), privacy by design (Art. 25), processor contracts (Art. 28), security (Art. 32), 72-hour breach notification (Art. 33), impact assessments (Art. 35), and transfer safeguards (Chapter V).
What are the 7 basic principles of GDPR?
Article 5 sets them out: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; and accountability, meaning you must be able to show you comply with the other six.
What do you write in a privacy policy?
Write what personal data you collect and from where, why and on what legal basis, who receives it, where it is transferred, how long you keep it, people's rights, and how to contact you, in plain language that matches what you actually do.