Information we collect
RevLens collects account information needed to create and secure a workspace, including your email address, authentication records, workspace name, project domain, and any profile or support details you choose to provide inside the product.
When you install the RevLens tracking script, we collect analytics records tied to your site key. Those records can include page URLs and paths, page titles, referrers, UTM parameters, browser and device details, viewport and screen sizes, language, timezone, and pseudonymous visitor and session identifiers.
Cookies and pseudonymous identifiers
The standard RevLens tracker uses first-party cookies to maintain a persistent visitor identifier for up to one year and a session identifier that refreshes across a 30-minute activity window. These identifiers let the product group pageviews, custom events, and live presence signals into a coherent journey without requiring direct personal identity.
RevLens also offers a cookieless install mode that avoids writing cookies and instead carries pseudonymous visitor and session parameters during navigations when possible. In that mode, identifiers are less durable and may reset on direct landings, hard reloads, or new tabs.
The tracker may also decorate approved cross-domain links with pseudonymous visitor and session parameters so journeys can continue across related sites. When that happens, RevLens removes those parameters from the browser address bar after they are read.
How we use information
We use collected information to authenticate users, provision workspaces, display dashboards, build funnel and cohort views, surface pseudonymous visitor timelines, and generate monetization or product recommendations based on the events and pageviews a customer sends to the platform.
We also use information to measure event volume for plan usage, operate trials and subscriptions, detect misuse, respond to support requests, and improve the reliability and quality of RevLens.
Sensitive and prohibited event data
RevLens is designed for event names and simple scalar properties such as strings, numbers, and booleans. The product guidance in the app explicitly tells customers not to send direct personal data such as names, email addresses, street addresses, or raw authentication tokens inside analytics events.
Customers are responsible for deciding which product events to track and for making sure their instrumentation choices are appropriate for their own users and legal obligations.
How data is shared
We do not sell personal information. We share data only with vendors and service providers that help us run RevLens, such as our hosting, authentication, database, and billing providers.
We may also disclose information when required by law, to enforce our terms, to prevent fraud or abuse, or to protect the rights, safety, and security of RevLens, our customers, or others.
Data retention and security
We retain account, workspace, billing, and analytics data for as long as reasonably necessary to provide the service, maintain historical reporting, honor legal obligations, resolve disputes, and enforce agreements. Customers may request deletion of workspace data, subject to those obligations.
RevLens uses reasonable administrative, technical, and organizational safeguards designed to protect information from unauthorized access, misuse, alteration, or loss, but no system can be guaranteed completely secure.
Your choices
Workspace owners control whether the tracker is installed, which domains it runs on, and which custom events are sent. Account holders can update workspace details in the product and manage subscription actions through the billing flows available in their account.
If you are an end user whose interaction data was collected by a company using RevLens, that company is the primary controller of that data. Please contact them directly for requests relating to access, correction, deletion, or consent.
Changes to this policy
We may update this Privacy Policy from time to time. If we make material changes, we will revise the effective date on this page and may provide additional notice in-product or through account communications.