Before you publish
🔴 items are legally load-bearing. 🟡 items materially reduce your privacy risk.🔴 Must be done
- Data controller filled in — legal company name, registered address, privacy contact email
- Every category of data you actually collect is listed (delete rows you don’t use; add ones you do)
- Payment processor named:
Waffo Pancake— card data is processed by Pancake, not stored on your servers - “We do not sell your personal information” kept if true (it’s true for most Pancake merchants)
- Retention periods filled in with real numbers
- Children’s minimum age set to match your market (13 / 16 / 18)
- The policy is linked from checkout and referenced by your Terms of Service
[privacy policy URL]
🟡 Strongly recommended
- Analytics tools named, each linked to its own privacy policy
- International-transfer safeguards declared if your servers or vendors are cross-border (SCCs, adequacy, BCRs)
- A real opt-out path for marketing (unsubscribe link + account toggle), separate from essential service notices
- Breach-notification timeframe stated (e.g., 72 hours)
Keep it in sync with your T&C. Section 11 of the Terms of Service template links to this policy by URL — publish this one first, then paste its URL into the T&C.
Template
Copy the block below and replace every[placeholder] with your real text. Delete any row or section that doesn’t apply to your product.
The template is in English. Translate or localize as your market requires — the legal substance should stay the same.
Privacy Policy (replace every [placeholder])
Section-by-section reference
Each section below shows its tier (🔴 load-bearing · 🟡 strongly recommended · ⚪ optional), a one-line summary, and the matching template snippet so you can read the guidance and copy that block together.1. Data Controller
🔴 load-bearing Names the legal entity responsible for the data — a brand name alone won’t do. Fill[full legal company name], [registered address], [privacy@yourcompany.com]. DPO only applies to large-scale or sensitive processing; otherwise write “Not applicable.”
Section 1
2. Personal Information We Collect
🔴 load-bearing List only what you actually collect — over-claiming creates obligations you can’t meet. Delete categories you don’t use, add ones you do. Keep the line that card numbers are not stored by you. Drop the optional block unless location or third-party login apply.Section 2
3. How We Use Your Information
🔴 load-bearing Each purpose is paired with a legal basis (GDPR Art. 6) — keep the pairing, it’s what regulators check. If you do marketing, “Your consent” is the basis, which means a real opt-in.Section 3
4. Cookies & Tracking Technologies
🟡 strongly recommended Disclose tracking. Strictly-necessary cookies can’t be disabled; everything else must be. Name your analytics tools and link each to its own policy; marketing pixels go in the “Marketing” row.Section 4
5. Sharing & Disclosure
🔴 load-bearing “We don’t sell” plus a named processor. For Pancake merchants the payment-processor line is the important one:Waffo Pancake is your PCI-DSS processor and card data never touches your servers. Keep “we do not sell” only if it’s true.
Section 5
6. Data Security
🔴 load-bearing Concrete measures plus a breach-notification window. List what you actually do; the 72-hour window (the GDPR reference point) signals you have an incident process.Section 6
7. Data Retention
🔴 load-bearing How long, then what happens. Vague “as long as necessary” is weak — give numbers. Tie transaction-record retention to your tax/accounting obligations, not a guess.Section 7
8. Your Data Rights
🔴 load-bearing The eight GDPR rights, how to exercise them, and the DPA complaint route. Fill the response window ([30 calendar days] is the GDPR default) and make sure the privacy email in Section 14 routes these requests to someone.
Section 8
9. Marketing & Opt-Out
🟡 strongly recommended Consent in, easy opt-out, and a clear line between marketing and essential notices. Keep billing and security notices outside the opt-out.Section 9
10. International Data Transfers
🟡 strongly recommended Only needed if data crosses borders. Name the safeguard — SCCs cover most cases.Section 10
11. Children’s Privacy
🔴 load-bearing Set the minimum age for your market and don’t knowingly collect below it (13 US/COPPA, 16 default GDPR, varies by member state).Section 11
12. Third-Party Links & Services
⚪ optional Disclaims responsibility for sites and services you don’t control.Section 12
13. Policy Changes
🔴 load-bearing Advance-notice window plus updating the date. 15 days is a reasonable default.Section 13
14. Contact Us
🔴 load-bearing Real, monitored channels. The privacy email here is where rights requests land — make sure someone reads it.Section 14