Browsing without an account
You do not need to register or sign in to read the results centre, guides or glossary. Free Google sign-in is optional. We store your Google account identifier, name and email to identify your account, plus events you save and bet records you enter. These records are stored in our MySQL database and displayed only in your signed-in dashboard. We do not store Google access tokens after sign-in. A signed, HTTP-only session cookie keeps you signed in for up to 14 days. We do not create an advertising profile or user-comment database. It does not install third-party analytics or advertising scripts.
Ordinary page requests still travel to the server hosting the site. The hosting platform can receive information needed to answer those requests, such as the requested path, IP address and browser headers. That operational traffic is separate from the optional saved-events feature.
Saved events on this device
When signed out, a heart control on a results list stores the event identifier, display title and selected date in localStorage under results-fast-saved-v1. This allows the saved-events page to link back to that record without creating an account.
When signed in, saved events are stored against your account and available across devices. The signed-out browser list is separate and is not automatically imported. You can remove account saves and bet records in the dashboard.
The signed-out list is not sent to a separate synchronisation service and does not automatically appear on another device or browser. Remove individual items on the saved page, clear the complete list there, or remove the site’s storage in your browser settings. Private browsing or storage restrictions can prevent the feature from persisting.
Searches and filters
Guide searches, glossary searches and some filter choices appear in the requested URL. As with other requested paths, they can be included in browser history or hosting access logs. Avoid entering private or sensitive personal information into a public search field.
The event-search box filters the records already loaded in the browser. It does not submit each typed search term to a separate search provider. The selected sport and date are sent to this site’s results endpoint to request the matching records.
The correction report builder
The report builder formats text in your browser. It has no message-sending endpoint and does not upload the completed report. Its fields are not saved by the application in localStorage. Reloading or leaving the page may discard the text, subject to the browser’s own form-restoration behaviour.
Copying the report places it on your device’s clipboard if you choose that action. Clipboard history, device synchronisation or other browser features are controlled by your operating system and browser. Do not include private details that are unnecessary to explain a sporting or editorial correction.
Provider services and editorial imports
The server requests sports records from its configured providers and publication material from Docs Library. API credentials remain server-side and are not part of the browser’s page source. Reading a guide does not require the visitor to authenticate with those providers.
Generated site images and imported covers are served from the site’s own static files. If you follow an external reference link, the destination site has its own practices. The page’s referrer policy limits information sent when leaving for another origin.
Hosting logs and retention
The application records service and scheduled-job output for operation and troubleshooting. A Linux log-rotation example is included with the deployment files, but a proposed configuration is not evidence that it is installed on a production host.
The final hosting log retention, backups and monitored privacy contact have not yet been configured for this prelaunch deployment. Those details must be confirmed before public launch. This page does not state a retention period or a contact address that has not been verified.