Decides how visitor data is used
- chooses which consents to collect;
- sets the retention period;
- publishes the banner and policies;
- responds to visitor requests.
HOW COOKILOW HANDLES CUSTOMER DATA
You set the rules. CookiLow keeps the consent history.
You decide which choices your website needs and how long records should remain. We store the visitor’s decision, protect its history and help you find the right record.
Updated 24 September 2026 · CookiLow international service
YOUR CONTROLYou set the rules
OUR JOBStore and protect records
TRANSPARENCYEvery provider is listed
CURRENT STATUSPaid storage is not live yet
RESPONSIBILITIES
You decide why data is needed. We operate the system.
This makes it clear what remains your company’s responsibility and what you ask CookiLow to do.
Stores and confirms the visitor’s choice
- records the visitor’s decision;
- protects the history from silent replacement;
- helps find and export the record;
- deletes data under the agreed rules.
WHAT HAPPENS TO A RECORD
Four clear stages — from choice to deletion.
You can see what happens at each stage and what your team can do with the record.
- 01A visitor makes a choice
CookiLow records the decision, event time and version of the banner they saw.
- 02The record is stored
It exists to confirm the choice, not to advertise CookiLow to the visitor.
- 03You control the record
The workspace will let you find, review and export the stored event.
- 04Data is removed when you leave
You receive an export window before remaining records are deleted on schedule.
WHAT WE COMMIT TO
Customer data is used only to run the service.
No hidden advertising purpose. Finding a record, answering a visitor or leaving CookiLow should follow a clear process.
No use for our own purposes
CookiLow stores consent records for your website and follows the instructions agreed with you.
No unnecessary access
Only people and services needed to operate CookiLow can reach customer records.
Help with visitor requests
You can find, export or delete a record when a visitor asks about their data.
Clear incident handling
If an incident occurs, we investigate it, notify the customer and support the required response.
Named service providers
Before onboarding, you can see which providers support CookiLow and what data they may process.
A clear data exit
You can export available records before remaining customer data is deleted on the agreed schedule.
WHO ELSE SUPPORTS THE SERVICE
Review every CookiLow provider before onboarding.
For hosting, email and other operational providers, we will show the company, its job, its location and whether it can process customer data.
Who supports CookiLow and why the provider is needed.
Exactly what the provider may access or process.
The country where the provider works or stores information.
Which protection applies when data leaves the EEA.
How and when customers hear about a new provider.
BEFORE PAID ONBOARDING
Read the terms before CookiLow stores customer data.
Production processing will not begin until customers can review the DPA, security measures, provider list, retention schedule and data exit process.
Request the documents