What data does ReoBrix collect?
Technical data
Server monitoring records anonymised IP addresses, browser and device details, operating system versions and request timestamps. These records are combined into aggregate reports. They show regional audience patterns, help fix slow routes and speed up pages on mobile and desktop. No individual profiles are built from them.Personal data
Personal details are collected only when a reader contacts the editorial team or sends feedback. In that case ReoBrix stores the name, email address and message. Technical tokens described in the cookie policy support basic site functions. Contact records are never sold or passed to marketing brokers.Legal basis and retention
Technical data is processed under a legitimate interest in network security and stable content delivery. Contact requests rely on the sender's consent. Server logs are deleted or irreversibly anonymised every 90 days. Email inquiries are kept for up to 12 months for compliance. Readers can ask to access, correct or delete their correspondence at any time, and requests are handled within 30 business days. More on the editorial approach is on the about us page, and safe play guidance is in the responsible gambling section.Direct Communications and Submitted Identifiers
When visitors initiate contact with our editorial desk, submit corrections regarding our published sports analysis and market odds, or subscribe to periodic digest notifications, we record the personal details voluntarily transmitted. This typically encompasses individual names, verified electronic mail addresses, message timestamps, and the specific text contained within correspondence threads. Where readers provide voluntary feedback regarding operator evaluations or point-spread breakdowns, that submission is catalogued strictly to facilitate direct replies, resolve factual discrepancies, or maintain ongoing editorial integrity across our review registry.
The legal basis for processing submitted communication data rests upon user consent and our legitimate administrative interest in addressing audience inquiries under applicable Canadian privacy frameworks, including PIPEDA standards. Information transmitted via direct email channels or web contact forms is retained within secure, access-controlled communication vaults for a defined period of twenty-four months from the date of final resolution, after which all identifying records are permanently purged or systematically anonymized for historical metric evaluation.
We do not require user account creation, financial profiles, or payment instrument credentials to browse our analytical guides or access editorial rankings. Readers exploring our platform do so without undergoing commercial onboarding, ensuring that personal contact records remain confined strictly to those individuals who proactively reach out to our staff. If you correspond with our team regarding editorial policies or platform updates, your details are never repurposed for automated marketing distribution without explicit, unambiguous opt-in consent.
Technical Telemetry, Device Data, and Server Logs
Our web servers automatically record network telemetry to safeguard platform availability, detect distributed denial-of-service attempts, and analyze routing performance across Canadian provinces. This infrastructure data includes originating Internet Protocol (IP) addresses, browser application user-agent strings, referring uniform resource locators, device operating systems, screen resolutions, and requested server resource timestamps. IP addresses are processed at ingress points and truncated or pseudonymized before long-term statistical storage to prevent direct individual identification.
Technical data processing relies on our legitimate operational interest to maintain infrastructure security, optimize load balancing across regional edge servers, and ensure our content renders accurately across desktop and mobile browsers. Raw web server logs containing unprocessed network traffic parameters are preserved for a rolling retention window of ninety days, after which they are systematically overwritten or expunged. Aggregated performance metrics—stripped of all personal network signatures—are preserved for up to fourteen months to evaluate multi-season audience trends.
In addition to core server metrics, technical telemetry helps monitor the functional deployment of player protection standards outlined in our responsible gambling guide. We monitor click-through patterns to ensure compliance notices are served consistently to visitors before they navigate to external licensed operators. These technical audits process aggregated connection counts and category interactions rather than granular user profiles, ensuring complete alignment with transparent data-handling principles detailed across our editorial about section.
How are cookies and tracking used?
What is recorded
Automated tracking records masked IP addresses, operating system and browser versions, referring sites, language settings and interaction times. This data is processed in aggregate. It reveals server problems, measures page speed on Canadian networks and shows which sections get regular traffic. No customer profiles or financial records are built from it.On what basis, and for how long
Essential scripts run under a legitimate interest in routing security, load balancing and protection against cross-site scripting. Analytics scripts that measure traffic and referral sources run only with the visitor's consent. Session tokens disappear when the browser closes. Analytics markers last from 30 days to 24 months before they are rotated and deleted.How to control tracking
Browser settings can block persistent cookies, clear stored data or turn on tracking prevention. The cookie settings and policy page lists each tool, its source and how long it lasts. Turning off non-essential tracking does not limit access to reviews, match analysis or safety guidance.Cookies, pixels and server logs
Session cookies last only while the browser is open. Persistent cookies last from 30 days, for interface settings, up to 24 months, for long-term analytics. They record times, screen settings and entry paths, but cannot read other files on the device.
Tracking pixels and script tags measure page speed. When a page loads, a one-pixel image sends a small request to a logging server. The log notes the load time, device environment and protocol version, which helps find broken links and slow servers.
Server logs record shortened IP addresses, browser strings, request methods and times. The last part of each address is masked before it is saved, so a log entry cannot be tied to a household's internet account. Logs are overwritten after 90 days.
Browser and opt-out controls
Modern browsers let users view stored cookies, block third-party scripts and clear data automatically when a session ends. Built-in protection, such as Intelligent Tracking Prevention and Enhanced Tracking Protection, separates cookies by site to stop cross-site tracking.
Global Privacy Control and Do Not Track signals send storage preferences directly to the server. Opt-out tools from the Digital Advertising Alliance of Canada (DAAC) and the Network Advertising Initiative (NAI) withdraw consent from partner networks that follow those codes.
Blocking storage does not limit access to articles or guides. It does stop the site from remembering display settings, time zone and closed banners. Full lists of vendors, cookie names and expiry dates are in the cookie overview.
What rights do readers have over their data?
Legal grounds and retention
Data is processed on two grounds: legitimate interest in platform security and consent for technical diagnostics.| Data type | Retention |
|---|---|
| Server access logs (shortened IP, browser string) | 90 days |
| Aggregated analytics without personal identifiers | Up to 14 months |
| Email sent to help desks | 24 months |