1. Analytics

This site uses PostHog for analytics, routed through our own domain (/ingest) rather than PostHog's servers directly. PostHog is a US-based service; the underlying analytics data is processed on PostHog's US cloud (us.i.posthog.com).

We do not use Google Analytics, Google Tag Manager, or any other analytics vendor.

PostHog collects page views (the URL visited, the referrer, and the referring domain), autocaptured clicks and form submissions, and a set of named events we've defined for our own product: booking CTA clicks, booking modal opens, completed bookings, and contact form start, submit, and success.

Every event also carries your IP address, which PostHog uses to derive an approximate location — country and region, not a precise or persistent identifier. We don't store IP addresses ourselves outside of what PostHog holds.

PostHog also captures heatmap data site-wide: aggregate mouse movement, click position, and scroll depth, turned on at the project level. This is separate from session replay below — it's an aggregate pattern across visitors, not a recording of any one visit.

2. Session replay

PostHog also records session replays — a visual playback of how a visitor moved through the page. All form inputs are masked in these recordings; what you type into any field, including the contact form, is not captured in the replay.

3. Cookies and local storage

PostHog sets a cookie and uses your browser's local storage to recognize you as a returning visitor across page views. This is what lets us tell, for example, whether a booking click and a later booking completion came from the same visit.

4. Third parties

Two outside services receive data from this site:

• PostHog — analytics and session replay, as described above.
• Cal.com — our embedded booking scheduler. If you open the booking modal and enter information there (name, email, meeting details), you're interacting directly with Cal.com, and Cal.com's own privacy policy governs what you submit through that scheduler. Separately, when a booking completes we send PostHog a non-identifying record of that fact: the booking's internal ID, the event type, its status, and whether it was recurring or required payment. The attendee's name is deliberately left out of that record; it isn't forwarded to PostHog.

5. Your choices

Global Privacy Control (GPC) is the reliable way to turn off session recording: when your browser sends it, we suppress the recording for that visit. GPC ships built into some browsers (Brave, Firefox with an add-on) or can be added as an extension in others.

We also honor Do Not Track (DNT) where a browser still sends it, but DNT is an older signal that most current browsers, including Chrome, no longer send at all — Chrome dropped it, so setting it there has no effect. Treat GPC as the lever that actually works.

This turns off session recording only. The analytics events described above — page views, clicks, form submissions, and the named product events — are still collected for all visitors, including those with DNT or GPC enabled.

6. Where this applies

Analytics and session replay are only active on the live production site. Preview deployments and local development builds send nothing to PostHog.

7. Contact

Questions about this page or how your data is handled: contact@oddeven-consulting.com.