Guides
Privacy, cookies and consent
What the snippet stores in visitors' browsers, how to load it after consent, and deleting data.
For data about your visitors, you are the controller and LiftCanary is your processor. Our Data Processing Agreement is part of the Terms of Service you accepted at signup. This page lists what the website snippet stores in your visitors' browsers, so you can add it to your own cookie policy, and how to run it only after consent.
What the snippet stores#
One first-party cookie on your own domain (two with LiftCanary's consent banner), and browser storage. No third-party cookies, and nothing that identifies a person unless you send a user id.
| Name | Where | Purpose | Kept for |
|---|---|---|---|
liftcanary_anon | Cookie (first party) | A random id, so a visitor sees the same variation on every visit | 2 years, renewed on each visit |
liftcanary:anonymous_id | localStorage | Copy of the same id (the cookie wins) | Until cleared |
liftcanary:identity, liftcanary:linked | localStorage | The signed-in user you told the snippet about, and whether it was linked to the anonymous id | Until logout or cleared |
liftcanary_consent | Cookie (first party) | The visitor's answer to LiftCanary's banner (only with data-consent="banner"); no id in it | 6 months |
liftcanary:first_seen | localStorage | New or returning visitor | Until cleared |
liftcanary:datafile:*, liftcanary:events:* | localStorage | Last copy of your experiments' settings, and events not sent yet (at most 200) | Until cleared |
liftcanary:reported | localStorage | Exposures already sent to an analytics tool (only with first exposure only) | Until cleared |
liftcanary:utm, liftcanary:session_new, liftcanary:geo, liftcanary:redirect, liftcanary:preview, liftcanary:editor | sessionStorage | This visit's UTM tags and location, redirect loop protection, preview and editor mode | Until the tab closes |
Events the snippet sends hold the anonymous id (or your user id), the experiment and variation, goal events and their values, and the browser, device, language, page, referring domain, UTM tags and country/region/city. IP addresses are used during the request (rate limits, location) and not stored with events. Events are deleted after 400 days, when you delete the project, or when the organization is deleted. An ended experiment's results are kept as totals per variation (counts and sums, nothing about any one visitor) for as long as the experiment exists.
Consent#
Recognising a returning visitor for A/B testing generally isn't "strictly necessary" under the EU ePrivacy rules, and the Turkish data protection authority's cookie guidance asks for consent for analytics and personalisation cookies. Both cover anything stored on or read from the visitor's device, so local storage needs consent just like a cookie. Unless your lawyer tells you otherwise, run the snippet in one of these ways.
Ask with LiftCanary's banner#
For a site without a cookie banner. Add data-consent="banner" to the script tag (the install page's default) and the snippet asks each visitor with a small banner of its own, before anything is stored:
<script src="https://cdn.example.com/sdk/v1/liftcanary.js" data-sdk-key="pk_…"
data-consent="banner" data-privacy-url="/cookie-policy"></script>
<!-- Optional while the cookie button is on: another way to change the answer -->
<a href="#" onclick="liftcanary.showConsent(); return false">Cookie settings</a>- Design it under Project → Consent banner, with a live preview: position, light, dark or following the page, the buttons' colour, corners, your site's font, the link to your cookie policy, and your own wording in any language. Saving publishes it; sites show it on the next page view, without changing the snippet.
- Reject and Accept always look the same and sit side by side, whatever the design: refusing is as easy as accepting.
- After an answer, a small cookie button stays in the corner and opens the banner again: visitors must be able to change their mind. It's on by default; if you turn it off, link
liftcanary.showConsent()from your footer instead. - The text follows the page's
<html lang>: LiftCanary's wording in English, Turkish, German, Spanish, French, Italian, Dutch and Portuguese, or yours.data-privacy-urlon the script tag wins over the cookie policy link set in the dashboard. - The answer is kept in the
liftcanary_consentcookie for six months, then the banner asks again. Until the visitor answers, the snippet behaves as described in the table below. - The banner (about 3 KB) loads only for visitors who haven't answered, never in the visual editor.
Wait for your consent manager#
If your site already has a cookie banner, add data-consent="required" to the script tag (My cookie banner on the install page), and tell the snippet what the visitor chose from your consent manager (CMP):
<script src="https://cdn.example.com/sdk/v1/liftcanary.js" data-sdk-key="pk_…" data-consent="required"></script>
<script>
// In your consent manager's callback; calling it on every page is fine.
liftcanary.consent(true); // accepted
liftcanary.consent(false); // refused, or consent withdrawn
</script>| Before consent | consent(true) | consent(false) | |
|---|---|---|---|
| Cookie and browser storage | Nothing read or written | The visitor's id is stored (an id from an earlier visit is kept) | Nothing stored; what LiftCanary stored before is removed |
| Events and exposures | Held in memory, not sent | Held events are sent, then as usual | Dropped; nothing sent |
| Analytics integrations | Not told | Told about held exposures, then as usual | Not told |
| Tests | Run for this page view with an id in memory | As usual | Show the original, as to visitors outside the test's traffic |
| Flags, shipped winners and personalizations | Run for this page view with an id in memory | As usual | Run for this page view only |
Visitors who haven't decided yet still see your experiments, but each page view gets a new random id, so a multi-page test can show them a different variation on the next page until they accept. Call consent() as early as your consent manager allows (it can be called through the stub before the SDK loads) so returning visitors get their id back before anything is decided.
Visitors who refused never count in results, so tests leave them alone: they see your original pages, as visitors outside a test's traffic do, and redirect tests don't send them anywhere. Rollouts, shipped winners and personalizations still apply to them. With LiftCanary's banner this starts on the first page, since the answer is remembered; with your consent manager, as soon as it calls consent(false), and what the page already shows stays until the visitor moves on.
Load the snippet only after consent#
Stricter: nothing of LiftCanary runs until the visitor agrees. Put the script in the same category as your analytics:
<!-- The consent manager turns this into a real script once "analytics" is accepted -->
<script type="text/plain" data-category="analytics"
src="https://cdn.example.com/sdk/v1/liftcanary.js" data-sdk-key="pk_…"></script>Until then, visitors see your original pages and aren't counted. Leave out the anti-flicker style in this setup: it would hide the page for nothing.
Cookie notice#
If you'd like the snippet in your cookie notice, a short version is:
We run experiments with LiftCanary to improve this site. For that, a random id is stored in your browser; your name and contact details aren't sent to LiftCanary, which processes this data only on our behalf.
A visitor's access or deletion request#
Project settings → A visitor's data (admins): enter the visitor's anonymous id (the liftcanary_anon cookie, or liftcanary.userId() on their browser) or the user id you send. You see what's stored (exposures and events, first and last seen, and the ids linked to it when they signed in), and can delete it all. Deletion covers every environment of the project and every linked id, finishes within a few minutes, and is recorded in the audit log without the ids. The same through the API: GET and DELETE /v1/projects/:project/visitors/:id. Deleting the project or the organization deletes all of its events.
Your account's data#
How we handle your own account (name, email, sign-in logs) is in the KVKK notice and the Privacy Policy. You can delete your account under Settings → Profile → Delete account: organizations where you're the only member are deleted with it, with their projects and collected events. If you're the only owner of a team, make someone else owner first. See also Team.