Desk page · Privacy
Privacy policy: what the almanac collects, and what it never does.
Ludotoday is an editorial almanac, not a ludo operator. The almanac does not run a wallet, does not hold KYC documents, and does not process deposits. This page lists exactly what data the almanac receives when a reader opens a chapter, what data is delegated to the third-party scripts on the page, and how a reader can request deletion or correction under the Digital Personal Data Protection Act 2023.
Updated 12 August 2026 · Editorial desk, Ludotoday
01 · Lede
Plain-English summary
The almanac is a static publication. Every chapter on the site is a prebuilt HTML page; there is no reader account to register, no email to provide, no KYC form to fill in. The almanac does not have a wallet, does not accept deposits, and does not pay out winnings; those operations sit on the third-party apps the almanac links to, and the privacy practices of those apps are governed by the apps themselves, not by this page.
Read this page in two passes. Sections 03 and 04 cover what the almanac actually receives in its own logs. Section 05 covers the third-party scripts and outbound links on each chapter. Section 06 lists the rights a reader has under Indian law and how to exercise them through the customer-care desk.
02 · What this policy covers
Scope and out-of-scope
In scope
The almanac at ludotoday.com and its chapter subdirectories. Subdirectories include /dice-probability/, /token-strategy/, /format-classic/, /format-quick/, /format-1v1/, /format-2v2/, /format-tournament/, /platform-reviews/, /wallet-kyc/, /how-to-play/, /bonus-code/, /refer-code/, /is-legal/, /responsible-play/, /customer-care/, /about/, /privacy/, /terms/, /news/, and the dated news briefings under /news/.
The play-now routing stub at /Login/playnow is hosted on a third-party domain. The privacy practices of that domain are governed by the third party's own policy; the almanac only sends a referral parameter through that stub.
Out of scope
Third-party apps linked from chapter pages. Each app the almanac links to publishes its own privacy notice; readers who decide to deposit, share KYC documents, or play for real money on a linked app should read that app's policy before proceeding.
State-level differences in privacy enforcement are not the almanac's reading. Where a reader sits inside a state with additional privacy protections, the almanac honours those protections on top of the baseline set out in this page.
03 · What the almanac collects
Logs, cookies, and the RSS feed
The almanac does not run analytics scripts that build a per-reader profile. The almanac does not place advertising cookies. The almanac does not run a third-party chat widget that records sessions. The only first-party data the almanac holds is the server access log, aggregated traffic counts, and any data a reader volunteers through the customer-care desk or the RSS subscription form.
The server access log holds the IP address only for the 30 days required to operate the site (rate-limit, spam-filter, abuse-handling); after aggregation the IP is dropped. The almanac does not sell the access log, does not share it with advertising networks, and does not use it to build a per-reader profile.
04 · What the almanac never collects
Categories that never leave your device
Never collected
The almanac never asks for, never stores, and never receives: a real name, a date of birth, an Aadhaar number, a PAN number, a bank account number, an IFSC code, a UPI handle, a credit card number, a debit card number, a CVV, a one-time password, or a photograph of an identity document. The almanac has no signup form. The almanac has no wallet form. The almanac has no deposit form.
Where a chapter instructs a reader to enter data on a third-party app, that data sits on the third-party app, not on the almanac. The almanac cannot retrieve it, redact it, or delete it; the third-party app's policy applies.
Never inferred
The almanac never infers: gender, caste, religion, political affiliation, health condition, sexual orientation, or biometric identifier. The almanac never infers a precise geolocation beyond the country-level IP geolocation used to route the request. The almanac never runs fingerprinting techniques; there is no canvas fingerprint, no audio fingerprint, no font fingerprint.
State-level inference (Andhra Pradesh, Tamil Nadu, Telangana, Odisha, Assam, Sikkim, Nagaland, Meghalaya, Manipur, or any state the Public Online Gambling (PROG) Act 2025 names as restricted) is the reader's responsibility: the almanac does not geofence content on the basis of state.
05 · Third-party scripts and outbound links
Who else runs on a chapter page
The almanac fonts come from Google Fonts and are loaded with a standard rel="stylesheet" tag in the head of every chapter. The almanac CDN sits in front of every chapter (Cloudflare or equivalent), which sees the same data any CDN sees. The almanac links to third-party apps from signup, deposit, customer-care and "play now" buttons; the link is marked rel="sponsored nofollow noopener noreferrer" so the click is not endorsed by the almanac for ranking purposes.
The almanac does not run advertising scripts. The almanac does not embed social widgets (no Facebook Pixel, no LinkedIn Insight Tag, no X pixel). The almanac does not load a third-party comment system. Where a reader wants to share a chapter on a social network, the reader copies the chapter URL and posts it through the reader's own account; that is a reader action, not an almanac script.
06 · Reader rights under the DPDP Act 2023
How to withdraw consent, request deletion, or correct a record
Rights the almanac honours
A reader has the right to obtain a copy of personal data the almanac holds, the right to correct inaccurate personal data, the right to request deletion of personal data, the right to withdraw consent for processing, and the right to nominate another individual to exercise these rights on the reader's behalf.
Where the almanac holds RSS subscription data or a correction-request record, the almanac responds within thirty days of a verified request, in line with Section 12 of the Digital Personal Data Protection Act 2023.
Limits on those rights
The almanac is not a credit-information company, not a healthcare provider, not a financial-services firm. The exceptions that exist for those categories in the DPDP Act 2023 do not apply to the almanac; the almanac honours the reader's right to deletion and the right to correction on the data the almanac actually holds.
Where data was collected for abuse handling (rate-limit log, spam filter), deletion may be denied if the data is still required to resolve an open abuse report; the almanac explains the reason in writing within thirty days.
07 · Contact and corrections
How to reach the privacy desk
Privacy requests, data deletion requests, correction requests, and consent-withdrawal requests should be sent through the customer-care desk. Include the chapter URL or the RSS subscription email so the desk can locate the data; the desk responds within thirty days, in line with the Digital Personal Data Protection Act 2023.
Where a reader would rather write directly to the editorial desk, the editorial correction address is published on the about page. The privacy desk is a duty the editorial desk carries; both inboxes reach the same desk.