Small tool, nothing hidden.

One script, published in the open

PlainConsent is a single small script. Its source code is published, so anyone (you, your developer, a regulator) can read exactly what runs in your visitors' browsers. There is nothing to take on trust.

Zero third-party calls

The script does not phone home. It calls no server of ours and no server of anyone else. Your visitors' data never leaves your page to ask whether it may be collected. A consent tool that tracks people would be the very thing it is meant to prevent; this one does not.

Consent is stored where it belongs: with you

Each visitor's choice is saved in a first-party cookie on your own domain. By default that record never reaches us.

Proof you can hold

Every fresh decision gets a unique consent ID and a standardised audit record: the ID, a timestamp, the policy version, and the choice per category. You can log that to your own endpoint, so if a regulator asks, you have the receipts. GDPR Article 7 puts the burden of proof on you, so we make the proof easy to keep.

Tracking stays off until consent

Through Google Consent Mode v2, tracking defaults to "denied" before anything loads. Nothing fires until your visitor agrees.

Built like it matters

Every release goes through an automated test suite, an independent security review, and a mechanical quality check before it is published. Versioned files are byte-pinned with Subresource Integrity (SRI), so the code you approved cannot be swapped for something else without detection.

You can host it yourself

Load the script from us over HTTPS, or self-host it on your own domain. Self-hosting means not a single byte of visitor data touches our infrastructure.