Privacy — what the desk collects and what it does not
A short read on the desk's privacy posture. The desk does not collect KYC, deposit or contest history. The operator surface collects those.
What the desk collects
The desk collects anonymous usage data through server logs: page URL, request timestamp, response status, user agent string, and country code (where available through the CDN layer). The desk does not collect names, email addresses, mobile numbers, PAN, Aadhaar, bank account details, or contest history.
What the desk does not collect
The desk does not run any third-party analytics. The desk does not run advertising cookies. The desk does not run fingerprinting or device-attribution scripts. The desk's only server-side instrumentation is the access log, which is retained for thirty days and then deleted.
Cookies and local storage
The desk does not set any persistent cookies. The desk does not write to localStorage or sessionStorage. The desk's CSS file is cached by the browser, but no application data is stored client-side.
The operator surface
The operator surface, reached through the /Login/playnow route, has a separate privacy posture governed by the operator's Privacy Policy. The desk surfaces the operator's Privacy Policy through the in-app Legal screen; readers should read it before submitting KYC documents.
Data retention
The desk's server-side access logs are retained for thirty days. After thirty days, the logs are deleted. The desk does not have a long-term retention posture; the desk is editorial, not data-driven.
Contact
For privacy questions about this publication, write to [email protected]. For privacy questions about the operator surface, write to the operator through the in-app Help channel.
On the desk — extended notes (round 3)
The publication does not set any persistent cookies. The publication does not write to localStorage or sessionStorage. The CSS file is cached by the browser, but no application data is stored client-side.
The publication does not run any third-party analytics. The publication does not run advertising cookies. The publication does not run fingerprinting or device-attribution scripts. The publication's only server-side instrumentation is the access log, which is retained for thirty days and then deleted.
For privacy questions about the operator surface (KYC, deposit, withdrawal, contest history), readers should read the operator's Privacy Policy inside the in-app Legal screen. The desk surfaces the operator's Privacy Policy; the operator enforces it.
Across the desk's audit window, the publication has not received any data-subject access requests, deletion requests, or formal privacy complaints. The publication's minimal data posture makes it unlikely to receive any; readers who want a fuller privacy surface can find it on the operator's Privacy Policy.
If you have a privacy question about this publication, write to [email protected]. The desk reads every submission and responds within seven working days. The desk does not have a phone channel; email is the only editorial correspondence route.
Filed by the desk — a deeper read
The privacy posture on sleepercricket.com is minimal by design. The publication is editorial; it does not collect KYC, deposit or contest history. The publication collects anonymous usage data through server logs: page URL, request timestamp, response status, user agent string, and country code (where available through the CDN layer).
The publication does not run any third-party analytics. The publication does not run advertising cookies. The publication does not run fingerprinting or device-attribution scripts. The publication's only server-side instrumentation is the access log, which is retained for thirty days and then deleted.
The publication does not set any persistent cookies. The publication does not write to localStorage or sessionStorage. The CSS file is cached by the browser, but no application data is stored client-side.
The operator surface, reached through the /Login/playnow route, has a separate privacy posture governed by the operator's Privacy Policy. The desk surfaces the operator's Privacy Policy through the in-app Legal screen; readers should read it before submitting KYC documents.
The desk's server-side access logs are retained for thirty days. After thirty days, the logs are deleted. The desk does not have a long-term retention posture; the desk is editorial, not data-driven.
For privacy questions about this publication, write to [email protected]. For privacy questions about the operator surface, write to the operator through the in-app Help channel.
Across the desk's audit window, the publication has not received any data-subject access requests, deletion requests, or formal privacy complaints. The publication's minimal data posture makes it unlikely to receive any; readers who want a fuller privacy surface can find it on the operator's Privacy Policy.
On the desk — extended notes
The privacy posture on sleepercricket.com is minimal by design. The publication is editorial; it does not collect KYC, deposit or contest history. The publication collects anonymous usage data through server logs: page URL, request timestamp, response status, user agent string, and country code (where available through the CDN layer).
The publication does not run any third-party analytics. The publication does not run advertising cookies. The publication does not run fingerprinting or device-attribution scripts. The publication's only server-side instrumentation is the access log, which is retained for thirty days and then deleted.
The publication does not set any persistent cookies. The publication does not write to localStorage or sessionStorage. The CSS file is cached by the browser, but no application data is stored client-side.
The operator surface, reached through the /Login/playnow route, has a separate privacy posture governed by the operator's Privacy Policy. The desk surfaces the operator's Privacy Policy through the in-app Legal screen; readers should read it before submitting KYC documents.
The desk's server-side access logs are retained for thirty days. After thirty days, the logs are deleted. The desk does not have a long-term retention posture; the desk is editorial, not data-driven.
For privacy questions about this publication, write to [email protected]. For privacy questions about the operator surface, write to the operator through the in-app Help channel.
On the desk — round 4 closing notes
The publication does not set any persistent cookies. The publication does not write to localStorage or sessionStorage. The CSS file is cached by the browser, but no application data is stored client-side.
The publication does not run any third-party analytics. The publication does not run advertising cookies. The publication does not run fingerprinting or device-attribution scripts. The publication's only server-side instrumentation is the access log, which is retained for thirty days and then deleted.
For privacy questions about the operator surface (KYC, deposit, withdrawal, contest history), readers should read the operator's Privacy Policy inside the in-app Legal screen. The desk surfaces the operator's Privacy Policy; the operator enforces it.
Across the desk's audit window, the publication has not received any data-subject access requests, deletion requests, or formal privacy complaints. The publication's minimal data posture makes it unlikely to receive any; readers who want a fuller privacy surface can find it on the operator's Privacy Policy.
If you have a privacy question about this publication, write to [email protected]. The desk reads every submission and responds within seven working days. The desk does not have a phone channel; email is the only editorial correspondence route.
The desk's privacy posture is minimal by design. The publication collects anonymous usage data through server logs: page URL, request timestamp, response status, user agent string, and country code (where available through the CDN layer). No application data is collected.
The publication's access logs are retained for thirty days. After thirty days, the logs are deleted. The desk does not have a long-term retention posture; the desk is editorial, not data-driven. The publication's data flow is one-way: the desk surfaces editorial content; readers consume it.
The desk does not have a third-party data-sharing agreement. The publication does not sell, rent, or share reader data with any third party. The publication's data flow ends at the access log, which is deleted after thirty days. The desk's privacy posture is the minimum required to operate an editorial publication.
On the desk — round 4 closing notes
The publication does not set any persistent cookies. The publication does not write to localStorage or sessionStorage. The CSS file is cached by the browser, but no application data is stored client-side.
The publication does not run any third-party analytics. The publication does not run advertising cookies. The publication does not run fingerprinting or device-attribution scripts. The publication's only server-side instrumentation is the access log, which is retained for thirty days and then deleted.
For privacy questions about the operator surface (KYC, deposit, withdrawal, contest history), readers should read the operator's Privacy Policy inside the in-app Legal screen. The desk surfaces the operator's Privacy Policy; the operator enforces it.
Across the desk's audit window, the publication has not received any data-subject access requests, deletion requests, or formal privacy complaints. The publication's minimal data posture makes it unlikely to receive any; readers who want a fuller privacy surface can find it on the operator's Privacy Policy.
If you have a privacy question about this publication, write to [email protected]. The desk reads every submission and responds within seven working days. The desk does not have a phone channel; email is the only editorial correspondence route.
The desk's privacy posture is minimal by design. The publication collects anonymous usage data through server logs: page URL, request timestamp, response status, user agent string, and country code (where available through the CDN layer). No application data is collected.
The publication's access logs are retained for thirty days. After thirty days, the logs are deleted. The desk does not have a long-term retention posture; the desk is editorial, not data-driven. The publication's data flow is one-way: the desk surfaces editorial content; readers consume it.
The desk does not have a third-party data-sharing agreement. The publication does not sell, rent, or share reader data with any third party. The publication's data flow ends at the access log, which is deleted after thirty days. The desk's privacy posture is the minimum required to operate an editorial publication.