Reference

Open 3rr Privacy Policy

3rr sets out what we collect when you open an account, how cookies and device data help us keep access steady, and why transaction references stay on file…

IndiaCookiesUPILocal law
Browse lobby Read FAQ
3rr Open 3rr Privacy Policy
CONTACT PATHS

Switch to privacy contact paths

If you want to ask what we hold, correct a detail or challenge a use of your data, contact us through the in-account message box, the…

Message box Log in and send us a privacy request from the account tied to your…
Contact form If you cannot access the account, use the form on our site and share…
Privacy desk For access, correction or deletion requests where local law permits, write to the privacy…
DATA SHIELD

Browse security and storage rules

We keep this policy practical: the data we store stays tied to a clear purpose, the cookies we set are limited to session and preference use, and the security checks watch for…

Data handling

We keep only the details needed to run your account, match payments, and respond to requests. That includes contact fields, device signals and transaction references, all tied back to the purpose you agreed to when you opened the account.

Cookies

Cookies help us remember session state, language choice and the pages you returned to, so you do not repeat the same steps each time. You can clear them in your browser, though some settings may reset.

Account security

Login checks compare password attempts, device patterns and access timing to spot misuse. If something looks unusual, we may ask you to confirm from a registered channel before we allow changes to your profile.

Retention

We store records only for as long as needed for account support, dispute handling, audit checks and legal duties. When the retention period ends, we remove or anonymise the data under our internal rules.

Request changes

If your contact detail, address or payment detail changes, send the update through support from your registered account or email. We will process it after a verification step and where local law permits.

Local law

When local law allows access, correction or deletion, we act on the request within the scope we are permitted to keep or share. If a request conflicts with a legal duty, we explain the limit in our reply.

Open privacy questions with us

These answers cover the privacy points most often tied to your account, cookies, payment records and contact requests. If your request needs a legal check, the reply you receive will follow the rules that apply in your area. We keep the process tied to the same support paths listed on this page so you know where to send each request and what proof may be needed. That helps us match the request to the right account and avoid delays.

We collect the details you enter, the contact route you use, device signals, cookie data and payment references needed to run the account and answer support requests properly.

Cookies keep you signed in, remember language choices and reduce repeated steps. They also help us spot unusual session patterns so we can protect account access more quickly.

Yes, we keep the transaction reference, status and timing needed to match a payment to your account and handle disputes. We do not treat that record as a full payment profile.

You can ask through support from your registered account or email. We will verify the request, apply the change where local law permits and keep a record of the action.

Only staff or service partners who need it for account handling, security checks, payments or legal duties can access it. We limit access by role and log the important actions.

Send a request through the contact paths listed on this page. We will check your identity, confirm what we can share and respond within the limits of local law.

Related Pages

About Us Penalty Series Power Hold Register