Public paid beta
Cookie Policy
How Metricanic and its customers may use cookies, local storage, tracking identifiers, analytics tags, and similar technologies.
- Effective date
- May 1, 2026
- Last updated
- May 1, 2026
Cookies and Similar Technologies
Metricanic is offered as a public paid beta. Beta features may change, have limited support or SLA commitments, and may be unavailable or incomplete. No production-grade SLA applies unless separately agreed in writing. Some integrations or advanced features may require configuration, approval, or plan eligibility. Cookies and similar technologies may be used to authenticate users, maintain sessions, protect the service from abuse, remember recovery or OAuth flows, measure product usage, and perform campaign attribution or ad measurement.
Metricanic customers may deploy tracking links, direct tracking scripts, cookies, tags, pixels, redirect logic, postbacks, and related technologies on customer-controlled websites, landing pages, apps, ad flows, and campaign infrastructure. In those cases, the customer controls the property or campaign where the technology is deployed and is responsible for end-user notice, consent, and legal basis.
Cookie and Storage Table
| Cookie or storage | Category | Purpose | Notes |
|---|---|---|---|
| Supabase auth/session cookies | Necessary | Authenticated panel sessions | Required for login and session continuity. |
| sb-password-recovery | Necessary | Password recovery flow | Used during password recovery. |
| Google OAuth state cookie | Necessary | OAuth CSRF/state validation for Google Ads linking | Used when connecting Google Ads integrations. |
| Turnstile/security | Necessary | Bot and abuse prevention | Used to reduce automated abuse and protect signup/login flows where implemented. |
| GA4 analytics cookies | Analytics | Panel or site usage analytics | Optional analytics cookies are used only after consent where implemented and required. |
| vid | Attribution/ad measurement | Visit attribution | Customer-controlled attribution/ad-measurement storage; customer is responsible for required consent or gating. |
| vclk | Attribution/ad measurement | Click attribution | Customer-controlled attribution/ad-measurement storage; customer is responsible for required consent or gating. |
| dtp_visit_{campaignId} | Attribution/ad measurement | Direct tracking visit continuity | Customer-controlled attribution/ad-measurement storage for direct tracking; customer is responsible for required consent or gating. |
Customer Consent Responsibilities
Customers are responsible for determining when prior opt-in consent is required and for obtaining any required consent before deploying Metricanic tracking.
Customers must block or gate vid, vclk, dtp_visit_{campaignId}, analytics cookies, and other non-essential Metricanic attribution, advertising measurement, analytics, tracking, profiling, localization, or identification storage unless lawful consent has been obtained or a valid cookieless flow applies.
- Provide cookie notices and privacy disclosures.
- Obtain and store required consent.
- Honor opt-outs and withdrawal of consent.
- Block or gate non-essential cookies and tracking where required.
- Avoid sensitive data in URLs, tokens, subids, pubids, external IDs, campaign names, and entity names.
Managing Cookies
Users may control cookies through browser settings and applicable consent tools. Blocking necessary cookies may prevent login, account access, password recovery, OAuth linking, or security checks from working correctly.
Contact Metricanic at [email protected].