Changelog
- 1.0.0, 22 October 2026: first release
kits / policy-pack
Thorough fill-in privacy, terms, cookie, refund and acceptable use templates, with a guide to which ones you need.
MIT License
Copyright (c) 2026 Snowkit
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.Version 1.0.0
Most small businesses need the same few legal pages: a privacy policy, terms, a cookie notice, a refund policy and often an acceptable use policy. This pack gives you thorough fill-in templates for each, a guide to working out which ones you need, a checklist to map the personal data you actually handle, and a routine for keeping everything current. The templates are written to work alongside the main privacy and consumer laws in the EU, UK, US, Canada and Australia, in plain language your customers can read.
which-policies-do-i-need.md and answer the decision table. It tells you which documents you need.data-processing-checklist.md. List what personal data you collect, why, where it goes and how long you keep it.privacy-policy.md and fill in the summary and section 2 from your checklist.cookie-notice.md and check your site loads no optional cookies before consent.policy-maintenance.md, then book a lawyer to review the finished drafts.| File | What it is |
|---|---|
README.md | This file |
which-policies-do-i-need.md | A decision guide: which documents you need, which laws to know about, and what to ask your lawyer |
data-processing-checklist.md | Find your data, a processing register, a processor and DPA checklist, rights requests, security basics and a breach plan |
privacy-policy.md | A full privacy policy with data and lawful basis tables, processors, retention, transfers, rights by region, children, cookies and changes |
cookie-notice.md | Banner wording in several variants, a preferences panel, the cookie notice with a cookie table, and a setup checklist |
terms-of-service.md | Terms covering accounts, acceptable use, payments and renewals, IP, user content, termination, disclaimers, liability, governing law and changes |
refund-policy.md | Refund and cancellation wording for digital goods, subscriptions, physical goods and services, with statutory rights and checkout wording |
acceptable-use-policy.md | Rules on illegal, harmful and abusive use, security, spam, enforcement, reporting and appeals |
policy-maintenance.md | When to update, notice periods, email and in-product notice templates, and a version history table |
CHANGELOG.md | Version history |
LICENSE.txt | Licence |
These are starting points, not legal advice, and using them doesn't make you compliant with any law. Laws differ by country and state, change over time, and depend on facts about your business that a template can't know. Have a qualified lawyer review your final documents, especially if you handle sensitive data, data about children, or sell to consumers in several countries.
MIT License. See LICENSE.txt.
Starting point, not legal advice. What you must prohibit, and how you must handle reports and removals, depends on your service and where your users are. Some countries have specific online safety and content moderation rules. Have a qualified lawyer review your final policy before you rely on it.
Everything below the line is the policy itself.
---
Last updated: [22 October 2026]
This policy explains what you may not do when using [Product name] and other services run by [Company legal name] ("[Company name]", "we", "us") (the "Service"). It forms part of our [Terms of service, link]. If you break it, we may remove content or suspend or close your account.
It applies to everyone who uses the Service, including people you invite or allow to use your account.
You may not use the Service to:
You may not:
If you believe content on the Service infringes your rights, contact [[email protected]] with the details in section 7.
You may not post content that attacks or demeans people based on race, ethnicity, national origin, religion, disability, sex, gender identity, sexual orientation, age or another protected characteristic, or that promotes violence against them.
[Add your own rules on adult content, graphic violence, profanity or other material, depending on your audience.]
You may not:
You may not:
We'll take action proportionate to the breach. Depending on its seriousness, we may:
Where it's practical and lawful, we'll tell you what we did and why, and how you can ask us to reconsider. For serious breaches, such as illegal content or threats to safety, we may act without warning.
We aren't obliged to monitor all content, but we may review content and activity to enforce this policy and keep the Service safe.
If you see something on the Service that breaks this policy, tell us:
Please include where the content is (a link if possible), what the problem is, and your contact details if you'd like to hear back. For infringement claims, also include the work you believe is infringed, your contact details, and a statement that you believe in good faith that the use isn't authorised.
We review reports [within X working days]. If there's an immediate risk to someone's safety, contact the local emergency services first.
If you think we made a mistake, reply to our notice or email [[email protected]] within [30] days. Tell us why. Someone who wasn't involved in the original decision will review it [where practical] and tell you the outcome.
We may update this policy. The "Last updated" date shows the latest version. If we make significant changes, we'll tell you [by email or in the Service] before they take effect.
Questions about this policy: [[email protected]].
Starting point, not legal advice. Cookie rules differ by country. In the EU and UK, most cookies and similar technology that aren't strictly necessary need consent before they are set, and some countries allow limited exceptions. In the US, rules focus more on disclosure and opt-outs. Have a qualified lawyer review your banner and notice before you rely on them.
This file has four parts:
"Cookies" here also covers similar technology: local storage, session storage, pixels, tags, SDKs in apps and device fingerprinting. The rules usually treat them the same way.
---
Cookies on [Company name]
We use necessary cookies to make this site work. With your permission, we'd also like to use analytics cookies to understand how the site is used, and marketing cookies to measure our ads. You can change your choice at any time in Cookie settings.
[Accept all] [Reject all] [Manage settings]
[Read our cookie notice]
We use necessary cookies to run this site, and optional cookies for analytics and ads if you allow them.
[Accept all] [Reject all] [Settings]
Help us improve [Product name]
We'd like to use analytics cookies to see which pages people use and where they get stuck. We don't use advertising cookies. Necessary cookies that keep the site working are always on.
[Allow analytics] [No thanks]
[Cookie notice]
You may not need a banner at all. Say so in your cookie notice instead:
We only use cookies that are strictly necessary for this site to work, such as keeping you signed in and remembering your cookie choice. We don't use analytics or advertising cookies.
Where your audience is mainly in US states that use an opt-out model, a notice plus clear opt-out links may be used instead of a consent banner. If you serve EU or UK visitors as well, use one of the variants above for them.
We and our partners use cookies for analytics and personalised advertising. You can opt out of the sale or sharing of your personal information, including through cookies, at any time.
[Do Not Sell or Share My Personal Information] [Cookie settings] [OK]
Honour browser opt-out signals such as Global Privacy Control where the law requires.
| Avoid | Why | Use instead |
|---|---|---|
| "By continuing to browse, you accept cookies." | Continuing to browse isn't valid consent in the EU or UK. | Ask for an active choice. |
| "We value your privacy" followed only by an Accept button | No real choice. | Put Accept and Reject side by side. |
| "Reject" hidden in a second layer or shown as a faint link | Unequal choice. | Same style and level for both. |
| "Cookies to improve your experience" | Too vague to inform anyone. | Name the purpose: analytics, advertising, preferences. |
| "Accept all to continue" with the site blocked | Consent must be freely given, so blocking access for refusing optional cookies is risky in many places. | Let people use the site after rejecting. |
---
Show these categories, each with a short description. Only "Necessary" is on by default and can't be turned off.
Cookie settings
Choose which cookies we can use. You can change this at any time from the Cookie settings link at the bottom of every page.
Necessary - Always on
These make the site work: signing in, keeping your session secure, remembering items in your basket and remembering your cookie choice. The site can't work properly without them.
Preferences - Off
These remember choices such as language, region or display settings, so you don't have to set them each visit.
Analytics - Off
These help us understand how people use the site, which pages are visited and where errors happen, so we can improve it. [We use Analytics provider. Data is reported in aggregate.]
Marketing - Off
These are set by us and our advertising partners to measure how well our ads work and, where allowed, to show you relevant ads on other sites.
[Save choices] [Accept all] [Reject all]
Keep the category names the same in the banner, the panel, the notice and your consent tool so people can follow them.
---
Everything below the line is the notice to publish, for example at /cookies.
---
Last updated: [22 October 2026]
This notice explains how [Company name] uses cookies and similar technology on [example.com and the Product name app]. It should be read together with our [Privacy policy, link].
Cookies are small text files that a website stores on your device. Similar technology includes local storage, pixels (tiny images that report when a page or email is viewed) and software development kits in apps. We call all of these "cookies" in this notice.
Cookies set by us are "first-party" cookies. Cookies set by another company, such as an analytics or advertising provider, are "third-party" cookies.
Some cookies last only until you close your browser ("session cookies"). Others stay for a set period ("persistent cookies").
| Category | What they do | Can you turn them off? |
|---|---|---|
| Necessary | Make the site work and keep it secure | No, but you can block them in your browser, and parts of the site may then stop working |
| Preferences | Remember your choices | Yes |
| Analytics | Help us understand use of the site | Yes |
| Marketing | Measure ads and, where allowed, personalise them | Yes |
We only set preferences, analytics and marketing cookies if you agree [or, in places where the law uses an opt-out model, until you opt out].
| Name | Provider | Category | Purpose | Duration | First or third party |
|---|---|---|---|---|---|
| [session_id] | [Company name] | Necessary | Keeps you signed in | [Session] | First |
| [csrf_token] | [Company name] | Necessary | Protects forms against cross-site request forgery | [Session] | First |
| [cookie_consent] | [Company name] | Necessary | Remembers your cookie choices | [12 months] | First |
| [lang] | [Company name] | Preferences | Remembers your language | [12 months] | First |
| [Analytics cookie name] | [Analytics provider] | Analytics | Distinguishes visitors and sessions | [Duration] | [Third] |
| [Ad cookie name] | [Ad provider] | Marketing | Measures ad conversions | [Duration] | [Third] |
| [Name] | [Provider] | [Category] | [Purpose] | [Duration] | [Party] |
We review this list [every quarter and whenever we add a new tool]. Third-party providers may change their cookie names; their own policies have the current details: [links to provider privacy or cookie pages].
We'll update this notice when we change the cookies we use. The date at the top shows the latest version. If a change needs your consent, we'll ask again.
Questions about cookies: [[email protected]].
---
Starting point, not legal advice. Record-keeping and contract duties differ by law and by the size and type of your business. This checklist helps you find out what personal data you handle so your policies can describe it accurately. Have a qualified lawyer review your conclusions before you rely on them.
Do this before you write or update your privacy policy. A policy written without it usually misses something, and the gaps are what get businesses into trouble.
Under the GDPR and UK GDPR, many organisations must keep a written record of their processing activities, and must have contracts with the service providers that process personal data for them. Even where those duties don't apply, the same record makes every other privacy task faster.
Business: ______________________ Completed by: ______________ Date: ____________
---
Work through each place personal data can enter your business. Tick each one that applies, then add it to the register in Part 2.
One row per purpose. Copy this table into a spreadsheet if it gets long.
| Purpose | People | Data | Source | Lawful basis (EU/UK) | Systems | Shared with | Location | Retention | Sensitive? |
|---|---|---|---|---|---|---|---|---|---|
| [Customer accounts] | [Customers] | [Name, email, password hash] | [Sign-up form] | [Contract] | [App database] | [Hosting provider] | [Region] | [Account life + 30 days] | [No] |
| [Payments] | [Customers] | [Billing details, transactions] | [Checkout] | [Contract, Legal obligation] | [Payment provider, accounting tool] | [Accountant] | [Region] | [Number of years required by tax law] | [No] |
| [Newsletter] | [Subscribers] | [Email, opt-in date] | [Sign-up form] | [Consent] | [Email platform] | [-] | [Region] | [Until unsubscribe] | [No] |
| [Analytics] | [Visitors] | [IP-derived location, device, pages] | [Website] | [Consent or Legitimate interests] | [Analytics tool] | [-] | [Region] | [14 months] | [No] |
| [Support] | [Customers, prospects] | [Name, email, messages] | [Email, chat] | [Contract, Legitimate interests] | [Support tool] | [-] | [Region] | [2 years] | [No] |
| [Purpose] | [People] | [Data] | [Source] | [Basis] | [Systems] | [Recipients] | [Location] | [Period] | [ ] |
Notes on the columns:
List every outside company that handles personal data for you.
| Provider | What they do for you | Data they handle | Location of processing | DPA signed? | Transfer safeguard | Security checked? | Review date |
|---|---|---|---|---|---|---|---|
| [Hosting] | [Hosts the app and database] | [All app data] | [Region] | [ ] | [Adequacy, SCCs, or n/a] | [ ] | [Date] |
| [Email platform] | [Sends newsletters] | [Email addresses] | [Region] | [ ] | [ ] | [ ] | [Date] |
| [Payment provider] | [Takes payments] | [Billing data] | [Region] | [ ] | [ ] | [ ] | [Date] |
| [Analytics] | [Usage statistics] | [Device and usage data] | [Region] | [ ] | [ ] | [ ] | [Date] |
| [Provider] | [Service] | [Data] | [Region] | [ ] | [ ] | [ ] | [Date] |
For each provider:
Some providers act as independent controllers rather than processors for some data (payment providers often do for fraud prevention, for example). Note this in the register, and name them in your privacy policy's sharing section.
Ask a lawyer whether any of these apply:
privacy-policy.md from the register: sections 2 to 7 map directly to Parts 2 and 3 here.cookie-notice.md from the website and app items in Part 1.policy-maintenance.md: [Date].Starting point, not legal advice. Notice periods and the way you must tell people about changes depend on the law where your users are and on what your own terms promise. Have a qualified lawyer review significant changes before you publish them.
Publishing a policy is the start, not the end. A privacy policy that described your business accurately last year may be wrong today because you added an analytics tool, launched in a new country or started a newsletter. This file gives you a routine, a log and notice templates.
---
Next scheduled review: [Date]. Owner: [Name].
| Type | Examples | What to do |
|---|---|---|
| Minor | Fixing typos, clearer wording, updating contact details, adding a processor that does the same job as one you already list | Update the policy and the "Last updated" date. Record it in the log. |
| Significant | New purposes, new categories of data, new types of recipients, selling or sharing data, new countries, changes to prices, renewals, refunds, liability or dispute terms | Tell users in advance. Record it in the log. Get legal review. |
| Needs new consent | Using data for a purpose people haven't agreed to and where consent is your lawful basis, adding a new cookie category | Ask for consent again. Don't rely on a notice alone. |
When unsure, treat a change as significant.
| Document | Suggested notice for significant changes | Notes |
|---|---|---|
| Privacy policy | Before the change takes effect, [30] days where practical | A new purpose may need consent, not just notice. |
| Cookie notice | When the change goes live, with a new consent request if a new category or purpose is added | |
| Terms of service | [30] days | Check your current terms, which may promise a specific period. |
| Refund policy | [30] days, and apply the policy that was in force at the time of purchase | Never apply a less generous policy to past orders. |
| Acceptable use policy | [14 to 30] days | Urgent safety changes can apply sooner. |
Changes required by law, or needed urgently for security, can take effect sooner. Explain why in the notice.
Use more than one channel for significant changes.
Subject: Changes to our [privacy policy / terms of service] from [date]
Hi [first name],
We're updating our [privacy policy / terms of service]. The changes take effect on [date].
What's changing
- [Plain summary of change 1]
- [Plain summary of change 2]
What this means for you
[One or two sentences. For example: "You don't need to do anything." Or: "If you don't want your data used for X, you can turn it off in Settings > Privacy."]
You can read the full updated [policy / terms] at [link], and compare it with the previous version at [link].
If you don't agree with the changes, you can [close your account / cancel your plan] before [date] [and we'll refund any unused prepaid period].
Questions? Reply to this email or contact [[email protected]].
[Company name]
We've updated our [privacy policy / terms]. [One-line summary.] Changes take effect on [date]. [Read what changed]
Updated [date]. We [added Provider type to our list of service providers / clarified how long we keep support messages / added a section on AI features]. [See previous version.]
Keep every published version. Store a dated copy (PDF or the page source) each time you publish, so you can show what someone agreed to and when.
| Document | Version | Published | Effective | Summary of change | Type | Notice sent | Approved by | Archived copy |
|---|---|---|---|---|---|---|---|---|
| Privacy policy | 1.0 | [Date] | [Date] | First version | - | - | [Name] | [Link] |
| Terms of service | 1.0 | [Date] | [Date] | First version | - | - | [Name] | [Link] |
| Cookie notice | 1.0 | [Date] | [Date] | First version | - | - | [Name] | [Link] |
| Refund policy | 1.0 | [Date] | [Date] | First version | - | - | [Name] | [Link] |
| Acceptable use policy | 1.0 | [Date] | [Date] | First version | - | - | [Name] | [Link] |
| [Document] | [Version] | [Date] | [Date] | [Summary] | [Minor / Significant] | [Date, channel] | [Name] | [Link] |
For terms of service and anything people accept actively, record for each user:
For cookie consent, record the banner version and the categories accepted.
Starting point, not legal advice. Privacy laws differ by country and, in the US and Canada, by state and province. This template is written to work alongside the GDPR, UK GDPR and CCPA as amended by CPRA, but it doesn't make you compliant on its own. Have a qualified lawyer review your final policy before you rely on it.
data-processing-checklist.md first. This policy should describe what that record shows, nothing more and nothing less.which-policies-do-i-need.md)./privacy, link it from every page footer and from every form that collects personal data.Everything below the line is the policy itself.
---
Last updated: [22 October 2026] Effective from: [22 October 2026]
The rest of this policy explains each point in detail.
[Company name] ("we", "us", "our") runs [the website at example.com and the Product name app] (together, the "Service").
For the purposes of the GDPR and UK GDPR, [Company name] is the controller of the personal data described in this policy, except where section 12 says otherwise.
[If you have appointed one:] Our data protection officer is [Name or firm], who can be reached at [[email protected]].
[If required, because you are outside the EU or UK but offer goods or services to people there:] Our representative in the EU is [Name, address, email]. Our representative in the UK is [Name, address, email].
| Category | Examples | When we collect it |
|---|---|---|
| Identity and contact | [Name, email address, phone number] | [When you sign up, buy or contact us] |
| Account | [Username, password (stored hashed), preferences] | [When you create an account] |
| Payment | [Billing name, billing address, last four digits of card, transaction history] | [When you buy. Full card details are handled by our payment provider, not stored by us.] |
| Communications | [Messages, support requests, survey answers] | [When you contact us or respond to a survey] |
| Content you create | [Files, posts, comments, project data] | [When you use the Service] |
| Marketing preferences | [Whether you've opted in to our emails] | [When you subscribe or change settings] |
| [Other] | [Examples] | [When] |
| Category | Examples | How |
|---|---|---|
| Device and technical | [IP address, browser type, operating system, device identifiers] | [Server logs, cookies and similar technology] |
| Usage | [Pages viewed, features used, clicks, time on page, referring site] | [Analytics tools, see section 9] |
| Approximate location | [Country or city derived from IP address] | [Server logs, analytics] |
| [Other] | [Examples] | [How] |
| Source | Data | Why |
|---|---|---|
| [Sign-in providers, such as Google or Apple] | [Name, email, profile picture] | [When you choose to sign in with them] |
| [Payment provider] | [Payment status, fraud signals] | [To confirm payments and prevent fraud] |
| [Your employer or team admin] | [Name, work email] | [When they invite you to their workspace] |
| [Other] | [Data] | [Why] |
[Choose one:]
We use personal data only for the purposes below. If you are in the EU, EEA or UK, the law requires us to have a lawful basis for each purpose. The table shows which one we rely on.
| Purpose | Data used | Lawful basis (EU and UK) |
|---|---|---|
| Create and manage your account | Identity, contact, account | Contract: we need it to provide the Service you asked for |
| Provide the Service and its features | Account, content, usage | Contract |
| Take payments, issue invoices and keep financial records | Identity, payment | Contract; Legal obligation (tax and accounting records) |
| Respond to support requests | Identity, communications | Contract, or Legitimate interests (answering questions from people who aren't customers) |
| Send service messages such as receipts, security alerts and changes to terms | Contact | Contract; Legitimate interests |
| Send marketing emails | Contact, marketing preferences | Consent, or Legitimate interests where the law allows us to email existing customers about similar products, with an easy opt-out |
| Understand how the Service is used and improve it | Usage, technical | Legitimate interests, or Consent where cookies or similar technology require it |
| Keep the Service secure and prevent fraud and abuse | Technical, usage, payment | Legitimate interests; Legal obligation |
| Comply with the law and respond to lawful requests | Any relevant data | Legal obligation |
| Establish, exercise or defend legal claims | Any relevant data | Legitimate interests |
| [Other purpose] | [Data] | [Basis] |
Where we rely on legitimate interests, we have balanced our interests against your rights. You can ask us for details of that assessment, and you can object (see section 8).
Where we rely on consent, you can withdraw it at any time. Withdrawing doesn't affect anything we did before.
Where we need data to perform a contract with you and you don't provide it, we may not be able to provide the Service.
[If applicable:] Automated decisions. We [do not make decisions about you based solely on automated processing that have legal or similarly significant effects / use automated processing to describe what, for example fraud screening at checkout. You can ask for a person to review the decision by contacting us].
[If applicable:] AI features. When you use [feature name], the content you submit is sent to [provider type, e.g. "a third-party model provider"] to produce a result. [It is / is not] used to train models. It is kept for [period]. [Explain any opt-out.]
We don't share personal data except as described here.
| Recipient | Purpose | Location |
|---|---|---|
| [Hosting provider] | Hosting the Service and storing data | [Country or region] |
| [Payment provider] | Processing payments | [Country or region] |
| [Email provider] | Sending service and marketing emails | [Country or region] |
| [Analytics provider] | Understanding use of the Service | [Country or region] |
| [Support tool] | Managing support requests | [Country or region] |
| [Other] | [Purpose] | [Location] |
These service providers act on our instructions under written contracts that require them to protect your data and use it only to provide services to us. [An up-to-date list is available at link.]
We may also share personal data:
We [do not] sell personal information, and we [do not] share it for cross-context behavioural advertising, as those terms are defined in California law. [If you do, say so here and describe your opt-out in section 8.]
We keep personal data only as long as we need it for the purposes in section 3, then delete or anonymise it.
| Data | Retention period | Why |
|---|---|---|
| Account data | [For as long as your account is open, then deleted within 30 days of closure] | Providing the Service |
| Content you create | [Until you delete it or close your account, then removed from backups within 90 days] | Providing the Service |
| Payment and invoice records | [Number of years required by tax law in country, often 6 to 10 years] | Legal obligation |
| Support conversations | [2 years after the conversation closes] | Support quality, legal claims |
| Marketing preferences | [Until you unsubscribe, plus a suppression record so we don't email you again] | Respecting your choice |
| Server logs | [30 days] | Security |
| Analytics data | [14 months] | Product improvement |
| [Other] | [Period] | [Why] |
We use technical and organisational measures appropriate to the risk, including [encryption in transit and at rest, access controls with two-factor authentication for staff, least-privilege access, regular backups, logging and monitoring, and staff confidentiality obligations].
No system is completely secure. If a breach affects your personal data in a way that is likely to put you at risk, we'll tell you and the relevant regulator where the law requires.
[Company name] is based in [country]. Our service providers process data in [countries or regions]. This means your data may be transferred to and stored in countries with different data protection laws from your own.
EU, EEA and UK. When we transfer personal data out of the EU, EEA or UK, we make sure it is protected by one of the following:
You can ask us for a copy of the safeguards we rely on by emailing [[email protected]].
Wherever you are, you can:
We'll answer every request, and we won't treat you differently for using your rights.
Under the GDPR and UK GDPR you have the right to:
If the CCPA as amended by CPRA applies to us, California residents have the right to:
We [honour / will honour] opt-out preference signals such as Global Privacy Control as a valid request to opt out of sale and sharing for that browser [and any account linked to it].
In the past 12 months we collected the categories of personal information listed in section 2, from the sources listed there, for the purposes in section 3, and disclosed them for business purposes to the categories of recipients in section 4. [We have not sold or shared personal information in the past 12 months.]
You can use an authorised agent to make a request on your behalf. We may ask the agent for proof of authorisation and ask you to confirm your identity directly.
Several US states give residents rights similar to those above, such as access, correction, deletion, portability and opting out of targeted advertising, sale and certain profiling. If one of these laws applies to you, use the contact details below. If we decline your request, you can appeal by replying to our decision with the subject line "Appeal". [If the law in your state requires it, add how to contact the state attorney general if the appeal is denied.]
If you are in Canada, you have rights of access and correction under PIPEDA or the applicable provincial law, and you can complain to the Office of the Privacy Commissioner of Canada or your provincial commissioner. If you are in Australia, you can access and correct your information under the Privacy Act 1988 and complain to the Office of the Australian Information Commissioner if you are not satisfied with our response.
We use cookies and similar technology such as local storage and pixels to [keep you signed in, remember your preferences, understand how the Service is used and measure marketing]. Some are strictly necessary. Others are only set if you agree.
You can change your choices at any time in [Cookie settings, link in the footer]. Full details, including a list of the cookies we use, are in our [Cookie notice, link].
The Service is [not directed at children under 13 / 16 / 18] and we don't knowingly collect personal data from them. If you believe a child has given us personal data, contact [[email protected]] and we'll delete it.
[If your service is aimed at or likely to be used by children, replace this section with advice from a lawyer. Rules such as COPPA in the US, the age of digital consent under GDPR Article 8, and the UK Age Appropriate Design Code may apply.]
The Service may link to websites and services we don't control. Their own privacy policies apply, not this one.
[Delete if not applicable.] When a business uses [Product name] to process personal data about its own customers or staff, that business is the controller and we act as its processor. Our [Data processing agreement, link] governs that processing. If your data is in a workspace run by an organisation, please contact that organisation first.
We'll update this policy when our practices or the law change. The "Last updated" date at the top shows when it last changed. If we make a significant change, we'll tell you [by email or with a notice in the Service] at least [30] days before it takes effect, unless the change is required sooner by law. Previous versions are available [at link / on request].
Starting point, not legal advice. Consumer law differs by country and state, and some customer rights can't be removed by any policy. This template includes wording for common statutory rights, but you need to check which apply to you. Have a qualified lawyer review your final policy before you rely on it.
/refunds, link it from the footer, the checkout page and your order confirmation emails.Your policy can be more generous than the law, never less. Some of the rules that often apply:
| Where | Rule | What it means in practice |
|---|---|---|
| EU and EEA | Consumer Rights Directive (2011/83/EU) | Consumers buying online usually have 14 days to withdraw without giving a reason. For goods, this usually runs from delivery. For services and digital content, from the day of the contract. |
| EU and EEA | Digital content exception | The right to withdraw from digital content not supplied on a physical medium can be lost once supply has started, but only if the consumer gave prior express consent to start during the withdrawal period, acknowledged that they lose the right, and you confirmed this on a durable medium such as email. |
| EU and EEA | Online withdrawal function | EU rules adopted in 2023 require traders who sell online to offer an easy withdrawal function on their interface, applying from June 2026. Check how this applies to your checkout and account pages. |
| United Kingdom | Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 | A 14-day cancellation right similar to the EU, with a similar digital content exception. |
| United Kingdom | Consumer Rights Act 2015 | Goods must be of satisfactory quality, fit for purpose and as described. Digital content must meet similar standards. Services must be performed with reasonable care and skill. Remedies such as repair, replacement, price reduction or refund apply when they aren't. |
| Australia | Australian Consumer Law | Goods and services come with automatic statutory rights, for example that goods are of acceptable quality and match their description. A business can't say "no refunds" in a way that suggests those rights don't exist. Customers are entitled to a remedy for a major failure. |
| United States | Varies by state | There is no general federal right to return goods. Some states require a refund policy to be displayed if you don't offer refunds, and many states regulate automatic renewals and cancellation of subscriptions. |
| Everywhere | Faulty or misdescribed products | In almost every country, customers have remedies when what they bought doesn't work or isn't what you described, whatever your policy says. |
Business-to-business sales are often outside these consumer rules, but your contract terms still apply.
If you sell digital downloads, online access or services that start straight away to consumers in the EU or UK, and you want the 14-day withdrawal right to end once access begins, the checkout needs an active step. A common pattern:
- [ ] I want access to start immediately. I understand that I lose my right to withdraw from this purchase once the download or streaming has started.
Then confirm it in the order email:
You asked for immediate access to [product] and acknowledged that your right to withdraw ends once access begins. Access started on [date and time].
For services:
- [ ] Please start the service now. I understand that if I cancel within 14 days I may have to pay for the part of the service already provided, and that I lose the right to cancel once the service has been fully provided.
The box must not be pre-ticked. Without these steps, the normal 14-day right usually applies even if the customer has already downloaded the product.
Everything below the line is the policy itself. Keep the sections you need.
---
Last updated: [22 October 2026]
This policy explains how cancellations and refunds work for purchases from [Company legal name] ("[Company name]", "we", "us") through [example.com / the Product name app].
Email [[email protected]] [or use the form at link] with:
[EU and UK customers can also use the withdrawal function at link, or the model withdrawal form below.]
We'll reply within [2 working days].
This covers [downloads, templates, e-books, software licences, online courses and other digital content].
This covers [monthly and annual plans for Product name].
This covers [consultations, bookings, projects, classes and other services].
If something is wrong, please contact us first. We can usually sort it out faster than a card dispute. You keep any right you have to raise a dispute with your card issuer.
Customers can use this, or any other clear statement, to cancel within the legal period.
To: [Company legal name, address, email]
I hereby give notice that I withdraw from my contract for the sale of the following goods / for the supply of the following service or digital content:
Ordered on / received on:
Name:
Address:
Date:
This policy doesn't affect your statutory rights as a consumer.
Starting point, not legal advice. Contract and consumer law differ by country and state, and some clauses here, such as limits on liability, may not be enforceable against consumers in every place you sell. Have a qualified lawyer review your final terms before you rely on them.
Everything below the line is the terms themselves.
---
Last updated: [22 October 2026]
These terms ("Terms") are an agreement between you and [Company legal name] ("[Company name]", "we", "us"), a company registered in [country] under number [number], with its address at [address]. They cover your use of [the website at example.com, the Product name app and related services] (the "Service").
Please read them carefully. By [creating an account / buying / using the Service] you agree to these Terms. If you don't agree, don't use the Service.
If you use the Service on behalf of an organisation, you confirm you have authority to accept these Terms for it, and "you" includes that organisation.
This summary is for convenience. The full Terms below are what apply.
These Terms include the following documents:
If these documents conflict, [these Terms apply / the more specific document applies].
You may use the Service only if you are at least [18] years old, or the age of majority where you live if higher, and you're not barred from using it under any applicable law.
We grant you a personal, non-exclusive, non-transferable, revocable right to use the Service for [your personal use / your internal business purposes] in line with these Terms.
You agree to follow our [Acceptable use policy]. In particular, you won't:
Prices are shown [on our pricing page, link] and at checkout. [Prices include / exclude] [VAT / sales tax / GST], which [is added at checkout where applicable].
Payments are processed by [payment provider]. By giving us a payment method you authorise us to charge it for the plan you choose, including renewals.
[Delete this section if you don't sell subscriptions.]
[Delete if not applicable.] If you start a trial that converts to a paid plan, we'll tell you the price and the date the first charge happens before you start, and [remind you before it ends]. Cancel before the trial ends to avoid being charged.
If a payment fails, we'll tell you and try again. If it still fails after [14] days, we may downgrade or suspend your account until payment is made.
Refunds are covered by our [Refund and cancellation policy, link]. Nothing in these Terms affects any statutory right you have to cancel or to a refund.
The Service, including its software, design, text, graphics and trademarks, belongs to [Company name] or our licensors and is protected by law. These Terms don't give you any rights in it except the right to use the Service as described in clause 5.
If you send us feedback or suggestions, we may use them without any obligation to you.
[Delete this section if users can't upload or create content.]
"Your content" means anything you upload, post, create or store in the Service.
[Optional, for AI features:] We [do not] use your content to train machine learning models. [Describe any opt-in or opt-out.]
The Service may let you connect to services run by other companies. Your use of those services is governed by their terms, and we're not responsible for them.
We're always working on the Service and may add, change or remove features. If we remove a feature that is a significant part of a paid plan, we'll give you reasonable notice and, if you cancel because of it, a pro-rata refund for any prepaid period you can't use.
You can stop using the Service and close your account at any time in [Settings > Account]. Closing your account doesn't by itself cancel a paid plan you've already paid for unless our refund policy says otherwise.
We may suspend or end your access to the Service if:
Where reasonable, we'll warn you first and give you a chance to fix the problem. If we end your access without you being at fault, for example because we close the Service, we'll give you at least [30] days' notice where possible and a pro-rata refund for any prepaid period.
We'll keep your content for [30] days after your account closes so you can export it, unless the law requires otherwise or we closed the account because of a serious breach. After that we delete it as described in our Privacy policy. Clauses that by their nature should survive, including 7, 12, 13, 15 and 16, continue after termination.
We work hard to keep the Service available and accurate, but we provide it "as is" and "as available". To the extent the law allows, we don't make any promises that it will be uninterrupted, error-free or fit for a particular purpose, beyond what these Terms expressly say.
This clause doesn't affect your statutory rights as a consumer (see clause 14).
Nothing in these Terms limits or excludes liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that can't be limited or excluded by law.
Subject to that:
[Ask your lawyer to review this clause for each market you sell in. Courts and consumer laws in many countries limit how far it can apply.]
If you're a consumer, you have legal rights under the laws of the country where you live that these Terms can't take away. Nothing in these Terms affects those rights. For example, consumers in the EU and UK usually have a right to cancel certain online purchases, and consumers in Australia have automatic rights under the Australian Consumer Law. See our [Refund and cancellation policy] for details.
[Business customers only. Delete or limit for consumers after advice.] If you use the Service for business, you agree to compensate us for reasonable losses and costs arising from a third-party claim that your content, or your use of the Service in breach of these Terms, infringes their rights or breaks the law.
These Terms are governed by the law of [country / state]. Disputes will be dealt with by the courts of [place], except that:
[If you are considering arbitration clauses or class action waivers, get specific advice. Their enforceability varies widely, and some consumer laws prohibit them.]
We may update these Terms to reflect changes in the Service, our business or the law. We'll tell you about significant changes [by email or in the Service] at least [30] days before they take effect, unless a change is required sooner by law or is needed to address a security risk. If you keep using the Service after the change takes effect, the new Terms apply. If you don't agree, you can close your account before then [and receive a pro-rata refund for any prepaid period].
Starting point, not legal advice. Laws differ by country, and in the US and Canada by state and province. This guide helps you work out which documents to prepare and what to ask a lawyer. Have a qualified lawyer review your final documents before you rely on them.
Answer the questions below for your business as it is today and as you expect it to be in the next year. Each "yes" points to a document in this pack and to the sections in it that matter most.
Business: ______________________ Completed by: ______________ Date: ____________
---
| Question | If yes, you need | Pack file |
|---|---|---|
| Does your website or app collect any personal data at all, including email addresses, contact forms, account details, IP addresses in logs or analytics? | A privacy policy | privacy-policy.md |
| Do you use cookies, local storage, pixels or similar technology that isn't strictly needed to deliver the service? | A cookie notice and, in many countries, a consent banner | cookie-notice.md |
| Do people create accounts, buy from you or use an online service you provide? | Terms of service | terms-of-service.md |
| Do you sell anything to consumers? | A refund and cancellation policy | refund-policy.md |
| Can users post content, send messages, upload files or use your service to reach other people? | An acceptable use policy | acceptable-use-policy.md |
| Do you use outside services that handle personal data for you (hosting, email, analytics, payments, support tools)? | A record of processing and contracts with those providers | data-processing-checklist.md |
| Are any of the above already published? | A maintenance routine and version history | policy-maintenance.md |
Almost every online business needs at least a privacy policy. A contact form or a mailing list is enough to make it necessary.
Laws usually follow where your customers or users are, not only where your company is based. Tick every region where you have, or are aiming for, real customers.
| Region | Main rules to know about | Check |
|---|---|---|
| European Union and EEA | GDPR for personal data. The ePrivacy rules, as applied in each country, for cookies and marketing emails. The Consumer Rights Directive for cancellations and refunds. | [ ] |
| United Kingdom | UK GDPR and the Data Protection Act 2018. PECR for cookies and electronic marketing. The Consumer Contracts Regulations 2013 and the Consumer Rights Act 2015. | [ ] |
| California | CCPA as amended by CPRA, if your business meets its thresholds. California's automatic renewal law for subscriptions. CalOPPA requires a privacy policy for commercial websites that collect personal information from California residents. | [ ] |
| Other US states | A growing number of states have their own comprehensive privacy laws with different thresholds and rights. COPPA applies nationwide to services aimed at children under 13. | [ ] |
| Canada | PIPEDA for private-sector organisations in most provinces, with separate provincial laws in some, including Quebec. CASL for commercial electronic messages. | [ ] |
| Australia | The Privacy Act 1988 and the Australian Privacy Principles, for businesses it covers. The Australian Consumer Law, including automatic consumer rights that a refund policy can't remove. | [ ] |
| Elsewhere | Many countries have privacy and consumer laws modelled on the ones above. List them here: [Countries]. | [ ] |
If you tick more than one region, write your documents to meet the strictest standard that applies, then add region-specific sections where the rules differ. The templates in this pack are set up that way.
Answer yes or no. A "yes" means a specific section needs extra care.
| Question | Yes / No | What it affects |
|---|---|---|
| Do you collect data about children, or is your service likely to attract under-18s? | [ ] | Children section of the privacy policy. Possibly parental consent, age checks and a child-focused design review. Get advice. |
| Do you collect health, biometric, financial, precise location, religious, political or sexual orientation data? | [ ] | Sensitive data rules in GDPR and many US state laws. Usually needs explicit consent or another specific condition. |
| Do you share or sell personal data for advertising, or use third-party ad pixels? | [ ] | Opt-out rights under CCPA/CPRA and other US state laws ("sale" and "sharing"), cookie consent in the EU and UK. |
| Do you send marketing emails or texts? | [ ] | Consent and unsubscribe rules. Privacy policy section on marketing. |
| Do you make automated decisions that significantly affect people, such as approvals or pricing? | [ ] | GDPR rules on automated decision-making and profiling. |
| Do you use AI features that process user content? | [ ] | Privacy policy: what data goes to which provider, whether it is used for training, how long it is kept. |
| Do you store data outside the country where your users are? | [ ] | International transfers section. Transfer safeguards such as standard contractual clauses. |
| Do you offer subscriptions that renew automatically? | [ ] | Renewal terms, reminders and cancellation method in the terms and refund policy. |
| Do you sell digital downloads or online access? | [ ] | The digital content wording in the refund policy and your checkout. |
| Do you let users post public content or message each other? | [ ] | Acceptable use policy, content licence in the terms, a way to report content. Some countries have specific online safety and notice-and-action rules. |
| Do you sell to businesses only? | [ ] | Consumer rules may not apply, but you still need privacy and terms. B2B customers will often ask for a data processing agreement. |
| Do you process personal data on behalf of your business customers? | [ ] | You are likely a processor for that data. Offer a data processing agreement. |
Copy the outcome here so it becomes a plan.
| Document | Needed? | Owner | Draft by | Lawyer review by | Published |
|---|---|---|---|---|---|
| Privacy policy | [ ] | [Name] | [Date] | [Date] | [ ] |
| Cookie notice and banner | [ ] | [Name] | [Date] | [Date] | [ ] |
| Terms of service | [ ] | [Name] | [Date] | [Date] | [ ] |
| Refund and cancellation policy | [ ] | [Name] | [Date] | [Date] | [ ] |
| Acceptable use policy | [ ] | [Name] | [Date] | [Date] | [ ] |
| Record of processing and processor list | [ ] | [Name] | [Date] | - | Internal |
| Data processing agreement for your customers | [ ] | [Name] | [Date] | [Date] | [ ] |
| Policy maintenance log | [ ] | [Name] | [Date] | - | Internal |
Policies describe what you actually do. If you write them from a template without checking, they will be wrong, and a wrong policy can be worse than a short honest one.
data-processing-checklist.md first. It tells you what data you hold, why, where and for how long.