What are cookies and why does ReoBrix use them?

Digital platforms rely on cookie files and localized data protocols to maintain core infrastructure and deliver consistent page behavior. When accessing pages across the platform, temporary text strings and cryptographic identifiers are generated and exchanged between your client device and our server instances. These files fall into two operational structures: session cookies, which exist solely in transient device memory and dissolve immediately upon terminating the active browsing session, and persistent cookies, which remain written to local browser storage until their predetermined expiration threshold or manual user deletion.

We categorize all client-side data storage into four operational tiers according to technical purpose and duration:

  • Strictly Necessary Cookies: Essential tokens responsible for load distribution, session security, cross-site request forgery prevention, and core content routing. These identifiers retain no direct demographic markers and expire automatically within 24 hours of session conclusion.
  • Preference and Configuration Cookies: Identifiers that record customized interface preferences, such as default odds display formats, display scaling, and regional content filters. These persistent parameters maintain a lifecycle between 30 and 365 days.
  • Performance and Analytics Cookies: Aggregated measurement scripts that log page load latency, referral sources, content interaction rates, and visitor retention metrics without recording identifiable user records. Analytical retention records are stored for 14 to 24 months.
  • Affiliate Attribution Cookies: Cryptographic referral tokens that verify traffic source pathways and campaign integrity when visitors transition through external reference links. These tracking elements store no personally identifiable information and expire within 30 to 90 days.

Modern web browsers store these identifiers alongside complementary client-side mechanisms such as HTML5 Web Storage (comprising localStorage and sessionStorage key-value pairs). Readers can independently inspect active identifiers assigned by this domain through desktop developer environments, including the Application tab in Chromium browsers, the Storage inspector in Mozilla Firefox, and the Storage panel in Apple Safari. These inspection panels display active cookie names, domain scopes, encryption state flags, and exact Greenwich Mean Time expiration dates.

You retain comprehensive administrative control over stored files and can modify, block, or delete them through individual browser preferences at any moment. Disabling essential or functional cookies may reset interface customizations, alter content rendering speeds, or require manual selection of regional filters on every visit. For broader details regarding data processing standards and technical operations, consult our privacy policy and review our company background.

Which third parties set cookies?

Provider typeExampleLifetime
AnalyticsGoogle Analytics (_ga, _gid)24 hours to 14 months
AttributionPartner referral tokens30 to 90 days
Security / CDNCloudflare (__cf_bm)30 minutes
AdvertisingRetargeting pixelsOnly after consent

Analytics

Google Analytics sets first- and third-party identifiers to collect aggregate metrics: screen size, browser version, referring URL and interaction times. Daily markers expire within 24 hours. Long-term analytics last up to 14 months with IP anonymisation.

Attribution

Visitors arriving from partner links or landing pages get identifiers that log campaign parameters, sub-affiliate tokens and click times. They last 30 to 90 days and are kept apart from player profiles, as described in the privacy notice.

Security and delivery

Content delivery and security layers use short-lived tokens, such as Cloudflare's __cf_bm, which lasts 30 minutes and separates people from bots. These tokens build no profiles. Disabling them would weaken stability and DDoS protection.

Advertising

Ad pixels stay off until consent is given in the cookie banner. Once allowed, they track campaign conversions across display networks. They can be blocked or cleared at any time in the browser or site settings, and navigation and odds remain fully available.

How is this policy updated, and who can answer questions?

ReoBrix reviews its tracking setup regularly. Web standards, Canadian provincial privacy rules and browser storage rules all change over time. When a third-party library or the site's caching changes, the policy is updated with exact lifetimes, storage keys and scope. Audits also remove retired analytics tokens and old referral tags from the code.

How are changes announced?

Significant changes include new cookie categories, new consent periods or a different referral structure. Each change comes with a new revision date at the top of the policy. If a change affects consent, a notice appears on the next visit before any new script runs.

Where is the rest of the data policy?

This page covers browser storage, local tokens and cookie lifetimes. Data collection, server-side processing and access rights are described in the privacy policy. Data from essential and analytics cookies is not reused for other purposes, combined across sites or sold.

Who answers cookie questions?

Questions about cookies, local storage or preference settings go to the technical compliance team. Contact routes are listed on the About Us page, or write to ReoBrix, 275 Slater Street, Suite 900, Ottawa, ON K1P 5H9, Canada, phone +1 (613) 555-0129. Each request is logged and answered.