Sixer is an editorial publication. The privacy note describes the editorial practice: the desk reads from public cricket feeds, writes dated notes and publishes source-tagged edits. Sixer does not run contests, hold wallets or store financial data.
The Sixer desk reads from public feeds — official broadcaster sites, team-association press releases and named cricket statisticians. The desk stores the editorial note, the source URL and the update time on the public site.
Public matchday feeds. Where a feed is private, the desk describes its editorial reputation without quoting the material.
The editorial note, the source URL and the update time. The desk does not store a reader account, a wallet or a withdrawal record.
Sixer does not collect a reader's platform credentials, KYC document, payment instrument or financial history. The privacy policy applies to the editorial practice only.
Sixer runs the desk on a static HTML / CSS / JavaScript stack. No third-party tracking cookies are loaded by the desk's own code.
The desk does not set first-party tracking cookies beyond a session-only preference cache for the mobile menu and the sticky CTA appearance state.
The desk loads Google Fonts CSS from Google's CDN. The CDN's own cookies may apply; the desk does not control that. The first-party access route and any embedded YouTube videos carry platform-controlled cookies.
A reader who wants to block the CDN cookies can use a browser privacy extension. Sixer's editorial stack remains usable without the CDN cookies; only the font and any embedded video break.
When Sixer files a correction, the desk publishes the correction on the same URL and updates the corrections log. Where a reader has emailed a tip that becomes a correction, the desk does not name the tipster in the editorial record.
The corrections log is open and dated. Sixer does not silently rewrite a published note; the editorial record is intact.
Where a reader email becomes a correction, the desk does not publish the tipster's name or email in the public record. The correction notes the fact and the source URL; the desk does not name the reader.
Sixer does not store a reader setting on the server. The mobile menu state, the sticky CTA state and any per-page preference are stored in the browser only.
Sixer publishes an editorial record on privacy: the corrections log, the source URL of every note, and the public-facing method statement.
Notes are dated, sourced and corrected on the same URL. The corrections log is public.
Where a note carries a source, the source URL is on the same line. The desk cross-references sources against public feeds.
Where a reader email becomes a correction, the desk does not publish the tipster's name or email in the public record. Anonymity is preserved.
Sixer stores reader-side settings in the browser only. The desk does not store server-side settings.
The mobile menu's open/close state is stored in the browser; the desk does not store it server-side.
The persistent CTA's appearance state is held in browser memory only; clearing the page resets it.
An open tag carries its state in the browser; the desk does not store it server-side.
The privacy note applies to the editorial practice. Sixer does not run contests, hold wallets or store financial data. The editorial record is the only record the desk maintains.
Notes are dated, sourced and corrected on the same URL. The corrections log is public.
Where a note carries a source, the source URL is on the same line.
Where a reader email becomes a correction, the desk does not publish the tipster's name or email in the public record.