Privacy policy writer
The privacy policy and terms every website is expected to have — written in plain English from a few questions, rather than copied off a competitor.
- It all happens here
- Every part runs in your browser. Nothing you type is uploaded, and it works with the internet off.
- No account, ever
- No sign-up, no email address, no trial that turns into a bill.
- Yours to use
- Nothing watermarked, nothing limited to a preview.
Your business
An address somebody actually reads. This is where a request to delete data arrives.
Decides whose law applies if there is ever a disagreement.
Genuinely optional. If you work from home, you are not obliged to publish where you live.
What your site collects
Tick what is true. Each one adds the disclosure it needs.
Who else handles it
The part copied policies always get wrong.
Separate with commas. Your website host, payment provider, mailing list, analytics. Naming them is what a regulator or a business customer checks first.
Records tied to a payment usually have to be kept for several years for tax reasons, whatever you choose here. The generated policy says so.
If you sell things
Only used for the terms of service.
Before you use this: This is a solid starting point, not legal advice. It covers what a straightforward website or shop normally has to disclose. If you handle health information, work with children, trade in several countries with different rules, or do anything unusual with personal data, have a lawyer read it — that is a short conversation, and much cheaper than the alternative.
Privacy policy
This business Effective 2026-08-16
This explains what information we collect, why, and what you can ask us to do about it. It is written to be read rather than to be long. If anything here is unclear, write to [your email address] and we will explain it properly.
Who we are
This business runs this website. You can reach us at [your email address].
What we collect
We collect your name, email address and whatever you write to us and anonymous information about how the site is used.
We do not collect anything we do not need, and we do not buy information about you from anybody else.
Why we collect it
We use it to answer you when you get in touch and understand which pages people find useful, so we can improve them. We do not use it for anything else, and we do not sell it. If we ever wanted to use your information for something new, we would ask first.
Who else sees it
Nobody outside this business, except where we are legally required to hand something over.
We will also share information if a court or the law requires it — and we will tell you if that happens, unless we are forbidden from doing so.
How long we keep it
We keep what you send us for about 24 months, unless we are legally required to keep it longer — records relating to a payment usually have to be kept for several years for tax reasons.
When we no longer need something, we delete it.
Cookies
A cookie is a small file the site asks your browser to keep. We use them for the things the site cannot work without — remembering you are signed in, keeping what is in your basket — and, if you agree, for counting visits so we can see which pages are useful.
You can clear or block cookies in your browser settings. Blocking the essential ones will break parts of the site; blocking the rest will not.
What you can ask us to do
You can ask us to show you everything we hold about you, to correct anything wrong, or to delete it. You can tell us to stop sending you email at any time, and every marketing email we send has an unsubscribe link in it.
Write to [your email address] and we will do it. We will not make you explain why, and we will not charge you.
Depending on where you live you may have further rights under laws such as the GDPR or state privacy legislation, and you may complain to your local data protection authority if you think we have got this wrong.
Keeping it safe
We take reasonable care: information is held on services that encrypt it, access is limited to people who need it, and we do not keep copies lying around. No one can promise perfect security, and anybody who does is not being straight with you. If something goes wrong in a way that affects you, we will tell you.
Changes
If we change how any of this works we will update this page and change the date at the top. If the change is significant, we will tell you directly rather than hoping you re-read it.
Last updated 2026-08-16.
Read it before you publish it
This is a statement about your business that you are responsible for. It is written to be short enough that reading it is realistic — which is the whole reason it is not nine pages.
Two things to check in particular: that the list of services you use is complete, and that the retention period matches what you actually do. Those are the two a regulator or an enterprise customer looks at first.
What this is, if you have never had to think about it
Most people arrive here having been told they need one of these, without being told what it is. Nothing below assumes you already know.
Why even a small site needs one
If your website has a contact form, an email signup, an analytics tag or an online shop, you are collecting information about people — and most privacy law is built on the principle that people are entitled to be told what you collect and why. A policy is how you tell them. It is also the first thing a payment provider or a business customer asks for, so its absence tends to become a problem at the worst moment.
What has to be in it
What you collect, why you collect it, who else sees it, how long you keep it, and how somebody asks you to delete it. Then how to contact you about any of that. That is the substance. A policy that runs to nine pages of definitions usually contains the same five answers, buried, and buried is closer to hiding than to disclosing.
The version everybody skips
Copying a competitor’s policy is the standard move and it is a genuinely bad one — you inherit their tools, their retention periods and their legal jurisdiction, and end up with a document describing somebody else’s business. Worse, it names services you do not use and omits the ones you do, which is precisely the thing a regulator or an enterprise customer checks first.
Questions people ask
Writing it once is fine. Remembering to change it is not.
Content publishes your policy as a real page with a proper address, keeps every previous version, and shows when it was last touched — which matters on the one page where “last updated 2019” is the whole problem.
