The policy describes the site you actually run
The common privacy failure is not malice. It is a policy written once, a tag added later, and nobody connecting the two. Then somebody complains, and the document is the evidence against you.
Nothing loads before consent
Where a site uses analytics or advertising, none of it runs until a visitor agrees. The consent choice is recorded, and the region determines how the question is asked: prior consent where that is required, opt-out with a respected Global Privacy Control signal where that is the standard.
- No third-party request fires before a grant, verified in an EU-geography test.
- Global Privacy Control is honored where it applies.
- Withdrawing consent is as easy as giving it.
One declaration produces the cookie table
Every vendor is declared once. That single declaration produces the recipients in the privacy policy, the rows of the cookie table, the categories the banner offers, and the origins the content security policy permits. A vendor cannot be present in one and missing from another.
- Adding a vendor updates four documents at once, or fails.
- A tag for an undeclared origin is blocked by the browser, so the cookie table cannot quietly stop being true.
Requests are answered on time
Access and deletion requests arrive through a form on your site, are logged with the policy version that governed them, and are answered inside the statutory deadline. Deletion is carried out across the stored record rather than marked as done.
- Every request is recorded with its date, so the clock is visible.
- Retention is enforced by the storage itself, and what was deleted is logged.
What you can show
- A consent log showing what was asked and what was chosen.
- A monthly count of requests received and answered within the deadline.
- A privacy policy and cookie table built from the same declarations the site is checked against.