Jourvex is designed with a privacy-first approach, helping teams understand user behavior without relying on direct personal identifiers.
What we collect
- Page URLs and navigation paths
- Session timing and engagement signals
- Browser and device information
- Pseudonymous identifiers (such as session tokens) used to group activity
- Device and browser signals used to support session-level analysis and measurement
Data collected by Jourvex is used for analytics and product insights and is not intended to directly identify individuals.
What we do not collect
- Names, emails, or passwords by default
- Form inputs or user-entered content
- Sensitive personal information
Where data goes
- Sent securely via HTTPS to our API
- Processed on infrastructure hosted in the United States
- Isolated per customer using siteKey scoping
- Not sold or shared with advertising networks
How identification works
- No direct identity is created by default
- No tracking across unrelated websites
- No linkage to real-world identity unless explicitly provided by the customer
Consent and regional controls
- Jourvex includes region-aware controls for data collection
- In certain regions (such as the EU and UK), tracking only activates after user consent
- If consent is not provided, no data is collected
Platform usage
- Jourvex operates as a first-party analytics tool for website owners
- Customers are responsible for implementing disclosures and consent mechanisms where required
Data storage and retention
- Data is retained only as long as necessary to operate and improve the service
- Customers may request deletion of their data
- Some anonymized or aggregated data may be retained for system improvement
Our commitments
- Privacy-focused by design
- No direct identifier collection by default
- Consent-aware tracking controls
- Working toward industry-standard security practices (including SOC 2 readiness)