A form for each site
Name, email address, what the person wants, where they live and, if your banner shows it, their consent ID.
Every request, answered by you.
Give each site a privacy request form and an inbox with suggested deadlines. Find every consent record of one visitor from their consent ID, and show visitors under an opt-out rule, such as California's, that their browser's opt-out was honoured.
On every plan. The form and the consent ID line are off until you turn them on.
How it works
The request reaches you only after the person confirms their email address. From then on it is in your inbox, with a suggested deadline, until you close it.
1, The person
From a link in your privacy policy, your banner's preferences or anywhere you paste it.
2, Kukie.io
One email with a link that works once, for 24 hours. A request nobody confirms is deleted.
3, Kukie.io
The request lands in Privacy Requests, and owners and admins get an email that names the site, not the person.
4, Your team
The consent ID, if the person gave one, finds their records in the Consent Log, ready to export or delete.
5, Your team
From your own email. Mark it Completed or Declined, and the 24-month clock for deleting it starts.
The confirmation link proves only that the person controls the email address. Before you send anyone personal data, check that they are who they say they are. California's rules do not allow that kind of check before a business stops selling or sharing, so keep the banner's Do Not Sell link on your US rules as well.
What the person sees, what your team works with and what the banner shows. Each card opens the guide for that part.
Who does what
Under the laws Kukie.io's region rules cover, the business answers a privacy request. Kukie.io runs the form and keeps the inbox, and never replies for you.
Deadlines
Each request gets a suggested deadline from the country the person chose on the form, counted from the day they sent it. The GDPR, for example, gives one month, which can be extended by two more for complex or numerous requests1.
It is a suggestion. The law that applies to your business decides the real deadline, so change the date in the inbox where it differs.
Suggested deadline, in calendar days
Consent ID
Under the GDPR, a business that relies on consent must be able to show it was given. Every record in your Consent Log has a consent ID, and one ID is now enough to find the rest.
Turn on Show the visitor's consent ID in the Banner Editor, on the Preferences modal tab. Once a visitor has made a choice, and while the consent log is on, the end of the banner's preferences shows the ID of their latest choice, a Copy button and "Quote this ID if you contact us about your consent." in the banner's language. It is off for every site until you turn it on.
In the Consent Log, Find a visitor's records takes the ID and finds that record, then every record from the same browser on your site, newest first. It searches back one month at a time to the oldest record your site still holds, shows its progress, and can be stopped.
Everyone with access to the site can search, as everyone can read the Consent Log. Owners and admins of the organisation can export and delete.
The CSV has the Consent Log export's columns plus the browser ID, the user agent hash and the Consent Mode state, so it holds the whole of each record.
One confirmation deletes every record of that browser on the site, even when there are more than the 1,000 the list shows. Export first if you might need them.
Each export and deletion is noted in Kukie.io's audit log with the time and the number of records, but not the consent ID. Keep the ID with your own record of the request.
A new consent ID is made every time a visitor saves a choice, and your own scripts receive it in the cc:consent-updated event.
Records from another browser or device, or from before the visitor cleared their storage, have another browser ID and are not found. Several people can share one browser.
Learn more about consent records Read how to find a visitor's records
Global Privacy Control
Global Privacy Control is a signal a browser sends to say its user does not want their personal information sold or shared. California's regulations treat it as a valid opt-out and ask the business to show that it was processed.
"A business must display whether it has processed the consumer's opt-out preference signal as a valid request to opt-out of sale/sharing on its website."2
It works on any region rule with one of those models, wherever Respect Global Privacy Control is on in the Banner Editor's Behaviour tab, which it is by default. On the Agency and Unlimited plans, new sites start with ready-made rules for the United States and California that use them. On other plans, add a US rule with one of those models.
Learn more about region rules Read how to set up the Do Not Sell link
Data
Someone who sends a request may never have visited your site. The Data Processing Agreement names them as Requesters and describes what the form stores and for how long.
| Data | What happens to it |
|---|---|
| The request | Name, email address, the request type, where the person lives, the country detected from their connection when it lies in the region they chose, their details and an optional consent ID. A daily clean-up deletes it once 24 months have passed since you closed it. |
| A request nobody confirms | Never shown in your inbox. The daily clean-up deletes it once its 24 hours have passed. |
| IP address | Not stored with the request. |
| Your notes and status | Seen only by the owners and admins of the organisation, never by the person, and deleted with the request. |
| The emails to your team | They name the site, the request type and the suggested deadline, not the person. |
| Deleting the site | Deletes every request of that site at once. |
The Data Processing Agreement, the Terms and the privacy policy describe this processing. No new sub-processor is involved.
Help Centre
Turn on the form, link to it, work through a request and export the list.
Find one visitor's records, export or delete them, and show visitors their consent ID.
The link, the dialog and how Global Privacy Control is recorded and shown.
Read the consent ID in your own scripts from the cc:consent-updated event.
Turn on the form, link it from your privacy policy and your banner, and every confirmed request arrives in one inbox with its deadline.
Requests lead to consent records, policies link to the form, and region rules decide where Global Privacy Control applies.
Consent rates and records
Cookie and privacy policies
A banner rule for each region
What each kind of request asks of you, under the GDPR and Brazil's LGPD, and the announcement of these tools.
Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.