Understanding Our Use of Cookies
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.
Categories of Cookies We Use
Essential & Functional Identifiers
Strictly Necessary Cookies: These fundamental identifiers are mandatory for core platform operations and cannot be toggled off within our configuration panels. They are deployed strictly in response to user-initiated actions, such as establishing privacy thresholds, logging into an authenticated profile, or submitting input forms. Strictly necessary cookies manage authentication state tokens, defend against cross-site request forgery (CSRF), and maintain load balancer routing across distributed servers. Their typical lifespans range from a transient browser session up to 24 hours for persistent login security tokens.
Functional & Preference Cookies: These files record user-specified parameters to preserve continuity between visits. Functional cookies retain interface preferences such as regional display setups, chosen sports market views, odds formatting preferences (such as decimal or fractional notations), and collapse states on dynamic navigation panels. Without these cookies, the site resets to factory defaults upon every page reload. Their retention cycles normally span between 30 days and 12 months, expiring automatically unless manually refreshed by updated user choices.
Affiliate Attribution & Referral Cookies: When users navigate to our pages via verified partner channels, specialized attribution cookies log the referral source identifier and campaign code. These records do not contain personal contact data; instead, they capture an encrypted transaction ID and a timestamp. These tags permit accurate traffic verification and partner auditing. Attribution tokens typically persist for a standard window of 30 days before being purged by your client browser.
Performance, Analytics & Measurement
Performance & Analytics Cookies: Analytic trackers evaluate aggregate behavioral patterns across the domain, monitoring metrics such as page load speed, bounce rates, navigation sequences, and HTTP error frequencies. We analyze aggregated statistical telemetry to identify platform bottlenecks and optimize editorial layouts. Metrics captured through analytics scripts remain pseudonymous and are stored for durations ranging from 14 days to 24 months, in compliance with standard digital telemetry retention policies outlined in our privacy policy.
Targeting & Conversion Pixels: We utilize specialized measurement cookies and pixel tags to assess the performance of informational campaigns and measure engagement with specific editorial sections. These tags associate your browser with an anonymous device profile to prevent repetitive prompt displays and ensure that notifications remain contextually relevant. Marketing tags typically carry expiration dates between 90 and 180 days.
Local Storage & Modern Cache Objects: Alongside standard HTTP header cookies, our technical architecture utilizes HTML5 Web Storage (`localStorage` and `sessionStorage`) to cache static resources and preserve offline filter states. Unlike standard cookies, localStorage objects do not transfer data payloads to the server with every HTTP request, minimizing bandwidth overhead. You can review detailed organizational protocols on our about page.
Audit Schedules & Expiration Controls: Every cookie category on this platform is bounded by strict `Max-Age` or `Expires` directives conforming to standard IETF RFC 6265 protocols. Transient session objects vanish the moment the browser window closes, while persistent records are routinely overwritten or cleared according to their individual expiry headers, ensuring no tracking token remains indefinitely dormant on your hard drive.
Third-Party Cookies and Analytics
External telemetry and measurement services assist in evaluating site stability, page load speed, and navigational traffic patterns across ReoBrix. Analytical providers, including Google Analytics, generate persistent first-party and third-party identifiers (such as _ga and _gid) to capture aggregated metrics. These scripts record anonymized device viewport dimensions, browser engine versions, referring URLs, and interaction timestamps. Standard telemetry cookies operate on configured retention schedules, with daily session markers expiring within 24 hours and aggregated longitudinal analytics persisting for up to 14 months under strict IP anonymization rules.
Attribution cookies handle incoming referral traffic and affiliate source logging. When visitors access the platform through partner links or promotional landing pages, dedicated tracking identifiers log campaign parameters, sub-affiliate tokens, and click event timestamps. These attribution records generally persist between 30 and 90 days on local storage to verify acquisition channels and prevent redundant referral reporting, operating independently of direct player profile records as outlined in our privacy notice.
Essential technical third parties deliver infrastructure security and media distribution across the site. Content delivery networks and edge-security layers utilize short-lived technical tokens, such as Cloudflare bot management identifiers (__cf_bm), which remain active for 30 minutes to distinguish legitimate human browsing from automated crawling scripts. These functional identifiers process no personal profiles and cannot be disabled without compromising platform stability and DDoS defense mechanisms.
Targeting and retargeting pixels deployed by advertising platforms remain dormant until explicit consent is registered via the compliance banner. These commercial scripts track campaign conversion events across display networks to measure promotional efficiency. Visitors can block or clear marketing pixels at any time through individual browser privacy controls or by adjusting site permissions, leaving core navigation, odds feeds, and general platform information fully accessible.
Managing Your Cookie Preferences
On-Site Consent Management Tool
When you access ReoBrix, a dedicated consent interface initializes before any non-essential trackers execute in your browser environment. This tool categorizes every identifier by functional necessity, granting you granular control over analytical, functional, and affiliate attribution storage tokens. Essential session tokens remain active to maintain core routing and cryptographic integrity, but you can freely accept all optional tracking, reject all optional categories, or toggle specific scopes according to your data privacy standards.
Your operational selections are encoded into an internal record cookie named reobrix_consent_state, which carries a rolling lifespan of 180 days. This mechanism ensures your custom parameters persist across browsing sessions without triggering redundant prompts on every page load. Should you decide to modify your permissions or revoke consent, you can reopen the preference module at any moment via the persistent link in the footer of our informational platform.
Adjusting these settings directly impacts how our platform measures interface interactions and attribution pathways. While declining analytics cookies will not restrict your access to comparative sports reviews, match statistics, or technical odds breakdowns, it prevents our measurement systems from aggregating your page dwell metrics and navigation sequences into our general usability testing datasets. For wider details on data governance, consult our comprehensive privacy notice.
Browser-Level Configuration and Storage Purging
In addition to our on-site consent manager, all contemporary desktop and mobile web browsers provide integrated controls to inspect, restrict, and purge local client-side storage. Through your browser developer console or privacy settings menu, you can evaluate the individual key-value pairs assigned under the domain, identify expiration timestamps, and delete specific cookies such as performance tokens, referral keys, or interface theme variables without altering your wider operating system settings.
To enforce complete containment across the web, you can configure your browser to reject third-party cookies by default or maintain a strict session-only clearance rule that purges all local storage objects upon closing the application window. Major browser engines—including Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge—feature distinct menu paths for content permissions, tracking prevention levels, and storage clearance, giving users total mechanical authority over their cache and cookie directories.
Note that applying global browser-level blocks against all cookie files, including first-party essential tokens, will disable critical site functions such as security validation tokens, responsive UI layout memory, and user-initiated preference caching. To maintain standard platform responsiveness while observing safe betting analysis and reference tools, we recommend allowing essential first-party cookies while disabling persistent third-party cross-site trackers. Review our responsible gambling resources for additional guidance on managing digital engagement securely.
Policy Updates and Contact Information
ReoBrix regularly evaluates its technical tracking architecture and data storage protocols to ensure continuous alignment with emerging web standards, provincial privacy frameworks across Canada, and shifting browser handling rules for partitioned client-side state. When third-party tracking libraries alter telemetry mechanisms or when core platform caching configurations evolve, this Cookie Policy is adjusted to reflect exact parameter lifetimes, storage keys, and transmission scopes. Routine audits ensure that discontinued analytics tokens and stale affiliate referral tags are purged from production codebases without unannounced persistence.
Material amendments to this policy—such as the introduction of new tracking categories, alterations to consent duration thresholds, or shifts in how affiliate referral parameters are structured—are accompanied by an updated revision date prominently displayed at the head of this document. For structural adjustments that alter tracking obligations or consent choices, a notification prompt will display upon your subsequent visit to provide transparent notice before refreshed scripts execute. Readers are encouraged to periodically review this record to remain informed about technical persistence parameters.
While this policy specifies browser storage mechanisms, local tokens, and tracking lifetimes, broader standards governing data collection, server-side aggregation, and data subject access entitlements are outlined in our dedicated Privacy Policy. Information collected via essential and analytics cookies is processed under strict governance rules, restricting unauthorized secondary processing, cross-site identity collation, or third-party data brokerage without transparent technical justification and verified safeguards.
Inquiries concerning cookie implementations, local storage management, or technical troubleshooting related to preference configurations can be directed to our technical compliance and editorial team. Readers requiring further details about specific script sources or seeking clarification on data handling workflows may consult our About Us resources or transmit queries directly via our designated compliance desk. We systematically log and address technical inquiries regarding tracking verification and script execution parameters.