Skip to contentSellstamp

Privacy policy generator

Answer what your site collects, why and who you share it with, and get a privacy policy that says only what is true of your site, with optional GDPR and CCPA sections. A template, not legal advice.

This is a template assembled from the answers you gave. It is information, not legal advice, and no lawyer has reviewed it. Laws differ by country, state and industry, and requirements that apply to you may be missing from it. Have it reviewed by a qualified lawyer for your own jurisdiction and circumstances before you rely on it.

Street, city, postcode, country — plus a tax number, email or phone if the document needs one.

What you collect

Only the boxes you tick appear in the policy. A policy that lists data you do not hold is as wrong as one that omits data you do.

One per line. Photos customers upload, a date of birth, a VAT number — whatever the list above missed.

Who you share it with

Categories, not company names — that is what a reader needs, and it stays true when you switch providers.

Tick this only if it is true. Advertising and marketing pixels can amount to it in some places, so check before you decide it does not apply.

Left empty, the document prints a visible gap rather than inventing a period.

An email address, a form, or a postal address. This is the one thing a privacy policy has to make usable.

Adds the general rights that regime is known for, and states plainly what the template has not filled in — lawful bases, controller identity, transfer safeguards.

Same shape: the general rights, and a sentence saying that whether the law applies to you is not something this tool can determine.

Opens your browser’s print dialog, where Save as PDF is the destination on every desktop browser. Nothing you have typed leaves this tab.

We’ll send you tips and updates from Sellstamp. Unsubscribe any time.

Stays on your device

Everything runs in your browser. Nothing you type is sent anywhere unless you choose to email yourself the result.

Selling digital work?

Sellstamp takes payment into your own account and delivers files or licence keys automatically, so there is less paperwork to do by hand. Open a free store

How to use it

  1. Fill in your business name, website and the effective date.
  2. Tick the kinds of data you collect and why, and who you share them with.
  3. Say how long you keep data and where people send privacy requests; blanks print as visible gaps.
  4. Tick the GDPR or CCPA section only if those rules may apply to you, then save it as a PDF.

A template, not legal advice

This is a template assembled from the answers you gave. It is information, not legal advice, and no lawyer has reviewed it. Laws differ by country, state and industry, and requirements that apply to you may be missing from it. Have it reviewed by a qualified lawyer for your own jurisdiction and circumstances before you rely on it.

Why this one asks so many questions

Because a privacy policy is a statement of fact about your business, published to the people whose data it describes. A generator that hands you a finished policy without asking what you collect has written you a document that is false about your own site — it lists data you do not hold, omits data you do, and names recipients you have never used.

So the categories are checkboxes and the answers are yours. What you do not tick does not appear. Where the tool cannot know something — how long you keep records, where privacy requests should go — the document prints a visible bracketed gap rather than filling it in with something plausible.

Categories of recipient, not company names

The sharing section names “a payment processor” and “an analytics provider” rather than particular companies. That is the level a reader actually needs, and it is the level that stays true when you change providers. If you want to name them, add them yourself — some regimes expect it, and this template does not assume which one you are under.

The GDPR and CCPA checkboxes

Ticking one adds a clause describing the rights that regime is generally known for, in general terms, and a paragraph saying plainly what the template has not filled in — the lawful basis for each purpose, who the controller is, what safeguards cover transfers, whether the law applies to your business at all. Those are determinations about your specific circumstances, and this page is not in a position to make them.

Leave them unticked and no regime is mentioned. What this tool will not do, in either case, is call the result compliant with anything.

Questions

Is this privacy policy legally compliant?

This tool cannot tell you that. It writes a policy from your answers; whether it meets the law that applies to you is a question for a lawyer, especially if you handle sensitive data or sell into several countries.

Why does it ask so many questions?

Because a privacy policy is a statement of fact about your own site. One that lists data you do not collect, or misses data you do, is wrong in public.

Why are some parts left as gaps in brackets?

Where the tool cannot know the answer, such as how long you keep records, it prints a visible gap instead of inventing one, so you notice and fill it in.

Does it name the companies I share data with?

It names categories such as “a payment processor” and “an analytics provider”, which stay true when you change providers. You can add company names yourself; some laws expect them.

What do the GDPR and CCPA checkboxes add?

A clause describing the rights each regime is generally known for, in general terms, and a note of what the template has not decided for you, such as your lawful basis for each purpose.