Protected connections
Connections to our dashboard, cookie banners and service are encrypted with HTTPS. This protects data while it travels between your browser and ConsentCook.
Stored data
The disks holding our live database are not encrypted. Encryption of website connections does not protect data stored on those disks.
Access to your account
You can turn on two-step sign-in for your account. Team permissions control who can view, change and publish your settings, and access checks restrict private workspace data to its members.
Checking your banner settings
We digitally sign published banner settings. The banner checks that signature before using them and rejects settings if the check fails.
Evidence of visitor choices
New consent records are digitally signed when saved, so later changes can be detected. You can export them from Reports and check their signatures independently. Older records created before signing was introduced remain unsigned.
A record of important actions
We record administrative actions in an audit log. Existing entries cannot be edited through the application. Controlled deletion is allowed when an account and its data are erased.
Backups and recovery
We make encrypted offsite backups each night. Our check on 8 October 2026 confirmed a successful backup that day and a successful database restore test on 1 October. We have not yet measured how long a complete service recovery takes.
Protection against excessive requests
We limit how often public requests can be made to help reduce abuse. We do not currently use a dedicated web application firewall, an extra layer that filters potentially harmful traffic.
If something goes wrong
Our incident procedure covers investigating problems, restoring service and telling affected customers. We are a small team working UK business hours, without round-the-clock support. Our procedure calls for a status update within 30 minutes of confirming a serious incident and an email to affected customers the same day.
Keeping and deleting records
An automatic job removes consent records after our configured retention period. We also support requests to erase records linked to a visitor’s anonymous identifier. This does not identify that person or delete their data from other services.
Where your data is kept
Our application and live database are hosted in the United Kingdom. Offsite backup storage is in the Netherlands. You cannot currently choose a different hosting region. Our list of service providers explains who else handles data.
Independent security testing
We have not completed an independent penetration test — a specialist attempt to find ways into the service. Our own automated checks are not a substitute for that assessment.
Trust
Security
How we protect your account and consent records, and where our protection has limits.
Questions or concerns?
Read more about your data or tell us about a security problem.
Who handles your data
The companies we use to run the service and what they do.
Service status
Whether ConsentCook and its main parts are working right now, with the time of the last check.
Report a security problem
Found something that could put data at risk? Please tell us privately.