What the scan sees
Only the public page and services loaded in an ordinary visitor’s browser.
No CMS password, private dashboard or analytics account is needed.COOKILOW SECURITY
Scan a website without passwords or admin access.
The first scan needs only a website address. CookiLow shows which services start before consent and, after onboarding, keeps the visitor choice history.
No sign-up · No website password · No analytics accessFOR THE SCANOnly the website address
IN THE RECORDChoice, banner version and time
COMPANYDIGITAL GROUP AS · Norway
SUPPORThello@cookilow.com
WHAT WE RECEIVE
CookiLow does not ask for more data than it needs.
See what the public scan reads and what the service will store after a customer connects their website.
What stays in your workspace
Your websites, scan results, settings and support history.
The workspace opens only after an authorised user signs in.What a consent record contains
The visitor’s choice, banner version, event time and a pseudonymous record ID.
Enough context to confirm the choice later without storing the page content.HOW DATA IS PROTECTED
Keep the history. Keep other people out.
When a visitor changes their choice, both records remain visible. Only an authorised workspace user can find or export them.
Keep the change history
When a visitor changes their choice, the earlier record stays and a new event is added.
Keep other people out
Customers see their own websites. Sensitive actions require a signed-in account.
Send data over HTTPS
The website and public API use protected connections that are checked after every release.
Keep recoverable backups
Backups and release checks help restore the service after a technical problem.
WHAT THIS GIVES THE CUSTOMER
Less manual work. Fewer unnecessary logins.
The first check runs without installation. After onboarding, the useful records and documents stay together.
No password handover
The first scan runs from the public website address. CookiLow does not ask for a CMS login.
Confirm a visitor’s choice
Find a record by its ID or date and export it when a visitor asks a question.
Keep the documents together
Privacy, processing and service documents remain available on the CookiLow website.
Still have a security question?Write to us and we will answer in plain language.
Ask a questionSERVICE READINESS
See what works now and what is still being prepared.
Paid accounts will open only after billing, cancellation, export and deletion have passed the full release test.
Public pages are checked without CMS credentials.
The website and public API use protected transport.
The DPA, security measures, provider list and retention periods will be published.
Sign-in, billing, cancellation, export and deletion will pass an end-to-end test.
About certification: CookiLow does not currently hold ISO 27001 or SOC 2 certification. If that changes, the supporting documents will be published here.
DOCUMENTS
All the rules stay together.
Read what data CookiLow receives, how this website uses cookies and what the service is responsible for.
Verify DIGITAL GROUP AS in the Norwegian register ↗DOCUMENTPrivacy notice
How account, scan and service information is handled.
Open →DOCUMENTCookie policyWhat the CookiLow website stores and when.
Open →DOCUMENTData processing termsRoles, instructions and safeguards for customer processing.
Open →DOCUMENTTerms of serviceService scope, responsibilities and launch boundary.
Open →IF YOU FIND A PROBLEM
Email the teamTell us and we will investigate.
Email hello@cookilow.com with the page and a short description of what happened. Do not send passwords or personal data.