GDPR pack · one payment · self-hosted

GDPR pages and a cookie banner you pay for once.

Answer a short wizard, download a ZIP: a privacy policy, a cookie policy and a cookie-consent banner that runs from your own server and makes zero third-party requests. English or Czech. No subscription, no account.

Generate my pack · $29 once

You read your full privacy policy before you pay. Not legal advice; see the FAQ.

acme-store.example

Theme

Position

Language

What cookie-banner.js is doing in that frame, read live

consent cookie: none yet. Pick an option in the banner.
analytics script: blocked tagged type="text/plain"
marketing script: blocked tagged type="text/plain"
Consent Mode v2: waiting for the banner
third-party requests: measuring

§ 1

Unzip it and this is what you have.

The pack below was generated by the same code that builds yours, for a made-up shop called Acme Store Ltd. Click through the files.

goodcookie-acme-store.example.zip

Privacy Policy

Who the controller is, what data is collected, purposes and legal bases as a table, retention, recipients, international transfers and every GDPR data-subject right. Sections appear or drop out depending on what you tick in the wizard. It is one standalone HTML file with inline CSS, so it loads nothing external.

Highlighted = filled in from the wizard answers.

Privacy Policy, as Markdown

The same document as source, for pasting into a CMS, a docs site or your repo.

Loading the sample…

First lines of the sample file.

Cookie Policy

Cookie categories, a starter cookie table, the legal basis, and how visitors change or withdraw consent. It branches on analytics, marketing and payments. You get it as standalone HTML and as Markdown; the Markdown source is shown here.

Loading the sample…

First lines of the sample file. The cookie table is a starting point: check it against a scan of your live site.

The cookie banner

One JavaScript file: your configuration at the top, the consent engine below it. No build step, no dependency, no network calls. This is the file running in the demo at the top of this page.

Loading the sample…

First lines of the sample file.

Integration README

Publish the pages, add one script tag, tag your analytics and marketing scripts so they stay blocked until consent, add a “Cookie settings” link.

Loading the sample…

First lines of the sample file.

§ 2

The banner is a file on your server, not a service.

Most consent tools are a script loaded from someone else's domain, billed monthly. This one is a single file you host.

Zero external requests: Config is baked into cookie-banner.js. Consent is stored in a first-party cookie, goodcookie_consent, for 12 months. Nothing is sent anywhere.
Blocks the scripts you tag: Tagged analytics and marketing scripts stay inert until the visitor agrees to that category. After “Accept”, the banner switches them on without a page reload.
Reject is one click: “Reject all” sits on the first layer right next to “Accept all”, as a full button rather than a buried link. Categories are granular and nothing non-essential is pre-ticked. Visitors can reopen it any time from a link you add.
Google Consent Mode v2: Sets every Google consent signal to denied by default and updates it after the visitor chooses. Relevant only if you use Google tags.

Install, from the README

<!-- 1. in <head>, as early as possible -->
<script src="/cookie-banner.js"></script>

<!-- 2. tag what needs consent -->
<script type="text/plain"
        data-cookie-category="analytics"
        src="https://example.com/analytics.js"></script>

<!-- 3. let visitors change their mind -->
<a href="#"
   onclick="GoodCookieConsent.showBanner();return false">Cookie settings</a>

§ 3

How it works

1
Answer the wizard
Your details and what your site actually does: analytics, marketing, newsletter, accounts, shipping, payments. A few minutes.
2
Read your policy, free
The full generated privacy policy is shown before any payment, so you know what you are buying.
3
Pay once, download
Stripe Checkout, then a ZIP with every file. No account to create. Host the files wherever your site lives.

§ 4

One payment. Then the files are yours.

Subscription cookie-consent tools typically run $6–$199 a month. This is one payment for files you keep, edit and host yourself.

The trade-off, stated plainly: it does not update itself when the law changes. If your details change, generate a new pack.

Good Cookie Pack

Privacy PolicyHTML + MD
Cookie PolicyHTML + MD
Cookie-consent bannerJS, self-hosted
Data-request pageHTML
Integration READMEMD
LanguageEnglish or Czech

Monthly feenone

Total, once$29

Generate my pack

Pay after you have read your privacy policy.

§ 5

Generate your pack

Four short steps. You preview the privacy policy before paying.

Your site

Language of the pack Site type Website URL Effective date

Your organization (the data controller)

Name / company Contact email Registered address Company / reg. no. (opt.) VAT number (opt.) Phone (opt.)

We have appointed a Data Protection Officer

What your site does

Tick what applies. Each one adds or removes sections in the policies and categories in the banner.

Uses analytics (e.g. Google Analytics) Uses marketing / ad cookies (e.g. Meta Pixel, Google Ads) Sends a newsletter / marketing emails Has user accounts / login Ships physical goods Processes card data directly (not via a redirect/hosted gateway) Uses preference/functional cookies (language, theme…)

Providers and banner

Providers are optional; naming them makes the policy more specific.

Hosting provider Email provider Banner theme Banner position

§ 6

Questions, answered straight

Is this legal advice?

No. Good Cookie Pack generates customizable templates and a consent widget from your answers. It's for general information only, is not legal advice, and does not guarantee compliance. Review the result with a qualified lawyer for your situation.

Do I own the files?

Yes. You download the source files and host them yourself. There's no subscription and nothing phones home. Edit them however you like.

Does the cookie banner send data anywhere?

No. cookie-banner.js makes zero external requests. Consent is stored in a first-party cookie on your visitor's browser. If you use Google tags, it emits Google Consent Mode v2 signals locally.

Does it actually block cookies before consent?

Yes, for scripts you tag. Change your analytics/marketing <script> tags to type="text/plain" with a category (the README shows exactly how); the banner re-activates them only after consent. Google tags are additionally gated by Consent Mode v2.

Is the banner GDPR-friendly?

It's built to the EDPB banner expectations: granular categories, “Reject all” on the first layer next to “Accept all”, no pre-ticked non-essential boxes, and withdrawal anytime via a settings link. Final compliance still depends on how you deploy and configure it.

Does it auto-update when the law changes?

No. It's a one-time pack you own. That's the trade for no subscription. Regenerate anytime your details change.

Can I see it before paying?

Yes. Fill the wizard and you'll get a full preview of your privacy policy for free. You pay only for the complete pack.

Does this page track me?

No analytics, no third-party scripts, and the fonts are served from this server. The banner demo at the top sets one goodcookie_consent cookie if you click a choice in it, which is the banner doing its job. Your wizard answers are stored on the server so your pack can be built.

GDPR pages and a cookie banner you pay for once.

Privacy Policy

Privacy Policy, as Markdown

Cookie Policy

The cookie banner

Banner test page

Data-request page

Integration README

Answer the wizard

Read your policy, free

Pay once, download