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 account flows, measure product usage, and perform customer-enabled attribution or ad measurement.
Optional analytics and advertising technologies are used only after consent where implemented and required.
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 |
|---|---|---|---|
| Required service cookies and storage | Necessary | Login, security, account flows, billing, and service operation | Required for service features. |
| Consent preference storage | Preference/consent | Stores optional cookie consent choices | Required to remember consent choices; does not itself enable optional tags. |
| Optional analytics and advertising cookies or storage | Analytics/advertising | Site or panel measurement, advertising performance, and product improvement | Used only after consent where implemented and required. |
| Customer-enabled attribution storage | Attribution/ad measurement | Customer-controlled attribution and measurement | 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 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, identifiers, campaign metadata, and similar fields.
Managing Cookies
Users may control cookies through browser settings and applicable consent tools. Blocking necessary cookies may prevent login, account access, account recovery, integration linking, or security checks from working correctly.
Contact Metricanic at [email protected].