Reference

r0blox Privacy Policy for India accounts

At r0blox, this page sets out how we handle your privacy when you open an account, sign in, or send a request to support.

Data UseCookiesSecurityIndia Law
Explore the lobby Read FAQ
r0blox r0blox Privacy Policy for India accounts
HELP ROUTES

Ways to reach our team

If you need help with a privacy request, use the channel that matches your account.

Email Send a message from the address linked to your account. We use that match to confirm ownership before we release records, make a correction, or close a request, and we may ask for one more check if the request is sensitive.
In-account form Use the in-account form for access, correction, or deletion requests. It keeps the request tied to the right profile from the first step and reduces back-and-forth for us, especially when we need to match a phone number or device change.
Reply window If you need a quick check, reply through the contact path shown on the page during posted support hours. We will tell you what extra proof we need before any sensitive change, and we will explain the next step clearly.
DATA CARE

How we keep your records

We store account records, cookies, device signals, and payment references only for the purpose for which each item was collected.

Account records

We keep the details you enter at sign-up and later changes to your profile so we can run your account…

Cookies

Cookies help us keep you signed in, remember language choices, and check whether pages load as expected.

Device logs

We log browser type, device model, IP address, and session timing to spot unusual access and protect accounts from misuse.

Payment trails

When you use UPI, Paytm, PhonePe, or Google Pay, we retain the transaction reference and status needed to confirm a…

Retention

We keep data only for as long as it is needed for support, record-keeping, dispute handling, or legal duties, then…

Your requests

You can ask for access, correction, or deletion through support.

Privacy questions you may ask

These answers cover the questions we hear most about account data, cookies, retention, and request handling. If you need a change, send it from your registered contact so we can verify the account before acting. When a local rule limits what we can share or remove, we explain the limit and keep the rest of the process simple, clear, and tied to your request.

We collect the details you enter, device and browser signals, and the transaction references linked to deposits or withdrawals. That lets us run the account, spot unusual access, and answer privacy requests without asking you to repeat the same fields.

Cookies help us keep you signed in, remember language choices, and check whether pages load as expected. You can clear them in your browser, but some settings may need to be chosen again after that.

Yes. Send a request from your registered account and we will verify ownership before sharing the records we can legally disclose. If a local rule restricts part of the file, we will state that limit clearly.

Ask support to update the field that changed, such as your name, phone number, or email address. We may ask for a fresh check so the update reaches the right account and does not affect another person's record.

We keep data only while it is needed for account use, dispute handling, audit trails, and legal duties. After that, we remove or anonymise it according to our retention schedule and any local rule that still applies.

Use in-account messaging or the email address shown in support. Keep your registered contact details ready, because we may need to confirm ownership before we process a request or share any record from the file.

Related Pages

About Us Spribe Aviator Diamond Strike r0blox Login