Cookie Policy

This Cookie Policy explains how Learn Domains uses cookies and similar technologies on learn.domains and app.learn.domains. It supplements our Privacy Policy.

Learn Domains does not display a cookie consent banner in v1. Essential and first-party functional cookies are required to operate the Service. Optional analytics scripts load only when configured via environment variables.

These cookies are required to sign in, maintain your session, and protect your account. They cannot be disabled while using the authenticated app.

• Clerk session cookies: Authentication, session management, and security for app.learn.domains. Exact cookie names are managed by Clerk. (Essential · Session to persistent (per Clerk configuration) · set by Clerk)

We set first-party cookies to run experiments, attribute referrals, and measure conversion without third-party advertising trackers.

• ld_vid: Stable anonymous visitor identifier for deterministic homepage experiments, funnel attribution, and first-party analytics correlation. (Functional · 365 days · set by Learn Domains)
• ld_aff: Stores the affiliate referral code for last-click attribution (90-day window). (Attribution · 90 days · set by Learn Domains · HttpOnly)
• ld_ref: Stores a customer referral code for last-click attribution (90-day window). (Attribution · 90 days · set by Learn Domains · HttpOnly)
• ld_ph_ref: Marks visits from Product Hunt for launch attribution (30-day window). (Attribution · 30 days · set by Learn Domains)

When configured, we load optional analytics scripts (Google Tag Manager, GA4, or DataFast). They may set their own cookies. We sanitize event payloads before sending to GTM — we do not send passwords, API keys, knowledge base content, AI prompts, or raw integration exports.

• Google Tag Manager / GA4 cookies: Optional marketing and product analytics when GTM or GA4 measurement IDs are configured. (Analytics · Per Google policy (configurable in Google admin) · set by Google)
• DataFast cookies: Optional product analytics when DataFast site configuration is enabled. (Analytics · Per DataFast policy · set by DataFast)

Server-side product analytics may also write to our internal events table (org/user identifiers). That data does not flow to client-side GTM pushes.

You can clear or block cookies in your browser settings. Blocking essential cookies will prevent you from signing in. Blocking ld_vid may reset experiment assignment and anonymous funnel attribution.

To stop optional analytics cookies, use browser controls or extensions that block third-party scripts. We plan to add consent-mode controls before expanding EU-heavy paid acquisition.

Questions about cookies? Email hi@learn.domains. For data access or deletion, see our Data Requests page at /data-requests.