Privacy & Transparency

    Cookie Policy

    Document Reference: DC-CK-2026-V1.1 (Scrubbed Architecture)
    Last Modified: June 2026
    Classification: Public Transparency / Legal Infrastructure

    1. Introduction, Scope & System Ethos

    This Cookie Policy explains how Data Compass Ltd (“Data Compass,” “we,” “us,” and “our”) deploys cookies, pixels, local storage, and related tracking web architectures when you interface with our web environments, portal entry points, and corporate assets located at https://datacompass.co.uk (collectively, the "Website").

    In line with our mission to dismantle the fragmented, bloated tech stacks of legacy CRM systems (The Frankenstack), we manage our data collection pipelines with extreme transparency and minimal overhead.

    Our application platform runs on an integrated native architecture designed to execute automated tasks, preserve security states, track active client sessions, and fuel our communication utility infrastructure.

    To the extent that any tracking technology collects, creates, or connects with Personal Data, such data is managed strictly in accordance with our Data Processing Addendum and Core Privacy Policy.

    2. Tracking Technologies Defined

    To maintain absolute architectural clarity, we utilize the following specialized tracking methods across our web delivery footprint:

    • •
      Cookies: Minimal text strings stored directly inside your browser cache to uniquely isolate your device, optimize server calls, and remember active session choices.
    • •
      Local Storage: On-device storage blocks utilized to accelerate application render speeds, cache user UI configurations, and ensure rapid interface functionality.
    • •
      Clear GIFs / Web Beacons: Invisible tracking graphics embedded within platform emails, transactional message flows, and specific site headers to continuously measure operational delivery performance and script efficiency.
    • •
      Pixels & Tags: Structural operational snippets deployed to establish immediate handshake routines with analytics systems and verify campaign attribution metrics.

    3. Granular Cookie Registries

    A. Strictly Necessary Cookies

    These tracking layers are hard-coded into our platform infrastructure to ensure base system runtime health, verify user data integrity, and protect gateway access nodes. They cannot be toggled off without entirely destabilizing system access.

    Owner / OperatorSpecific ProviderOperational PurposeStandard Lifecycle
    Data Compass (Platform Native)Data Compass App EngineDeploys session files (e.g., _helpkit_session) to verify data integrity, manage active customer support routes, and track open help tickets.Session-bound
    Data Compass (Platform Native)Data Compass App EngineDeploys specific preference hooks (e.g., cookie_config) to permanently store and execute a visitor's explicit privacy choices.Up to 1 Year
    Data Compass (Platform Native)Data Compass App EngineDeploys backend markers (e.g., _tracking_consent, _fprom_code) to support authorized partner tracking loops and validate user data privacy profiles.Up to 1 Year
    CloudflareCloudflare.comUtilizes the __cf_bm cookie file to intercept malicious automated bot networks, validate authentic inbound web traffic, and shield server nodes.Session-bound
    GoogleGoogle.comEmploys the _GRECAPTCHA file layer to perform structural risk analysis and block brute-force scripting on inbound web forms.6 Months

    B. Performance & Telemetry Cookies

    These trackers compile clean, aggregated data matrices regarding page visits, workflow pathways, and performance drop-offs. They allow us to optimize system processing speeds and balance server loads.

    Owner / OperatorSpecific ProviderOperational PurposeStandard Lifecycle
    Data Compass (Platform Native)Data Compass App EngineUtilizes tracking components (such as _landing-page, v2_session_history_, and v3_first_session_event_) to capture, report, and audit page interactions.Up to 1 Year
    Google AnalyticsGoogle.comDrops system diagnostics (such as _ga, _gclxxxx, _gid, _ga_xxxxxxxxxx, _gat) to capture user journeys and throttles script volumes on high-traffic days.Up to 1 Year
    Data Compass (Platform Native)Core Ecosystem ArchitectureDeploys operational identifiers (such as msgsndr_id) to manage downstream deployment paths and split-test performance variations.Up to 1 Year
    Microsoft Clarityclarity.microsoft.comDrops behavioral mapping cookies (such as _clck and _clsk) to generate structural UX click maps and locate broken application paths.Up to 1 Year
    ShopifyShopify.comUtilizes dedicated system parameters (such as _shopify_s, _shopify_sa_t, _shopify_sa_p, and _shopify_y) to trace referral metrics and check checkout speeds.Up to 1 Year

    C. Functional Tracking Technologies

    These specialized configurations unlock high-tier user personalization layers, enable real-time communication channels, and secure custom workspace parameters.

    Owner / OperatorSpecific ProviderOperational PurposeStandard Lifecycle
    Data Compass (Platform Native)Data Compass App EngineDeploys financial localization tracking (such as cart_currency) to execute and display clear, accurate check-out currencies on dynamic payment pages.13 Days
    FreshworksFreshworksInstantiates communication identifiers (such as _x_w) to tie help desk tickets to an active chat window session and maintain live support links.Session-bound
    LinkedInlinkedin.comDeploys core sharing and professional attribution assets (such as bcookie or lidc) to facilitate content-sharing and tracking interactions.1 Year
    Microsoft Clarityclarity.microsoft.comDeploys structural diagnostic analytics (such as SM and CLID) to track user navigation trends and interface performance.Session-bound
    ShopifyShopify.comRuns transactional stability files (such as _orig_referrer, _tracking_consent, and secure_customer_sig) to handle basket choices and client log-in profiles.1 Year

    D. Marketing & Campaign Alignment Cookies

    These tracking blocks are configured by our enterprise marketing operations and advertising partners to build contextual interest matrices, map customer conversion pathways, and serve relevant ad configurations across external platforms.

    Owner / OperatorSpecific ProviderOperational PurposeStandard Lifecycle
    FacebookFacebook.comEmploys audience mapping frameworks (such as _fbp) to deliver target retargeting arrays and measure precise conversion value metrics.2 Months
    GoogleGoogle.comCoordinates user profile records (such as NID and _gcl_au) to measure corporate ad performance across search networks and track ad spends.6 Months
    Microsoft BingBing.comDeploys marketing parameters (such as MR, SRM_B, MUID, and ANONCHK) to personalize digital ad delivery and audit search engine conversion paths.1 Year
    RedditReddit.comDeploys targeting strings (such as _rdt_uuid) to audit performance metrics and track click events generated on the Reddit platform.Session-bound
    YouTubeYoutube.comInitiates video optimization tracking (such as YSC and VISITOR_INFO1_LIVE) to maintain streaming speeds and feed dynamic ad networks.Session-bound

    4. Control Mechanics & Compliance Signals

    We empower mid-market enterprise users and web visitors with direct control over their data footprint. Your data tracking preferences can be adjusted through several direct enforcement mechanisms:

    • •
      The Privacy Choices Panel: You can comprehensively adjust your non-essential tracking parameters at any time by clicking the "Your Privacy Choices" link located permanently within our Website footer.
    • •
      Regional Consent Management: Because Data Compass targets the UK and European corporate sectors, we run strict opt-in consent protocols. Non-essential tracking cookies (Performance, Functional, and Marketing) are completely blocked by default until you grant explicit, granular consent via our localized banner panel.
    • •
      Global Privacy Control (GPC): Our systems natively honor GPC broadcasting protocols. If your browser or network routing layer issues an automated GPC privacy signal, Data Compass reads it as a valid, binding instruction to opt out of all non-essential data tracking. No further action is required on your part.
    • •
      Manual Browser Overrides: You can alter your browser configuration profile to inspect, erase, block, or completely reject cookies. Please note that disabling critical functional tracking layers will degrade application stability and may prevent access to parts of the Data Compass operational platform.

    For custom browser guidance, consult the native help documentation for your application (e.g., Google Chrome, Mozilla Firefox, Apple Safari, or Microsoft Edge).

    Independent Framework Opt-Outs: For global behavioral ad tracking controls, you can completely opt out of target networks via About Cookies, the European Interactive Digital Advertising Alliance, or the Digital Advertising Alliance.

    5. Revisions and Corporate Contact

    Data Compass Ltd reserves the right to modify this Tracking Policy dynamically to match new core software deployments, feature updates, or statutory requirements. Any revisions will be accompanied by an updated policy timestamp at the apex of this document.

    For any legal queries, regulatory data audits, or clarity regarding our tracking infrastructure, please contact our Compliance Desk directly:

    Corporate Entity Name: Data Compass Ltd (Company No: 16430399)

    Registered Office Footprint: Rosings, Smarden Rd, Headcorn, Kent, TN27 9HP, United Kingdom

    Compliance Inquiries Contact: data@datacompass.co.uk