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 types of cookies are used?
Essential and functional cookies
Strictly necessary cookies
These are required for the site to work and cannot be switched off. They are set in response to a user's own actions, such as choosing privacy settings, logging in or sending a form. They keep a login active, block cross-site request forgery (CSRF) and route traffic between servers. They last from one browser session up to 24 hours for login security tokens.
Functional and preference cookies
These remember choices between visits: regional display, preferred market views, odds format (decimal or fractional) and collapsed menus. Without them, the site returns to default settings on every reload. They last from 30 days to 12 months, unless a new choice resets them.
Affiliate and referral cookies
When a visitor arrives through a partner link, these cookies log the referral source and campaign code. They hold no contact details, only an encrypted transaction ID and a timestamp. They let partners verify traffic and usually expire after 30 days.
Analytics, marketing and storage
Performance and analytics cookies
These measure overall behaviour on the site: load speed, bounce rate, page paths and error rates. The aggregated data shows bottlenecks and helps improve page layouts. Records are pseudonymous and last from 14 days to 24 months, in line with the retention rules in the privacy policy.
Targeting and conversion pixels
These tags measure how campaigns and editorial sections perform. They link the browser to an anonymous device profile, so the same prompt is not shown again and again. Marketing tags usually expire after 90 to 180 days.
Local storage
Besides cookies, the site uses HTML5 Web Storage (localStorage and sessionStorage) to cache static files and keep filter settings. Unlike cookies, this data is not sent to the server with each request, which saves bandwidth. Organisational details are on the about page.
Expiry controls
Every cookie has a Max-Age or Expires setting under the IETF RFC 6265 standard. Session cookies vanish when the browser closes. Persistent cookies are cleared or overwritten when they expire, so no token stays on a device indefinitely.
Which third parties set cookies?
| Provider type | Example | Lifetime |
|---|---|---|
| Analytics | Google Analytics (_ga, _gid) | 24 hours to 14 months |
| Attribution | Partner referral tokens | 30 to 90 days |
| Security / CDN | Cloudflare (__cf_bm) | 30 minutes |
| Advertising | Retargeting pixels | Only 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 can cookie preferences be changed?
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.