The jackpot desk reads from the reader's browser only what the browser sends by default. The desk stores only what the reader chooses to send to the desk's editorial channels. The desk never asks for, never stores, and never publishes the reader's name, phone, email, address, or government identity number.
Adult readers only. The desk publishes for adult readers in jurisdictions where skill-game play is permitted. The desk does not run a wallet, an account system, or a customer database. The operator handles the reader's account on the operator's own domain.
The desk's reading is bounded. The desk reads what the browser sends, logs what the reader sends to the desk, and never reads what the reader types into the operator's site.
The desk's web server logs the standard request line: the URL the reader opened, the time of the request, the response code, and the user-agent string. The logs are retained for the desk's operational window and then rotated.
The desk counts how many times a page was opened. The desk does not tie the count to a name, an email, or a device identifier. The aggregate is used to plan editorial coverage.
Where the reader sends the desk an email, the desk reads and answers the email. The desk does not subscribe the reader to a marketing list. The desk logs the editorial note when it surfaces a primary source the desk can follow.
The desk does not set tracking cookies. The desk's site may set a small set of functional cookies (for example, a font-display preference) where the reader's browser requests the desk's font assets. The desk does not use these to track the reader across sites.
The desk is a reference publication, not a customer database. The reader's identity, the reader's stake, and the reader's hand history live on the operator's site, not on the desk's.
The desk does not ask for, does not store, and does not publish the reader's name, phone, email, postal address, or government identity number. The desk does not run a customer database.
The desk does not see the reader's stake, the reader's deposit ledger, the reader's withdrawal queue, or the reader's bonus balance. Those records live on the operator's site.
The desk does not see the reader's hand history, the reader's game log, or the reader's tournament record. The operator publishes those records to the reader's account, not to the desk.
The desk does not see the reader's KYC documents, identity proofs, address proofs, or selfie verifications. The operator's KYC queue handles those documents on the operator's site.
The desk reads only the country code the reader's browser sends. The desk does not read the reader's precise geolocation, the reader's IP-based street address, or the reader's device fingerprint.
The desk does not see the reader's account. The operator's privacy notice is the binding source for what the operator stores, how the operator stores it, and how the reader requests a deletion. The desk links the operator route.
The desk's page may set a small set of functional items when the reader's browser requests the desk's font assets. The desk does not set tracking cookies. The desk does not embed third-party advertising scripts. The desk does not embed social-share buttons that ping the platform on page load.
The desk's editorial pages link to the operator's site through a plain anchor tag with a rel-sponsorship marker. The reader who clicks the link opens the operator's site on the operator's domain, where the operator's own privacy notice and cookie policy apply.
Source frame: a closed notebook on a wooden table, used as the editorial cover for the cookie section.
The desk honours five rights on the editorial-side data the desk reads. Where the data lives on the operator's side, the operator's privacy notice governs.
| Right | What the desk does |
|---|---|
| Access | The reader can ask the desk what editorial-side data the desk holds on the reader; the desk answers within the working-day window |
| Correction | The reader can ask the desk to correct editorial-side data the desk holds; corrections are logged with date and source |
| Erasure | The reader can ask the desk to erase editorial-side data the desk holds; the desk erases the data on the next retention cycle |
| Restriction | The reader can ask the desk to restrict the processing of editorial-side data the desk holds; the desk logs the restriction |
| Complaint | The reader can complain to the relevant data-protection authority where applicable; the desk links the published authority register where one applies |
For account-side data, the reader reaches the operator's privacy notice on the operator's domain. For editorial-side data on this desk, the contact page lists the working channel.
No. The desk does not ask for, does not store, and does not publish the reader's name. The desk is a reference publication; the operator handles the reader's account on the operator's own domain.
No. The desk does not set tracking cookies. The desk's page may set a small set of functional items when the reader's browser requests the desk's font assets. The desk does not embed third-party advertising scripts.
Yes. The reader asks the desk through the contact page, citing the data and the channel the reader used. The desk erases the editorial-side data on the next retention cycle and logs the erasure with date and source.
The operator. The operator publishes a privacy notice on the operator's domain. The operator's privacy notice governs the operator's storage, the operator's retention, and the reader's right of erasure on account-side data.
No. Reader notes addressed to the desk stay with the desk unless the reader names the operator as the destination. The desk does not forward reader notes to the operator's customer support queue.
The desk is a reference publication; the operator is reached through the affiliate route. The desk does not name a specific operator, director, or registered address. Where a fact cannot be verified from a primary source, the desk marks it "to be verified locally".
Corrections are logged with date and source when an observation is found to be inaccurate.
The desk accepts commercial support to keep the publication running. The support relationship is disclosed on the about page. The desk's editorial coverage is independent of the commercial support.
The desk does not own the operator, does not run contests for the operator, and does not settle payouts. The desk reviews and reports; the operator deals and settles.
Age 18+. The privacy notice is published for adult readers in jurisdictions where skill-game play is permitted.
Read the responsible-play controls. The deposit-limit and session-timer guides are linked from the responsible-play hub.