Cookie Policy & Tracking Architecture
1. Technical Overview: HTTP Headers vs. Client-Side Script Cookies
Signal Recovery Software Engine ("SRSE") operates a specialized server-side reverse proxy and Conversions API (CAPI) routing layer. Unlike traditional ad-tech platforms that rely on client-side JavaScript cookies (document.cookie) or third-party tracking pixels, SRSE utilizes first-party HTTP response headers governed by RFC 6265bis.
Issued directly by our edge reverse-proxy nodes during initial page request negotiation:
Domain=.customerbrand.com;
Path=/;
Max-Age=31536000;
Secure; HttpOnly; SameSite=Strict
Restricted from client-side script tampering, immune to cross-site scripting (XSS) extraction, and preserved under WebKit ITP rules.
Generated within browser memory via document.cookie calls:
Subject to severe browser decay: automatically capped by Apple Safari ITP to 7 days (or 24 hours if incoming with query parameters such as fbclid or gclid).
2. Apple Safari ITP & WebKit Anti-Tracking Compliance
Apple's WebKit Intelligent Tracking Prevention (ITP) was designed to combat invasive cross-site tracking and hidden third-party tracking networks. SRSE's architecture complies with the technical specifications and spirit of WebKit privacy policies:
- Legitimate First-Party Context: SRSE edge nodes run within our subscriber's authenticated DNS ownership hierarchy (e.g.,
data.customerbrand.com) under valid first-party SSL certificates. They do not operate as cross-site tracking networks across unrelated web properties. - Absence of CNAME Cloaking: Unlike predatory tracking vendors that disguise third-party domains behind CNAME aliases to siphon user browsing histories across the web, SRSE reverse proxies only process data within the discrete, single-merchant boundary. Our edge nodes do not aggregate browsing profiles across different subscribers.
- 365-Day Attribution Persistence: Cookies issued via authentic server-side HTTP response headers (
Set-CookiewithHttpOnly; Secure; SameSite=Strict) are legally retained for up to 365 days under RFC 6265bis without triggering WebKit client-side script caps, enabling accurate long-cycle attribution for high-consideration purchases.
3. Comprehensive Cookie & Local Storage Inventory
The following table enumerates all cookies and identifiers utilized by SRSE on our public website and subscriber edge reverse-proxy nodes:
| Cookie Name | Type / Mechanism | Lifespan | Category | Purpose & Technical Function |
|---|---|---|---|---|
| _cg_fp_uid | 1st-Party Server HTTP Header | 365 Days | Attribution / Analytics | Cryptographically generated UUIDv4 assigned to identify return sessions, prevent duplicate CAPI conversions, and bridge cross-session conversion events. |
| _cg_sess_id | 1st-Party Server HTTP Header | 30 Minutes | Strictly Necessary | Maintains active session continuity during browsing navigation and groups rapid multi-step checkout events. |
| _fbp | 1st-Party Browser Cookie | 90 Days | Marketing / CAPI | Meta pixel browser identifier utilized to align client-side browser actions with server-side Meta Conversions API events. |
| _fbc | 1st-Party Browser Cookie | 90 Days | Marketing / CAPI | Stores incoming Meta Click Identifier (fbclid) from inbound ad referrals to enable deterministic conversion attribution. |
| _gcl_au / __gads | 1st-Party Browser Cookie | 90 Days | Marketing / Attribution | Google Ads attribution cookie utilized by Google Enhanced Conversions to correlate ad clicks with verified purchase conversions. |
| tt_pixel_id_s2s | 1st-Party Server Cookie | 13 Months | Marketing / CAPI | TikTok Events API match token utilized to correlate server-to-server conversion events with TikTok ad interactions. |
| __stripe_mid / __stripe_sid | 3rd-Party Cookie (Stripe) | 1 Year / 30 Min | Strictly Necessary | Fraud detection and prevention for commercial subscription checkout flows. Processed under Stripe's PCI-DSS Level 1 certification. |
4. ePrivacy Directive (Art. 5(3)) & Consent Management Platforms
Under Article 5(3) of the European ePrivacy Directive (Directive 2002/58/EC as transposed into national member state legislation):
- Strictly Necessary Cookies: Cookies essential for the provision of a service explicitly requested by the user (such as session continuity, checkout security, and Stripe fraud prevention) do not require prior opt-in consent.
- Attribution & Marketing Cookies: Identifiers utilized to measure advertising performance, track conversions, or link user activity across visits (
_cg_fp_uid,_fbp,_gcl_au) strictly require prior, freely given, explicit opt-in consent from users within the EEA, UK, and Switzerland before activation. - Consent Banner Integration: Our subscribers are contractually required to integrate SRSE edge ingestion nodes with a certified Consent Management Platform (CMP) (such as OneTrust, Cookiebot, Klaro, or Usercentrics) to govern cookie issuance.
5. Google Consent Mode v2 & Meta Limited Data Use (LDU) Propagation
SRSE features automated real-time parsing and enforcement of global ad platform privacy and consent parameters:
Google Consent Mode v2 Dynamic Enforcement
SRSE edge nodes inspect incoming telemetry for Google Consent Mode v2 signal states:
_gcl_au) may be read or stored.
_ga).
If ad_user_data='denied', SRSE automatically strips all user match parameters (hashed email, phone, address) before dispatching the payload to Google endpoints, routing only cookieless attribution pings.
Meta Limited Data Use (LDU) Automated Flagging
To satisfy CCPA/CPRA and US multi-state privacy regulations, SRSE reverse proxies support automated injection of Meta's Limited Data Use parameters:
"data_processing_options_country": 1,
"data_processing_options_state": 1000
When LDU is active, Meta processes conversion events strictly in its capacity as a Service Provider, disabling cross-context behavioral ad sharing for that event.
6. Global Privacy Control (GPC) & Universal Opt-Out Signals
In compliance with California CPRA regulations (§ 7025) and emerging state privacy mandates, SRSE reverse-proxy edge ingestion nodes actively inspect incoming HTTP request headers for:
When a GPC signal is detected, the reverse proxy automatically suppresses non-essential cookies, sets Google Consent Mode v2 flags to denied, and injects Meta LDU directives for that specific session without requiring manual banner interaction.
7. User Cookie Management & Browser Controls
Users maintain absolute authority over the storage of cookies on their client devices:
- Browser Configuration: You can configure your browser (Google Chrome, Apple Safari, Mozilla Firefox, Microsoft Edge) to reject all cookies, block third-party cookies, or alert you when a cookie is placed.
- Deleting Stored Cookies: You may at any time purge all stored cookies and local storage records via your browser's security/privacy preferences.
- Digital Advertising Alliance Opt-Outs: You can opt-out of interest-based advertising from participating ad networks via the DAA WebChoices Tool or the EDAA Your Online Choices Portal.
8. Cookie Policy Governance & Contact
For technical or legal inquiries concerning our cookie issuance architecture or Consent Mode integration, please contact our tracking engineering team: