Privacy Policy

What is collected

Three things, none of which identify you as a person:

• Traffic counts, in aggregate. Page views, rough region, broad device class. Enough to tell whether a guide is being read; nowhere near enough to identify a reader. Any IP used for approximate location is cut short before storage and thrown away afterwards.
• Hosting logs. The platform we host on keeps the usual request records for abuse prevention. They expire on their own schedule and are not something we sit and read.
• Whatever your own browser remembers. An expanded FAQ, a scroll position — held locally on your device, invisible to us, and gone when you clear site data.

What is not collected

Easier to list what is absent. Nobody can register here. There is no form to submit, no list to join, and no way to hand us a payment detail. We run no ad cookies, no tracking pixels shared with other sites, and no arrangement with any data broker. Nothing here reads your precise position, your contacts, your messages or your files. You will not see a consent banner because there is no consent to collect.

Retention

Traffic counts survive about two years, in a shape that could not be resolved back to a person even if somebody wanted to. Hosting logs clear out inside a month.

Slow down here — this is the half where identity documents and money actually change hands. The app is run by someone else entirely, under a policy you agree to at registration inside it. We cannot see that data, cannot answer questions about how it is held, and cannot remove any of it on your behalf.

An app of this type holds:

• Your mobile number and a hashed password. The number is the account identifier. A properly built platform never stores a password in readable form.
• KYC documents. Identity papers and a selfie, submitted once, required before withdrawal limits lift.
• Payment details. The UPI handle or bank details you supply, plus transaction amounts, status and timestamps. Card numbers and UPI PINs remain inside the payment provider.
• Gameplay and wallet history. Stakes, sessions, bonus state and withdrawal requests.
• Referral and agent data — and this one is worth pausing on. Because Raja7 runs an agent programme, the platform necessarily records who invited whom and how much each invitee bets. That is a social graph plus a spending record, held about people who are not you, generated by your invitations. Anyone sending referral links should understand that is what the mechanism requires.
• Device and usage data. Device model, Android and app version, IP address and login history, used for fraud detection.

Indian data protection law, and its equivalents in other jurisdictions, gives you a set of entitlements: see what is held, correct it, erase it, or halt its processing.

Pointed at this site, they find almost nothing to work on — there is no account here and no record with your name attached. Pointed at the app, they matter a great deal, and they cover your KYC file and the referral graph your invitations built. Those requests belong in Raja7's own support channel, which is both the only place with the access to act and the only place that can tell you the erasure went through.

Minors

The subject here is an adults-only product and nothing on the site is aimed at under-18s. No data is knowingly gathered from a minor, and in practical terms a child could not submit anything to us if they tried — there is no channel through which to do it.

Sites we point at

Outbound links reach payment providers, Android documentation and support helplines. Each runs under its own rules, not these. Our involvement ends at the link itself.

Revisions

Amendments appear on this page with the date at the top adjusted. Nothing is archived; whatever you are reading is the version in force.

See also: Terms & Conditions, Disclaimer, Responsible Gaming.