What we set, what we don't, and how to control it.

A cookie is a small text file placed on your device by a website you visit. Similar technologies — local storage, session storage, and pixel tags — perform comparable functions. In this policy we use "cookies" to refer to the whole category.

Strictly necessary

Required for the site and lab tools to operate — for example, session continuity during a discovery chat, security tokens, and the form-submission flow. These cannot be turned off without breaking core functionality.

Functional

Remember preferences such as the last lab tool you visited or whether you've dismissed an informational banner. Functional cookies are first-party and short-lived.

Analytics — Google Analytics 4 (first-party)

We use Google Analytics 4 (GA4) for aggregate page-view counts, traffic source attribution, and on-site interaction metrics (such as which lab tools are used most). GA4 is configured as a first-party analytics deployment — cookies are set under the eigenra.com domain, not on a third-party tracking domain.

The cookies GA4 sets:

• _ga — distinguishes returning visits; expires after approximately two years
• _ga_<measurement-id-suffix> — session state for the GA4 property; expires after approximately two years

GA4 processes IP addresses to derive coarse geolocation and then drops them — full IP addresses are not stored. We do not run Google Ads campaigns, behavioural retargeting, or remarketing audiences against this analytics data. Google acts as a sub-processor; the cross-border disclosure terms in section 08 of the Privacy Policy apply.

To opt out specifically from GA4 measurement on this site, install Google's official Analytics opt-out browser add-on. Browser-level cookie blocking (see section 04 below) also prevents GA4 cookies from being set.

What we do not set

• Third-party advertising or retargeting cookies
• Social-media share-button trackers
• Behavioural profiling cookies
• Browser fingerprinting
• Pixel tags from advertising networks

Where we embed external content — for example, a calendar booking embed on /book — that provider may set its own cookies under its own privacy policy. We choose providers with strong data-handling commitments and disclose every embed in this section. Currently:

• Booking embed (when configured): a third-party calendar provider sets cookies necessary for the booking flow. Disable by booking via email instead — submit the form at /contact and we'll send a calendar link manually.

You can control cookies from your browser settings — most browsers let you block all cookies, block third-party cookies, or delete existing cookies. Disabling strictly necessary cookies will break parts of the site that depend on them. Browser-specific instructions:

• Chrome: Settings → Privacy and security → Cookies and other site data
• Safari: Settings → Privacy → Manage Website Data
• Firefox: Settings → Privacy & Security → Cookies and Site Data
• Edge: Settings → Cookies and site permissions → Cookies and site data

We honour Do Not Track and Global Privacy Control signals where the analytics platform supports them. Sending these signals will reduce the analytics information we collect from your visit.

When we add or remove a cookie, we update this page and refresh the effective date. Material changes — including any new third-party embed or any new analytics category — are highlighted at the top for thirty days.

Questions or concerns about cookies: privacy@eigenra.com. The full Privacy Policy is at /privacy.