Privacy & GDPR
How LeadJourney handles personal data – first-party tracking, partially masked IP addresses, and the controls you have to exclude traffic and pages from tracking.
LeadJourney is built around first-party tracking and gives you several controls over what gets recorded. This page summarises the privacy-relevant behaviour and where to manage it.
Not legal advice
This explains how the product behaves. How you use it compliantly – consent collection, your privacy policy, data-processing terms – depends on your jurisdiction and setup. Treat this as a feature reference, not legal guidance.
First-party tracking
Tracking runs from your own tracking domain (a
subdomain like t.your-site.com), so data is collected first-party rather than through a
third-party domain. This is what keeps attribution accurate – and it's covered more in
What is the tracking script?.
IP addresses are masked
In the interface, IP addresses are partially masked for privacy compliance – you'll see them shortened rather than in full (for example in a lead's IPs tab in Lead Overview). Full IP data is available via the API with the appropriate permissions, for cases where you need it.
Controls over what's tracked
You decide what counts and what's ignored:
- Exclude pages – stop lead capture on specific paths (e.g.
/admin,/private/*) under Settings → Tracking. - Blacklist – exclude traffic by IP, user agent, referrer, campaign, email, email domain or entry URL, so it's ignored across all reports and lead data. See Manage your blacklist.
- Exclude bots – keep automated traffic out of your numbers. See Exclude bots from tracking.
Data retention
How long data is kept is covered in Data retention.
Need to remove a person's data?
You can delete a lead (and its journey) directly from Lead Overview – use the row menu or select and delete in bulk.