What the desk collects
The desk collects no personal data from readers. The desk does not run a comments section, a newsletter sign-up, an account system or a payment flow. The desk's only data point is the operator's first-party affiliate route, which is configured at the project level and which does not pass reader data to the desk.
The desk's server logs are limited to standard request lines for 30 days. The logs record the request path, the response code, the response size and the referrer. The logs do not record the requester's IP address, the requester's user-agent or the requester's device fingerprint. The logs are used to keep the desk responsive and are not tied to reader identities.
What the desk does not collect
The desk does not collect names, emails, phone numbers, PAN, Aadhaar, UPI IDs, addresses, IP addresses or device fingerprints. The desk does not run third-party analytics. The desk does not run social pixels, marketing pixels, retargeting pixels or attribution pixels. The desk does not embed third-party scripts that read the visitor's cookies.
The desk does not place cookies on the visitor's device. The desk does not use local storage, session storage, IndexedDB or any other client-side persistence layer. The desk's only persistent client artefact is the browser's own cache, which is governed by the browser's own cache policy and contains no personal data.
What a reader can do
A reader who wants to contact the desk can use the contact channel listed on the contact page. A reader who wants the desk to remove any data that may have been collected by accident can use the same channel and the desk will respond within seven days. The desk's standing response is to take the request seriously, to confirm what was collected, to delete what was collected and to publish a dated note describing the request.
A reader who wants to verify the desk's claim can do so by reading the desk's verifiable record: the server logs, the desk's HTTP headers, the desk's robots.txt and the desk's llms.txt. A reader who wants to ask the desk a question can do so by writing to the contact channel. The desk's standing response is to publish the question and the desk's answer in the next desk pass, with the asker's name redacted unless the asker has asked to be named.
The operator's privacy policy
The operator's privacy policy applies to the operator's product, not to the baccarat editorial desk. The desk publishes a pointer to the operator's privacy policy from the safety chapter so a reader can read both documents side by side. The desk does not paraphrase the operator's policy and the desk does not publish language that suggests the operator's policy is flexible.
The desk reserves the right to update this summary. The desk will publish a dated correction note at the foot of the affected chapter whenever the summary changes in a way that affects the reader's reading. The summary is not a contract and the desk is not a legal advisor. The desk's standing position on the operator's data handling is published in the safety chapter and the desk reviews the operator's policy at every desk pass.
Changes to this summary
The desk publishes a dated note at the foot of this chapter whenever the summary changes. The summary is reviewed at every desk pass and the date of the last review is published at the top of the chapter so a reader can answer the question "when was this last checked" without leaving the page. The desk's standing policy on corrections is published in the terms chapter and the desk applies the same policy here.
The desk refuses to publish any change to this summary that reduces the reader's privacy. The desk's standing rule is that every change to this summary must be at least as reader-protective as the previous version. Where a change is necessary, the desk publishes the change with a one-paragraph rationale and the date the change takes effect.