What we store on your browser, and why.

Small text files. That's it.

Cookies are small text files that websites store on your device to remember information about your visit. Similar technologies include local storage, session storage, and pixels — we treat all of them the same way for the purposes of this policy.

Some cookies are required for the site to function (you can't really opt out of those without breaking things). Others help us understand how the site is used so we can improve it.

Four categories, plain English.

Services that may set cookies.

DataDoe is built on Webflow, which hosts and delivers this site. On top of it we use:

• Google Analytics 4 (Google LLC) — page views, sessions and traffic sources. Its cookies (_ga, _ga_*) are set only after you click Accept. Until then, and if you click Decline, Google receives cookieless signals without any cookie identifier, as described in Google Consent Mode. With your consent, Google may also use this data to measure our Google Ads campaigns.
• FirstPromoter — credits signups that come through our partner and affiliate links. If you arrive through such a link, it stores a referral identifier (_fprom_tid, _fprom_ref).
• Campaign attribution (_dd_utm, our own cookie, kept for 90 days) — if you arrive from a link with campaign (UTM) parameters, we remember the campaign and the landing page so a later signup can be attributed to it.
• Embedded videos and demos — some pages embed YouTube videos and Arcade product demos. Those providers may set their own cookies when the player loads, under their own policies.

Other subprocessors listed in our Privacy Policy (Stripe, Google Cloud, AI inference providers) operate server-to-server and do not set cookies on this marketing website. If you use the in-product checkout flow on app.datadoe.com, Stripe sets its own cookies on that domain for fraud prevention — Stripe's own cookie disclosures apply there.

If we add or remove analytics or marketing services, this policy will be updated to reflect them. We do not use social media tracking pixels.

Banner on first visit.

The first time you visit DataDoe, a cookie banner appears with options to Accept or Decline. Your choice is stored locally in your browser so we don't show the banner again on every page.

You can change your mind at any time using the controls described in the next section.

Reset or change your choice.

To reset your cookie preferences and bring the banner back, clear your browser's site data for datadoe.com — specifically the localStorage entry named dd-cookie-consent. The banner will reappear on your next visit.

If you'd prefer we delete any data already collected about your sessions, contact us at contact@datadoe.com and we'll handle it under the rights described in our Privacy Policy.

Browser-level privacy signals.

Some browsers send a Do Not Track (DNT) header or a Global Privacy Control (GPC) signal indicating you do not wish to be tracked across sites.

DataDoe honors the GPC signal as a valid opt-out under the California Consumer Privacy Act — if your browser sends GPC, we treat it as a request to opt out of any sale or sharing of personal information (although, as stated in our Privacy Policy, we do not sell or share personal information in the first place).

DNT is not a formal standard and adoption varies across services. We treat it as informational and respect your explicit cookie banner choice over the DNT header.

Block cookies at the browser level.

All major browsers let you block or delete cookies through their settings. Useful direct links:

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

Note that disabling all cookies may break essential site functions, including form submissions and session-dependent features.

When we update this page.

We may update this Cookie Policy when we add or remove services, change cookie usage, or in response to regulatory updates. The "Effective" date at the top reflects when this version was published.

Material changes are also reflected in the cookie banner — if categories change in a way that requires fresh consent, the banner will reappear.