Customer Data and Tracking

When you build a funnel, page or checkout in Oddyssey, the measurement running on it is yours. You decide what is collected and why. We provide the tooling and process the data as your processor under the Data Processing Addendum. To your visitors, you are the business behind the tracking.

• Page and step views, clicks, form starts and completions, and time on step.
• A first-party identifier stored in a cookie or local storage to tie a visitor's steps into one session and one journey.
• Referrer, campaign parameters such as UTMs and platform click identifiers, and the experiment arm the visitor was assigned.
• Device, browser and coarse location derived from IP address.
• Order and revenue events you send us, including refunds and disputes where your gateway reports them, so readouts are net.
• Any custom event or property you choose to send. What you send is your decision and your responsibility.

• Publish your own privacy notice on your funnels, naming the categories above and the purposes.
• Collect and honour consent where the law requires it, including cookie consent in the EEA and the UK, and do not fire non-essential tracking before consent is given.
• Respect Global Privacy Control and similar opt-out signals where applicable, and honour state-level opt-outs in the US.
• Do not send us special category data, government identifiers or card data through tracking events.
• Do not track people in ways your notice does not describe.

Where you configure it, conversion events are forwarded to ad platforms through their server-side APIs. Server-side delivery does not change the legal position: the same consent and disclosure obligations apply, and the platform's own data terms apply to you.

• We do not build a cross-customer identity graph. Your visitor data is not combined with another customer's.
• We do not sell visitor data or share it for cross-context behavioural advertising.
• We do not use your visitors' data to train AI models.
• We do not track visitors across unrelated sites.

Event-level data is retained for 25 months by default, then deleted or aggregated. Aggregated experiment readouts and learning records are kept for as long as your account is open, because they are the point of the product. You can shorten retention or delete a data set from the workspace at any time.

Access, deletion and opt-out requests from your visitors go to you, because you hold the relationship. You can action them in the workspace. If a request reaches us directly we will refer the person to you and tell you it happened. Notify us at support@tryoddyssey.com if you need help executing one.