Legal · Privacy
Privacy notice
The data the vegas pro editorial desk collects through this site, what it is used for, how long it is retained and the rights the desk recognises. This notice is the desk's; the platform's notice describes its own practices.
For adult readers (18+) only · Editorial information, not legal advice · This notice describes the desk's practices; the platform's own privacy notice describes theirs
What this notice covers
Scope of this privacy notice
This notice covers the vegas pro editorial desk at vegasproin.com. It describes the personal data the desk processes when an adult reader visits the editorial pages of this site, what the desk does with that data, how long the desk retains it and the rights the reader can exercise. It does not cover any third-party site the desk links to, including the partner site that the mobile sticky contextual CTA directs readers to under /Login/playnow/. The partner site's notice governs that site.
The desk treats this notice as a working document. Where the desk's practices change, the notice is updated and the last-reviewed date at the bottom of this page moves forward. The desk does not retroactively alter what was held under a previous notice.
Data the desk collects
What the desk actually receives
The desk collects three categories of data, and only these three:
Server logs
IP address, user agent, request path, response code and timestamp. These are generated automatically by the hosting infrastructure for every HTTP request. They are not enriched with names, emails or account identifiers.
Contact messages
Email correspondence sent to the address on the contact page. The desk only sees what the reader chooses to write. The desk does not subscribe the reader to a list.
Tip submissions
Reader-supplied corrections, tips and editorial feedback submitted through the contact route. The desk verifies before publication and deletes the raw material after the editorial record is complete.
The desk does not collect KYC documents, PAN, Aadhaar, date of birth, biometric data, payment instrument details, mobile numbers or any other identifier the desk has not listed. The desk does not run a real-money rummy platform and has no need for such data.
Cookies
What the desk stores on the device
The desk sets no tracking cookies. The desk runs no third-party analytics that set cookies. The desk embeds no advertising that sets cookies. The desk's site loads only the resources required to render the page: a single self-hosted stylesheet at /assets/css/site.css, a single self-hosted script at /assets/js/menu.js that powers the mobile drawer, the page's own WebP images, and two Google Fonts requests. Google Fonts is loaded over fonts.googleapis.com with a preconnect; Google may log the request from your IP, and Google's privacy policy applies to that log.
The reader who prefers the desk's pages without the Google Fonts request can disable web fonts in the browser; the desk's CSS falls back to system-ui and a serif fallback, and the page remains legible.
Use of data
What the desk does with what it collects
Server logs are used to operate the site, to detect abusive traffic, to debug rendering defects and to confirm that links and assets return the response code the desk intends. Logs are not used for advertising, retargeting or audience profiling. Logs are not sold or shared with marketing parties.
Contact messages are used only to respond to the reader who sent them. Where a message is a correction that the desk publishes, the published version may be paraphrased; raw messages are not republished. Where a message contains an editorial tip, the desk uses it to verify the underlying claim and then deletes the raw tip after the editorial record is complete.
Retention
How long the desk keeps what it collects
| Data category | Retention window | Deletion method |
|---|---|---|
| Server logs | 30 days | Rotation + overwrite |
| Contact email correspondence | Up to 90 days, longer for open editorial threads | Manual purge after the thread closes |
| Tip submissions (raw) | Until the editorial record is complete | Manual purge after publication |
| Backup snapshots | 30 days rolling | Overwritten by the next snapshot |
The reader who wants a specific communication deleted should write to the desk through the contact page. The desk will action the request within 30 days. Where the request concerns content already published, the desk will remove or correct the published content as well, with an editorial note where appropriate.
Sharing and disclosure
What the desk does and does not share
The desk does not sell, lease or share the data it collects with third parties for marketing purposes. The desk does not place reader data into advertising networks, retargeting segments or lookalike audiences.
The desk may share data with the following categories of recipients as part of normal operations:
- Hosting and CDN provider: The desk's pages are served through a managed hosting provider and a CDN; the provider receives request logs in the course of serving the site. The provider's own privacy notice governs what they retain.
- Legal compulsion: Where the desk receives a binding legal order from a competent Indian authority, the desk will disclose only the data that order requires and will challenge over-broad orders where it is reasonable to do so.
- Successor operator: Where the desk is acquired or transferred, the acquiring party inherits this notice; the desk will notify readers through the homepage banner where the transfer is material.
Reader rights
What the reader can ask the desk to do
The desk recognises the rights a careful adult reader can exercise over data the desk holds. Where the reader's request falls within the desk's practice, the desk action it within 30 days of receipt.
Access
The reader can ask what the desk holds about them. The desk will respond with the data and the retention window.
Correction
The reader can ask for a correction where the desk's record is wrong. The desk will correct or annotate the record.
Deletion
The reader can ask for deletion of contact messages or tip submissions. The desk will action within 30 days and confirm in writing.
The desk does not hold a profile of the reader beyond the items listed above. Where the reader believes the desk holds something else, the desk will investigate and respond.
Children
Under-18 traffic is not targeted
The desk writes for adult readers (18+). The desk does not knowingly collect personal data from anyone under 18. The desk does not target under-18 traffic through advertising, content or distribution. Where the desk becomes aware that data has been received from someone under 18, the desk will delete the data and confirm in writing.
A parent or guardian who believes a minor has interacted with the site should write to the desk through the contact page; the desk will respond within seven days.
AI-generated content
How the desk handles AI-assisted drafting
The desk uses generative-AI assistance selectively for first-draft summaries, keyword clustering and image planning. Editorial copy is reviewed, edited and signed off by a named desk editor before publication. The desk does not publish unedited AI output. Image briefs that are sent to a generation provider are reviewed before they leave the desk and the resulting images are rejected if they fail the desk's editorial standards (no fabricated text, no platform logos the desk cannot verify, no neon or jackpot imagery).
The desk does not feed reader correspondence into a generative-AI training pipeline. Where reader data is used for editorial verification, the desk reads the message and acts on it; the desk does not upload it to a third-party AI provider.
Security
How the desk protects what it holds
The desk's site is served over HTTPS only. The desk's administrative access is protected by multi-factor authentication. The desk's email correspondence is held in an account protected by hardware-key MFA. The desk's hosting provider enforces its own access controls, which the desk has reviewed.
No system is perfectly secure. The desk will notify affected readers through the homepage banner and through the contact channel where a data incident is material and the reader can be identified.
Changes
How the desk updates this notice
The desk updates this notice when its practices change. The last-reviewed date at the bottom of this page reflects the most recent update. Material changes are noted on the homepage for at least 30 days. The desk does not retroactively alter what was held under a previous notice.
A reader who wishes to be notified of a material change before it takes effect can write to the desk through the contact page; the desk will keep the reader's contact on file for the notice window only and will delete it afterwards.
Cross-border readers
Where the reader is outside India
The desk is written for adult readers in India. The desk's pages describe Indian rules, Indian platforms and Indian responsible-play controls. The reader outside India should treat the desk's pages as context, not as a legal reading of the reader's local rules. The desk does not warrant the accuracy of its pages for readers in jurisdictions where the underlying rules differ from the Indian rules the desk reads.
Where the reader is in a jurisdiction where the desk's pages are not appropriate, the reader should rely on local primary sources. The desk's contact page accepts editorial feedback; the desk does not provide legal advice to readers in foreign jurisdictions.