Cookie Policy

1. What cookies are

Cookies are small text records stored by a browser. Similar browser storage can serve related purposes. First-party cookies are set for the site you visit; a third-party service may receive information when its script or resource is loaded. Session cookies expire with the session, while persistent cookies remain until their expiry or deletion.

2. Necessary storage

Necessary storage is used without the optional analytics choice because the requested feature cannot operate securely without it.

• Supabase authentication cookies (commonly named with an sb-…-auth-token pattern, including split chunks): maintain and refresh a signed-in session. Duration follows the authenticated session and Supabase token lifecycle.
• dramafork-analytics-consent-v1: records granted or denied analytics choice and the update time for up to 180 days. This cookie does not identify an account.
• Temporary in-memory page state: keeps unfinished input on the current loaded page. It is not the authoritative database and can disappear on reload.
• Legacy migration access: a compatibility tool may read older DramaFork localStorage or sessionStorage records for an explicit account import or cleanup flow. New business records are not persisted there as a cloud-failure fallback.

3. Optional analytics

If you choose Allow optional analytics, DramaFork loads Google Analytics 4. GA4 may set first-party _ga and _ga_<measurement-id> cookies to distinguish browsers and sessions; Google's default expiry can be up to two years, subject to browser and analytics-property settings. DramaFork's own consent choice expires after 180 days, so you may be asked again sooner.

The current configuration sends normalized page categories, referrer origin, limited product events, and LCP, CLS, and INP performance metrics. It does not intentionally send email, profile fields, prompts, messages, project names, project text, project IDs, or content IDs. Query strings and fragments are removed; detail routes are converted to generic templates.

4. Advertising remains off

The current Google consent configuration keeps ad_storage, ad_user_data, and ad_personalization denied. Google Signals and ad-personalization signals are disabled. DramaFork does not use analytics consent to enable targeted advertising or upload account data to Google Analytics.

5. Manage or withdraw consent

Use the Cookie settings control on this page or in the site footer. Choosing Necessary only stops future DramaFork analytics events and attempts to remove accessible _ga cookies for this site. It cannot retract events already sent or remove records retained independently under Google's policy. You can also clear or block cookies in your browser, but blocking authentication cookies can prevent sign-in.

When the browser reports Do Not Track (DNT) or Global Privacy Control (GPC), DramaFork forces optional analytics to denied in that browser. If a browser blocks storage entirely, the site may ask again because it cannot remember the choice.

6. Provider information

Google independently describes GA4 cookie names, collection, controls, and retention in its documentation and privacy policy. Supabase describes its role in authentication and infrastructure in its privacy documentation. Provider defaults can change; the actual DramaFork code continues to gate GA4 loading on your choice.

7. Updates and contact

We will update this page if cookie names, purposes, providers, or durations materially change. Email [email protected] with questions or to report behavior that does not match this policy.