Turnjo
Log in
← All docs/GDPR & Data Privacy

GDPR & Data Privacy

Turnjo includes several features to help you meet your obligations under GDPR and similar data protection regulations. Your legal team should review your specific requirements — this article explains the tools available to you.

For an overview to share with your privacy team, including the services that process data for Turnjo and where it's hosted, see Turnjo and the GDPR.

Consent collection

Use the Consent field type in your Popup forms to collect explicit consent from visitors before capturing their data. You control the exact wording — write your consent label to match your privacy policy and legal requirements.

The label supports markdown links so you can link directly to your privacy policy:

I agree to the [Privacy Policy](https://yoursite.com/privacy) and consent to being contacted.

The consent checkbox value (yes or no) is recorded with every lead, giving you an auditable record of consent at submission time.

Data retention

How long Turnjo keeps leads and survey answers depends on your plan:

  • Paid plans keep them for as long as you're subscribed.
  • The Free plan keeps them for 24 months. Anything older is deleted on the 1st of each month.

On a paid plan, an admin can set a shorter or longer retention period, for example to match your own privacy policy:

  1. Go to Account → Settings.
  2. Under Data Retention, enter the number of months.
  3. Save.

Leads and survey answers older than that period are deleted on the next monthly purge. Leave the field blank to go back to your plan's default.

If you move to the Free plan, including when a paid subscription is cancelled or lapses, nothing is deleted straight away. You get 30 days' notice: Turnjo emails your team with how many leads and survey answers are older than 24 months and the date they'll be deleted, and shows the same warning in Account → Settings. Choose a paid plan before then to keep them, or export your leads first.

Visit events

Records of what visitors did, such as a popup being shown, a Yes/No choice or a tour step, are kept for 13 months. After that they're replaced by daily counts with no visitor details, so your analytics history stays complete. Anonymous visitor counts used for billing are kept for the current and previous billing period, then kept only as a total per month.

Right to erasure

To delete all data for a specific individual:

  1. Go to Leads.
  2. Click Erase by Email.
  3. Enter the email address and confirm.

This permanently deletes all lead records for that email, any survey answers and Chat conversations given with that email, and scrubs their data from webhook delivery logs. The action cannot be undone.

Right of access

When someone asks for a copy of the data you hold about them:

  1. Go to Account settings › Lead data.
  2. Click Export by email.
  3. Enter the email address and download the file.

The file (JSON) holds every lead for that email across your properties, with the fields and answers they gave, the consent wording they agreed to, their survey answers and Chat conversations, and where each lead was sent (your integrations and webhooks). Send it to the person who asked. Exporting and erasing need an account admin.

What the embed stores in the visitor's browser

Turnjo's embed sets no cookies. It does use the browser's own storage, scoped to your site, so that popups, experiments and tours behave consistently for each visitor. None of it is a cross-site identifier, and none of it is shared with other sites.

The With consent mode column shows what happens before the visitor consents when consent mode is on: Stored keys serve something the visitor asked for or remember a choice they made, and are stored as usual; Waits keys are kept in memory for the page only, until consent.

Session storage is cleared when the visitor closes the tab:

Key Purpose With consent mode
turnjo_visitor_{token} A random visitor identifier for the session, used to attribute experiment enrollments and tour progress. It's regenerated every session, so it can't link visits together. Waits
turnjo_tracked_{token} A 1 flag so the visitor is counted for billing only once per session (see below). Waits
turnjo_shown_{token} Popups shown this session, for the "once per session" frequency setting. Waits
turnjo_closed_{token} Popups the visitor closed this session (consent mode only, see below). Stored
turnjo_active_tour The tour and step in progress, so a tour resumes after a page change. Stored
turnjo_geo_{token} Cached approximate location looked up from the visitor's IP address (country, region and coordinates, for location targeting). Waits
turnjo_cfg_{token} The Property's configuration, to avoid refetching it on every page. Stored
turnjo_chat_{token} The Chat conversation's opaque id, so the conversation continues across pages. Stored
turnjo_chat_notice_{token} Whether the visitor dismissed the Chat privacy notice. Stored
turnjo_chat_peek_{token} Whether Chat's greeting has already been shown this session, so it pops up only once. Waits
turnjo_counts_{token} A 1 flag marking this session's visit as counted, for the "after N visits" settings. Waits
turnjo_debug Set only when someone opens your site with ?turnjo_debug=1, so Turnjo's debug messages stay on in that tab until ?turnjo_debug=0. Meant for your team, not visitors. Stored

Local storage persists until the visitor clears their browser data:

Key Purpose With consent mode
turnjo_seen_{token} Popups the visitor has already submitted, so they aren't asked again. Stored
turnjo_closed_{token} When the visitor closed each popup (consent mode only, see below). Stored
turnjo_shown_{token} When each popup was last shown, for the 7-day, 30-day and "show once" frequency settings. Waits
turnjo_visits_{token} A count of page views, for the "visit count" targeting rule. Waits
turnjo_counts_{token} Running counts of page views and visits, for the "show again after N visits / page views" settings. Waits
turnjo_closed_counts_{token} The visit and page view counts at which the visitor closed each popup, so a popup closed with an "after N visits / page views" limit stays closed for that long. Stored
turnjo_shown_counts_{token} The visit and page view counts at which each popup was last shown, for the "after N visits / page views" frequency settings. Waits
turnjo_choice_{token} The visitor's Yes/No answer to each popup that asks one, for targeting on it. Waits
turnjo_answers_{token} The visitor's choice and rating answers to each survey, for targeting on them. Written (free-text) answers are never stored in the browser. Waits
turnjo_cd_{token} When the visitor first saw each popup with a per-visitor countdown, so their countdown keeps running across pages and visits. Waits
turnjo_hv_{id}, turnjo_exp_{id} The popup variant or experiment variant assigned to the visitor, so they see the same version on every visit. Waits
turnjo_done_tour_{id} Tours the visitor has finished or dismissed. Stored

Apart from the session's approximate location and survey choice and rating answers, these values hold only Turnjo ids, timestamps, counts and Yes/No answers. They never include anything the visitor typed.

Consent mode

Under the ePrivacy Directive and similar laws, storing information on a visitor's device (in browser storage as well as cookies) can require consent unless it's strictly necessary for something the visitor asked for. A/B tests, visit counting and impression-based frequency limits may not meet that test.

Turn on Consent mode in the Property's Settings and Turnjo stores only the keys marked Stored above until your consent banner reports that the visitor has consented. Until then, Chat, Popups, Surveys and tours still work, but anything that needs to remember the visitor between pages can't:

  • Popups without a close-based limit show again on every page until the visitor closes one. Limits based on when a popup was shown ("once per session", "every 7 days", "after N page views") need storage, so before consent they count from when the visitor closes it instead. A popup closed with an "after N visits / page views" limit stays closed until the visitor consents, then counts from there.
  • Lower-priority popups may not get a turn. Only one popup shows at a time, and the first one to qualify shows again on each page, so another popup on the same pages may wait behind it until it's closed.
  • Experiments need consent before the script loads. A visitor is only enrolled, and only sees an A/B variant, once consent is known. Set window.turnjoConsent = true before embed.js for visitors who have already consented, so the right variant shows as the page loads. When consent arrives part-way through a page, Turnjo enrols the visitor then and applies their variant to the page already on screen (split-URL tests start from their next entry page); from then on every page shows their variant.
  • Analytics treat each page as a new visitor. The visit-count rule only sees the current page, the session visitor id is new on every page, and events for your own Google Analytics or Tag Manager wait on the page until consent, and are dropped if the visitor declines or leaves.

Waiting only in Europe

Consent Mode can wait for consent everywhere (the default) or only in the EEA, the UK and Switzerland, where the law requires consent before anything is stored. Choose under Wait for consent in the Consent Mode card.

With only in the EEA, UK and Switzerland, visitors elsewhere are treated as having consented, so A/B tests, experiments and frequency limits work for them from their first page. The visitor's country comes from their IP address, looked up by our network edge; a visitor whose country can't be determined waits for consent. If your banner does report a refusal (window.turnjoConsent = false) for a visitor outside Europe, Turnjo still honours it.

Some places outside Europe have their own rules. Check with your privacy adviser which setting fits your site.

Tell Turnjo about consent from your banner's callback, on every page. Any of these works, whether or not embed.js has loaded yet:

<!-- Before embed.js, when you already know the visitor's choice: -->
<script>window.turnjoConsent = true; /* or false */</script>
// When the visitor accepts or withdraws, once embed.js has loaded:
window.turnjo.consent(true);
window.turnjo.consent(false);

// Or, at any time, by setting the same value again:
window.turnjoConsent = false;

// Or, if your banner may answer before embed.js has loaded, through a queue Turnjo reads when it starts:
window.turnjo = window.turnjo || {};
window.turnjo.q = window.turnjo.q || [];
window.turnjo.q.push(['consent', true]);

On consent, everything waiting in memory for that page is stored, merged with anything stored when the visitor consented before, so earlier visits, closed popups and the variant they were shown are kept. On withdrawal, Turnjo deletes the Waits keys from the browser, even if the withdrawal arrives before Turnjo has finished loading. Turnjo doesn't remember the decision itself; your banner owns it.

Classify Turnjo in your banner as functional or analytics, whichever matches your policy. Whether each Stored key is exempt where your visitors are is a legal judgement, so check this list with your legal team.

Billing visitor counts

For billing, Turnjo counts monthly tracked visitors. The only thing stored on the device is the per-session turnjo_tracked_{token} flag above, which holds no identifier (with consent mode on and no consent yet, not even that). On the server, Turnjo records only a salted, one-way hash of the visitor's IP address and browser type; the IP address itself is never stored. The salt is specific to your account and changes every billing period, and is destroyed about 40 days after the period starts, so visitors can't be re-identified or linked across periods. Hashes are kept for the current and previous billing period, then replaced by a total per month.

Visitors are counted this way even before they consent, in consent mode too. Turnjo still shows them your popups, Chat and tours, so the visit is real use of the service, and counting it stores and reads nothing on their device. The hash is used only to count unique visitors for your bill, never to track or profile anyone, and isn't linked to leads or other visit records.

Page addresses

Visit records, leads, survey answers, feedback reports, Chat conversations and tour events note the page they came from. Turnjo sends that address without its query string or # fragment, which can carry personal details such as an email address or a reset token, keeping only the utm_source, utm_medium, utm_campaign, utm_term and utm_content campaign tags. Targeting rules still see the full address in the visitor's browser.

Chat conversations

If you use Chat, Turnjo keeps each conversation so your team can read it in Conversations:

  • Messages. What the visitor and Chat wrote. With Sensitive details turned on under Chat → Guardrails, card numbers, ID numbers and passwords are removed before a message is stored or sent to the AI, and the visitor is told.
  • Who started it, for blocking. A keyed hash of the visitor's IP address, specific to your Property, so it can't be turned back into the address or matched across sites, and a shortened version such as 203.0.113.x for your team to recognise. These let you block a visitor from Chat; a block lasts 30 days.
  • How long. A conversation that ends in a lead is kept as long as that lead, and goes with it when the lead is erased or reaches your retention period. Any other conversation is deleted 90 days after its last message.

Erasing a lead by email also deletes the Chat conversation that produced it.

Survey answers

If you use Surveys, Turnjo keeps each response so you can see it in Results:

  • Answers. What the visitor chose or wrote. Written answers can contain personal data if a visitor types it, so treat them as you would any other personal data you hold.
  • Where and who. The page the survey was answered on, and the embed's visitor id for that browser session (only while that id is stored, see above). A survey asks for an email only if you add an email field; giving one also creates a lead.
  • How long. Answers are deleted after your account's data retention period, and with the lead when a lead is erased by email.

Visitor feedback data

If you enable the feedback widget, submitted reports may include a screenshot of the page and recent browser console logs, which can contain personal data depending on your site. Visitors control this: the screenshot and diagnostics options are shown as checkboxes they can turn off before sending. What visitors typed in form fields (emails, card numbers, passwords) is hidden from screenshots by default. You can also mask other sensitive elements with CSS selectors on the Property's Feedback page, or with a data-turnjo-mask attribute in your markup. If you need typed values to debug a form, turn on Show what visitors typed in form fields there. Treat feedback reports as you would any other personal data you hold.

Feedback reports, with their screenshots and your team's comments on them, are deleted after your account's data retention period, on the same monthly purge as leads. A report doesn't ask for the visitor's email, so Erase by Email doesn't find it; if a visitor asks you to delete feedback they sent, delete the report from the Property's Feedback page.

Webhook delivery logs

Webhook delivery logs include the lead payload for debugging purposes. Payload data is automatically scrubbed from delivery logs after 90 days. The delivery record itself (status, timestamps, error messages) is kept for 13 months for audit purposes, then deleted.

Data processors

Integrations you connect receive data from Turnjo. Make sure you have appropriate Data Processing Agreements in place with those providers before enabling them.

  • Lead destinations. When you connect HubSpot, Klaviyo, Brevo, ActiveCampaign, Loops, Mailchimp, SharpSpring, Shopify or Zapier, or add a webhook, each lead (and the survey answers given with it) is sent there.
  • Slack. New leads, Chat handoffs and feedback reports can be posted to the Slack channel you choose.
  • Feedback destinations. When you connect Linear, GitHub or Slack for feedback, each report is sent there with the page address, browser details and, when the visitor left those options on, the screenshot link and console log.

If you use Chat, visitors' messages and your site content are sent to the AI provider that answers them (Anthropic, or OpenAI if that model is chosen) to generate each reply. Those providers act as Turnjo's sub-processors and don't use the data to train their models.