№ 07 / SolutionsFree

  UK Privacy & Cookie Policy Generator

A policy that says what you actually do.

Answer a few questions, get a UK GDPR privacy policy and a PECR cookie policy built from them — purposes, lawful bases, retention, transfers and a cookie table included. Free, no signup, and your answers never leave this browser tab.

№ 01 — Your business

Who the policy speaks for.

Most UK businesses processing personal data must register with the ICO — check at ico.org.uk.

№ 02 — What you collect

Each selection adds its purpose, lawful basis and a sensible UK retention default.

№ 03 — Services you use

Drives the sharing section, the international-transfers table and the cookie policy in one go.

№ 04 — Anything unusual?

Fill in your legal name, website URL and contact email — the preview builds itself as you type.

Questions

Asked a lot

  • № 01

    Is it really free?

    Yes, with no catch and no signup. Generation runs entirely in your browser — your answers are stored locally on your machine and never sent to us. The business model is the scanner next door: once you publish the policy, you'll want to verify the live site matches it.

  • № 02

    Is this legal advice?

    No. The generator produces a solid, honest starting point built from your answers and current UK practice, and every document says so on its face. For complex or high-risk processing — health data, children's services at scale, large-scale profiling — have a professional review it.

  • № 03

    Do I need to register with the ICO?

    Probably. Most UK organisations processing personal data must pay the ICO data protection fee — exemptions are narrow. The check takes two minutes on ico.org.uk, and your registration number belongs in the policy, which is why the generator asks for it.

  • № 04

    How is this different from other policy generators?

    It is UK-only on purpose. Most generators are US-centric and treat UK GDPR, PECR cookie rules and ICO registration as an afterthought. This one generates from the same UK rules our compliance scanner checks against — so the policy it writes is the policy the scan expects to find.