Reference

w8ben Privacy Policy for India

This page sets out how we handle your personal data when you open an account, send a support message or use our payment checks.

IndiaCookiesSecurityRetention
w8ben w8ben Privacy Policy for India
CONTACT PATHS

Where to Send Privacy Requests

If you want a copy of your account data, need a correction, or want us to limit a message type, use the contact path below.

Email request Write from the address on your account and include the change you want, the…
Account form Use the form inside your account when you need correction, export or deletion handling.
Reply thread If you already have an open message with support, continue there so the full…
SECURE HANDLING

How We Keep Data Limited

We collect only the fields we need for account setup, payment matching, eligibility or region checks where law allows, and support follow-up.

Collection scope

We keep the account profile, device log and transaction reference set small on purpose. That lets us confirm identity, handle service messages and check for suspicious access without building a wider file than needed.

Cookie use

Cookies remember your signed-in state, session length and language choice. If you clear them, some parts of the page will ask you to sign in again, but the policy data already linked to your account stays in place.

Account safety

We use device markers, password checks and unusual-login alerts to keep account access tied to the right person. If we see a mismatch, we may pause the request path until the account is checked.

Retention window

We keep records only for the period needed for security, accounting reconciliation and legal duty. After that, the data is deleted or archived in a form that is less directly usable, where local law permits.

Change requests

You can ask us to correct name, contact or wallet-related fields that are wrong. We will update what we can once the request is verified, and we will explain any part we must keep unchanged.

Contact owner

Send privacy requests to the channel linked on your account page. We use that route to confirm identity, track progress and answer within the same thread, so you do not have to repeat your case.

Privacy Questions You May Have

These answers cover the parts people ask about most often: what we collect, why we keep it, how long it stays with us and how you can ask for a correction. If your request is tied to local law, we follow the rule that applies in your region and confirm any limits before we act.

We collect the details needed to create and protect the account, such as your contact data, device markers, messages you send us and any record linked to a deposit or withdrawal check. We keep the set tight and only for stated reasons.

Cookies keep your session active, remember language choices and reduce repeated checks on the same device. They do not replace the account record, and you can clear them in your browser if you want the page to forget local session state.

Yes. Send a request through the contact path on your account and we will confirm whether we can share it under local law. If parts must stay hidden for security or legal duty, we will explain the limit.

We keep records only as long as needed for security, dispute handling, audit trails and legal duty. When that purpose ends, we delete or archive them based on the record type and the rule that applies in your region.

When you use UPI, Paytm or PhonePe, we may send the minimum details needed to confirm status, detect mismatch and stop duplicate entries. We do not use those records for unrelated purposes, and we keep the sharing narrow.

Use the request path in your account and tell us exactly which field is wrong. After we verify the request, we update what we can and tell you if any part must remain as-is for legal or security reasons.

A support agent trained on data handling replies from the same thread you use to contact us. If the request needs extra checking, the case can move to a specialist so the thread stays intact.