DataDad.
Join the closed betaJoin beta
DataDad / Privacy

Privacy-first analytics.
Cookieless by default.

Measure traffic and conversions without analytics identity cookies. Use optional consent to connect visits over time.

Join the beta
Website activity becomes analytics reports without a persistent visitor cookie. Your analytics Traffic & conversions No analytics identity cookies

No identity cookies

Default website tracking uses no visitor or session identity cookies.

Daily visitor IDs

Cookieless visitor IDs change each day and differ between websites.

Optional identity

Enable first-party identity cookies through your existing consent flow.

Choose how visits connect

Both modes measure traffic and conversions. Persistent identity adds journeys across visits.

Cookieless analytics compared with optional consent-based identity
Website trackingCookielessDefaultWith consentOptional
Traffic & conversionsIncludedIncluded
Visitor identityChanges dailyPersists across visits
Identity cookiesNoneFirst-party visitor and session cookies
Customer journeysWithin the daily visitor IDAcross visits and days

Privacy and compliance

GDPR & cookie rules

Cookieless tracking limits persistent identity. Consent requirements still depend on your setup and local rules.

Audience measurement guidance

HIPAA

Health data needs a separate assessment and appropriate agreements. Do not send protected health information to the beta.

Health data and tracking

SOC 2

SOC 2 examines a service’s controls. DataDad does not currently claim a SOC 2 audit report.

About SOC reports

Privacy questions

Does cookieless analytics need a cookie banner?

Cookieless does not automatically mean consent-free. DataDad’s default website mode sets no analytics identity cookies. Your setup and local rules determine whether consent is required.

Is cookieless visitor data anonymous?

No. Daily visitor IDs are pseudonymous. They change each day and are specific to your website, but the data can still fall under privacy law.

What happens when a visitor withdraws consent?

DataDad removes visitor and session identity cookies and returns to cookieless tracking. It also stores the visitor’s consent choice in a first-party preference cookie.

Data used to run your DataDad account

The tracking choices above apply to analytics on your website. Your DataDad account also uses an email address, authentication records, project settings, and session cookies. These records let you sign in and manage your projects.

Analytics data includes the events and properties your project sends. Use fixed event names and avoid personal details in URLs and event properties. Manage project data in project settings. Manage sign-in sessions on your account page.

For a website visitor’s data request, contact the operator of the website you visited. That operator controls its analytics project and consent setup.

Explore DataDad’s traffic and conversion reports.

View analytics features