Wexlyn is built so you can run it under the GDPR, the UK GDPR and the Swiss FADP. Everything on this page is a setting you control per account, in Tracking → Tracking Configuration → Privacy. Nothing here is legal advice: the right choice depends on your legal basis and your cookie banner, so confirm it with your counsel.
Who is the controller
You (the website owner) are the controller of your visitors' data; Wexlyn processes it on your instructions as a processor under the Data Processing Agreement. The subprocessors page lists every provider Wexlyn relies on and the transfer mechanism for each.
Off by default
GDPR mode on the Privacy tab is off for every new account. Off means every visitor, in Europe or anywhere else, is tracked exactly the same way and nothing on that tab applies. Turn it on only when you (or the client whose account it is) market to people in the EU, the UK or Switzerland. Once on, the choices below apply only to visitors located in those countries; visitors elsewhere are unaffected unless you also tick "wait for consent outside those countries".
Visitors in the EU, UK and Switzerland
The script asks the collector where the visitor is (country only, from the network edge, never stored) and then follows the choice you made:
- Track only after consent. Nothing is stored on the device and nothing is sent until the visitor accepts. The visitor id lives in memory; the page view is sent the moment consent arrives, so the click is not lost. This satisfies the cookie rules (ePrivacy, Austria's TKG §165, Germany's TTDSG) without a tag manager.
- Do not track. Visitors in these countries are never recorded: the script stops before writing a cookie, and the collector drops anything that arrives from those countries anyway.
Wait for consent everywhere extends the consent rule to every visitor, wherever they are.
The countries covered: the 27 EU member states, Iceland, Liechtenstein, Norway, the United Kingdom and Switzerland.
Connecting your cookie banner
With consent-first on, the script needs to hear "yes". Cookiebot and CookieYes are detected automatically: accepting statistics or marketing cookies starts tracking, declining keeps it off. For any other banner (Usercentrics, OneTrust, Complianz, your own) call this from the accept callback:
window.wexlyn.consent(true); // visitor accepted: tracking starts, ids are kept
window.wexlyn.consent(false); // visitor declined: nothing is sent
The decision is remembered in the browser, so returning visitors are not asked by Wexlyn again (your banner decides when to re-ask). Visitors who decline stay anonymous; their later purchases still arrive from your checkout or CRM integrations, just without the click journey.
IP addresses
Wexlyn uses the IP for the visit's location and, when identity grouping by IP is on, to join an anonymous visit to a known person. Hash IP addresses stores only a salted hash (h:… in the CRM's identity list): matching still works, the address itself is never written. City, region and country are still recorded from the edge and are not personal data on their own.
Retention
Tracking Configuration → Data → Data retention (months) sets how long tracked events are kept for this account (25 months by default, the table's own limit). A nightly job deletes events and anonymous visitors older than your window. Leads, sales, calls and subscriptions are business records and are kept until you delete them.
Access, portability and deletion requests
When a person asks what you hold about them, or asks you to delete it:
- Export. On the lead's profile (the download icon next to the name) or in Tracking Configuration → Privacy → Export a person's data, enter the email. You get a JSON file with the lead, every identity, every tracked event, sales, calls, subscriptions and stage history, ready to pass on.
- Delete. The trash icon on the profile, or Privacy → Delete a person's data by email, removes the lead, its identities, its tracked events in ClickHouse, sales, calls and subscriptions. Both actions are written to the audit log with your name.
Shopify's own GDPR webhooks (data request, customer redact, shop redact) are handled automatically for connected stores.
Looking at a lead without becoming one
Opening a page from a journey inside Wexlyn appends wexlyn=disabled to the URL. The script records nothing on that page or on any page you reach from it in the same tab, so your own visit is never attached to the person you were reviewing.
What Wexlyn itself does
Wexlyn's own site runs the same script under Wexlyn's own account, with the same settings available to you. Breaches are notified to affected customers within 72 hours of confirmation, in line with Article 33. The privacy policy has the full detail.