Privacy and data
What the script keeps in a visitor's browser, what is saved with a lead, the consent and tracking settings, how long leads are kept and how to erase a person.
This article says plainly what Tafsee Popup stores and where. It is not legal advice. Your own privacy policy should mention the popups you run.
What the script keeps in the visitor's browser
The script sets no cookies. It uses the browser's own storage, for your website only:
- Local storage, one entry per website (its name starts with tafsee:v:). It holds a random visitor id, the date of the first visit, the number of visits and page views, pages visited, and for each campaign: when it was shown, closed or signed up on, the game prize won, and the A/B version this visitor gets.
- Session storage, one entry per website (its name starts with tafsee:s:). It holds this visit only: where the visitor came from, the UTM tags and the first page of the visit. It is gone when the tab is closed.
This is what makes frequency rules work: "once a week", "not again after they sign up", "one play per visitor". If a visitor clears their browser data, they are a new visitor.
What is saved with a lead
- What the visitor typed in your form, and their answers to surveys and quizzes.
- Consent: whether it was given, when, and the wording they agreed to.
- Where it came from: campaign, page address, device, country, and the source or UTM tags of the visit.
- The discount code they were given.
- The IP address, unless Anonymise IP addresses is on, in which case part of it is hidden before it is saved.
Consent
- Add a Consent field to a form to ask for agreement. See Consent and the privacy line.
- GDPR mode: Adds a required consent box to any form that asks for an email and does not already have one.
- A lead without consent is marked so in the list, and you can filter by it. Leads who opted out are left out of exports unless you include them.
Do Not Track
Respect Do Not Track: Visitors whose browser sends Do Not Track or Global Privacy Control see no campaigns and are not counted.
Target EU visitors differently
The condition EU visitors (GDPR) lets a campaign show only inside or only outside the EU, for example a version with a consent box for EU visitors. See Location and traffic source.
How long leads are kept
Lead retention (days): Keep forever unless your privacy policy says otherwise. Older leads are deleted every day.
Erase a person's data
- Open Settings > Privacy and data and find Erase a person’s data.
- Type the person's address in Email address to erase and click Erase.
- Confirm with Erase for good.
For a GDPR or PDPL erasure request: deletes every lead with this email (with its delivery history), their game prizes, and their email on any discount code they were given. It cannot be undone. Copies already sent to your integrations stay there.
Shared learning
Help every store convert better: Add your campaigns’ anonymous patterns (which trigger, moment and format converted) to the learning all Tafsee stores benefit from, including the A/B optimizer’s starting points. Only counts are pooled, never leads, emails or visitor ids, and a number is shown only when at least three stores stand behind it. Switch it off to keep your numbers out. You still see what others share.
Your connected tools
A lead sent to a tool is then also held by that tool, under its own rules. Keys and tokens you enter are stored encrypted and are used only to deliver your leads.
Data layer events
On a page with a tag-manager data layer, the script announces when a campaign is seen and when someone signs up. Only the campaign and version ids are put there, never what the visitor typed. See Tag manager and analytics events.
If it does not work
- Only teammates who can manage leads can erase a person’s data.
- Could not erase that email address. Check the address for typing mistakes.
- A visitor asks why they see no popups: their browser may send Do Not Track or Global Privacy Control.
