Reference

Open the bovada Privacy Policy

This page explains how we handle the account details, device signals and support messages you share with bovada, so you know what we collect, why we use it…

IndiaUPIPaytmPhonePe
bovada Open the bovada Privacy Policy
CONTACT PATHS

Switch to the right privacy contact

If you want to ask how a record was used, what we keep, or how to amend a detail, start with the contact route inside your account.

Account chat Send a privacy request from the chat area in your account so we can match it to your profile and log the request date before we reply.
Support email Use written mail for copies, corrections or deletion requests where local law permits. A written trail helps us verify the exact record you want changed.
Footer contact If you cannot reach chat, use the contact details in the footer. Include your registered email and the account detail you want us to check so we can find it faster.
CONTROLLED HANDLING

Browse the controls that protect your data

We use the data you submit to confirm identity, keep the wallet record accurate and reply to your requests.

Data handling

We use form entries and account activity to run your profile, settle support queries and prevent duplicate records. Only the details needed for that purpose stay in active use.

Cookie use

Cookies remember your session, language choice and on-page settings; browser controls can remove them, though some screens may ask you to sign in again or reset your preferences.

Account security

We may ask you to confirm email, phone or recent account actions before we share data or change an account detail, so we do not expose private records to the wrong person.

Retention

We keep records for as long as they are needed for the account, support, dispute handling or legal duties. After that, we delete or archive them according to the retention rules that apply to the record type.

Request changes

Send the exact field you want changed and the updated value. We will check the request, confirm the account and make the change where local law permits, then let you know once it has been logged.

Contact route

Use account chat, email or the footer contact route so the request lands with the right team and can be tracked from start to finish without repeating the same details.

Open answers about privacy

These answers cover how we collect, use, store and correct data, plus what happens when local law changes. If your request is about your own account, send it through the support route above so we can verify it, keep the thread in one place and reply with the right context.

We collect the details you enter for the account, the device and browser signals your session sends, and the messages you send to support. We keep only what we need for the service, account checks and lawful record keeping.

Cookies help us keep you signed in, remember settings and recognise repeat sessions from the same device. You can clear them in your browser, but some pages may ask you to sign in again or reset your preferences.

Yes. Send a request through the contact routes above, and we may ask you to confirm the account first. Where local law permits, we can share a copy of the data tied to your profile.

We keep records for as long as they are needed for the account, support, dispute handling or legal duties. After that, we delete or archive them according to the retention rules that apply to the record type.

Send the exact field you want changed and the updated value. We will check the request, confirm the account and make the change where local law permits, then let you know once it has been logged.

Only the teams and service partners that need it to run the account, answer support requests or meet legal duties can access it. We limit access by role and keep a record of the request path.

Yes. Access and any related service conditions depend on local law and are available where local law permits. If the rules change for your location, the policy that applies to your account can change too.