LEGAL
Cookie & Tracking Technologies Policy
1. INTRODUCTION
This Cookie Policy explains how Outmate.ai ("Outmate", "we", "us", or "our") and the Outmate visitor-tracking pixel use cookies, local storage, device-characteristic signals, and similar technologies ("Tracking Technologies"). It should be read together with our Privacy Policy.
This Policy covers two distinct contexts: (a) the Outmate application, dashboard, and marketing website that we operate; and (b) the Outmate visitor-tracking pixel that our subscribers deploy on their own websites.
2. WHAT ARE TRACKING TECHNOLOGIES
Cookies are small text files stored on a device by a website. "First-party" cookies are set by the website you are visiting; "third-party" cookies are set by a different domain.
Local storage is a browser mechanism that stores data on a device without using cookies.
A device fingerprint is a value derived from a combination of browser and device characteristics (such as rendering behavior, screen attributes, time zone, and language) used to recognize a device.
3. TRACKING TECHNOLOGIES IN THE OUTMATE APPLICATION AND WEBSITE
The Outmate authenticated application and dashboard do not set advertising or analytics cookies, and we do not embed third-party analytics, advertising, or social-media trackers on our authenticated product surfaces.
Authentication and session state in the Outmate application are maintained using browser local storage (for example, an authentication token, cached user profile, and a workspace pixel-key value) rather than cookies. This storage is strictly necessary to keep you signed in and to operate the application.
If our public marketing website uses any analytics or consent technologies, they are disclosed in the table referenced in Section 6.
4. TRACKING TECHNOLOGIES USED BY THE VISITOR-TRACKING PIXEL
When a subscriber deploys the Outmate pixel on the subscriber's website, the pixel uses first-party Tracking Technologies on that website to identify and de-anonymize visitors, subject to the consent gating described in Section 5.
The pixel may set or use the following on the subscriber's website:
A first-party visitor identifier, stored in local storage and a first-party cookie, with a lifetime of up to 365 days, used to recognize a returning visitor.
A captured business email value, stored in local storage and a first-party cookie where an email is submitted through a form or passed to the pixel by the website, with a lifetime of up to 365 days.
An opt-out flag, stored in local storage and a first-party cookie, used to record and honor a visitor's choice to opt out of tracking.
A device fingerprint, computed from browser and device characteristics and used to support identification and deduplication.
The pixel also processes event data described in the Privacy Policy (such as page URL, referrer, IP address, device and engagement signals). The pixel does not set third-party advertising cookies.
5. CONSENT AND CONTROL FOR THE PIXEL
The pixel is designed to respect end-user consent and preference signals before activating, including: a stored opt-out flag; the browser Do Not Track signal; the Global Privacy Control (GPC) signal; and recognized consent-management platforms, including the IAB Transparency and Consent Framework (TCF 2.0), Cookiebot, and OneTrust.
For visitors the pixel determines to be in the EU, EEA, United Kingdom, or Switzerland, the pixel defaults to a consent-denied state and does not track unless an affirmative consent signal for the relevant purposes is received from a consent-management platform.
Subscriber Responsibility. The subscriber, as controller of its website and visitor data, is responsible for deploying an appropriate cookie banner and consent-management platform, for providing notice, and for obtaining any legally required consent before the pixel collects data. Outmate provides the consent-gating controls described above but does not act as the subscriber's consent-management platform.
6. COOKIE AND STORAGE DETAILS
The following summarizes the Tracking Technologies described above.
Context: Outmate application. Name/Type: authentication token and cached profile (local storage). Purpose: keep you signed in and operate the application. Duration: until logout or token expiry (default 24 hours for the token). Party: first-party. Category: strictly necessary.
Context: Subscriber website (pixel). Name/Type: visitor identifier (local storage and first-party cookie). Purpose: recognize returning visitors for identification. Duration: up to 365 days. Party: first-party. Category: identification/analytics (consent-gated).
Context: Subscriber website (pixel). Name/Type: captured email value (local storage and first-party cookie). Purpose: associate a submitted business email with the visitor. Duration: up to 365 days. Party: first-party. Category: identification (consent-gated).
Context: Subscriber website (pixel). Name/Type: opt-out flag (local storage and first-party cookie). Purpose: record and honor an opt-out. Duration: persistent until cleared. Party: first-party. Category: strictly necessary (consent/preference).
Context: Subscriber website (pixel). Name/Type: device fingerprint (computed signal). Purpose: support identification and deduplication. Duration: not stored as a persistent identifier on the device; computed per event. Party: first-party. Category: identification (consent-gated).
6.2
7. MANAGING YOUR PREFERENCES
You can control Tracking Technologies through your browser settings, by using the opt-out and consent controls offered on a subscriber's website, by enabling Global Privacy Control or Do Not Track, and by using the visitor opt-out mechanism described in our Privacy Policy. Disabling strictly necessary storage in the Outmate application may prevent the application from functioning.
This policy is provided for general information and does not constitute legal advice. Certain details (such as the legal entity name and jurisdiction of incorporation) are subject to final confirmation.