Reference

Open rajdhaniyan legal terms and rights

This page sets out how we handle access, data use, account records and policy changes for India.

IndiaLocal lawData useAccount records

Explore jurisdiction checks and account handling

rajdhaniyan Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Our legal position is tied to the account and the jurisdiction linked to it. We do not treat every request the same way in every place, because access, data use and record handling can change with local law. When a request reaches us, we check the

1
registered name, phone number and the specific change you asked for before we act. If the request touches a wallet record, transaction trail or identity match, we may ask for a document that links you to the account so we do not update the wrong record.
2
We keep account and support data only for as long as we need it for service, dispute handling, security checks and legal duties. If a rule changes, we update this page and apply the new position from the update date forward. For India, the same approach
3
applies to UPI, Paytm, PhonePe and Google Pay flows linked to the account.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT ROUTES

Switch to contact paths for requests

When you need a legal change handled, use the path that matches the request type.

DATA CONTROLS

Browse how we handle account data

We keep legal handling separate from day-to-day browsing. Cookies help with session state, language choice and whether a policy message has already been seen; they do not change the account name or…

Data Handling

We collect the details needed to run the account, such as name, contact number, device signals and request logs. Payment references are kept only so we can match deposits or withdrawals to the correct account record.

Cookie Control

Cookies remember your session, page language and whether you have already accepted a policy message. You can clear them in your browser, but some pages may ask you to verify again.

Account Security

Keep your password and one-time codes private. We use login checks, device signals and withdrawal-match checks to reduce mistaken access, and we may pause a session if something looks off.

Record Retention

We keep account and support records only for the period needed for service, dispute handling, fraud checks and legal duties. After that, we archive or remove them using controlled processes.

Change Requests

When you ask for a change, send it from the registered contact and include the exact field you want updated. We compare it with current records before we change anything.

Access Requests

If you want to see, correct or close a record, use email or chat first. We will tell you what proof is needed, what can be changed and what must stay.

Open answers about access and records

These questions cover access, records, corrections and contact paths for this page. If your request touches account data or a region check, we verify it against the registered details before any change. Where local law matters, the answer can differ by location, so use the contact route tied to your account and include the exact action you want. We keep the response tied to your own record, not to a generic site message.

Access depends on local law and on whether your account details match the region we can serve. If a location check blocks a page, use the contact route and we will explain the next lawful step.

We keep the contact details, login trace, support history and payment references needed to run the account. We do not keep more than is needed for service, dispute handling, security checks and legal duties.

Yes. Send the request from your registered contact details and tell us which record set you want. We may ask a quick identity match before we share anything account-specific.

Use email or chat, state the exact field that is wrong and attach proof where needed. We compare the request with the current record and update only what we can verify.

Cookies store session state, language choice and whether a policy message has been seen. They help us keep the page flow consistent, but they do not change your account record or payment trail.

We keep records only while they are needed for account handling, dispute work, security checks and legal duties. After that period, we archive or remove them through controlled internal processes.

Use the email route for written requests and chat for quicker status checks. Include your registered name, phone number and the exact action you want so we can route it correctly.

Open rajdhaniyan legal terms and rights

Switch to contact paths for requests

Browse how we handle account data

Data Handling

Cookie Control

Account Security

Record Retention

Change Requests

Access Requests

Open answers about access and records

01 When can I access the site from India?

02 What account data do you keep?

03 Can I ask for a copy of my records?

04 How do I correct a wrong detail?

05 How do cookies affect my legal settings?

06 How long do you keep records?

07 Who should I contact for a legal request?

Related Pages