Reference

How royaljeet handles your privacy

We collect only the account, device, payment and support data needed to run your royaljeet account, secure your wallet and answer your requests.

India data handlingUPI privacy contextPaytm and PhonePe recordsAccount security checks
royaljeet How royaljeet handles your privacy
HELP PATHS

Contact us about privacy requests

Privacy questions need a clear route, so we keep account help, payment-record checks and data requests separate from general lobby chat. Use the contact path that matches your request and include enough detail for us to verify you safely. We will not discuss private records with an unverified person, even if that person knows your email or mobile number.

Team online

Email privacy desk

Write to [email protected] from the email linked to your account. Include your account ID, the data request you want handled, and a clear way for us to reply.

Secure account chat

Use live chat after logging in when you want us to check account access, cookie choices, or a recent data correction. We will ask security questions before discussing private records.

Payment data route

If your request concerns UPI, Paytm, PhonePe or Google Pay records, send the payment reference and date. We use those fields only to match your wallet history with your account.

DATA CARE

How we manage privacy work

Our privacy work starts with collection control and ends with a recorded response to you.

Data we collect

During account creation we ask for details needed to identify your account, run security checks and keep your wallet records…

Cookie choices

Our cookie banner separates login cookies, security cookies and measurement cookies.

Payment records

UPI, Paytm, PhonePe and Google Pay references are stored with transaction time, amount, account ID and status.

Account security

Login activity, device signals and IP data help us spot unusual access, protect wallet actions and confirm whether a request…

Retention periods

We keep records for as long as they are needed for account service, dispute handling, security, tax, audit or legal…

Change requests

You can ask us to correct profile details, update contact data, receive a copy of eligible records or delete data…

Privacy Policy questions answered clearly

The answers below explain how this Privacy Policy applies to your account data, wallet records, cookies, verification checks and contact rights. They are written for India account holders in plain language. If your situation involves a legal dispute, a payment mismatch or a security concern, contact us through the privacy path so we can check the exact record.

We collect account details, contact data, login records, device signals, payment references, verification documents when required, cookie choices and support conversations. Each data type is tied to account service, security, legal duties or your requests.

UPI, Paytm, PhonePe and Google Pay records help us match wallet credits, investigate failed transactions, process withdrawals and answer payment history requests. We use reference numbers, dates and amounts for matching, not unrelated personal profiling.

Yes. Contact the privacy desk from your registered email and tell us what record range you need. We verify your identity first, then provide eligible account data in a format we can safely share.

Yes. You can request corrections for eligible profile, contact or wallet-linked details. Some records, such as completed transaction logs, may need to remain unchanged for audit, tax, dispute or legal reasons.

Retention depends on the record type and legal need. Account, payment, verification and security records may be kept while needed for service, dispute handling, audits, tax duties or fraud prevention, then deleted or anonymised.

We use cookies for login sessions, fraud checks, language settings, site measurement and remembering your choices. Optional measurement cookies can be changed through privacy controls; essential cookies keep account access working safely.

Only authorised staff and contracted service partners can access data needed for assigned tasks. Examples include payment processors, verification tools, hosting services and security systems. Access is limited, logged and tied to operational need.