Reference

Your data terms at betnaija

Live Baccarat, Spribe Aviator, Buffalo Blitz and UPI wallet flows create account records, and this Privacy Policy explains how we collect, use and protect those records when you…

Account data useCookie choicesUPI record careIndia privacy support
betnaija Your data terms at betnaija
CONTACT ROUTES

How to reach privacy support

Privacy questions should reach the team that can read account records, check identity and reply with care.

Email privacy desk Write to our privacy desk from your registered email if you want access to your data, a correction, deletion where allowed, or a copy of key account records tied to your profile.
Live chat handoff Start with chat if you need help finding the right privacy route. Our chat team can verify your account safely, then send the case to the data team without asking for secret payment codes.
Account message centre Use the message centre for privacy requests linked to deposits, withdrawals, cookies or login sessions. Keeping the request inside your account helps us match the record and respond with fewer repeat checks.
CARE STEPS

How we protect account data

Your privacy depends on daily controls, not just a written policy. We separate payment references from game session records where practical, restrict internal access by role, and use security checks for logins…

Data collection

We collect account details, verification records, payment references, device data and session activity only for clear account purposes. This helps us run the wallet, confirm requests and keep privacy decisions tied to the right profile.

Cookie control

Cookies support login status, fraud checks, language choice and basic site measurement. You can manage browser cookies, but some account features may not work correctly if required security cookies are blocked.

Payment privacy

UPI, Paytm, PhonePe and Google Pay references are used to match wallet activity and resolve payment disputes. We do not ask for your UPI PIN, and privacy support should never request it.

Access checks

Before sharing, correcting or deleting account data, we verify that the request comes from you. This may include email confirmation, account checks or limited payment reference matching for safety.

Retention rules

Some records must stay for legal, tax, security or dispute reasons even after an account change. When those reasons end, we delete, anonymise or separate the data from direct account identity.

Policy updates

When we change this Privacy Policy, we update the page date and may send a message if the change affects how your data is collected, used, shared or retained.

Privacy Policy questions before joining

Read these answers before you open an account or send a privacy request. They explain what data we collect, why payment references matter, how cookie choices work and how you can ask for changes. If your question involves local eligibility, access depends on local law and is available where local law permits.

It covers account details, verification records, payment references, device data, cookies, login activity, support messages and wallet records. We use this data to run your account, process requests, secure access and meet legal duties.

We use payment references to match deposits and withdrawals with your wallet, investigate failed transactions and reduce misuse. We do not need your UPI PIN, and you should not share secret payment codes with support.

Yes. Send the request from your registered email or account message centre. We may verify identity first, then share the account data we can provide under applicable law and retention duties.

You can ask us to correct account data that is inaccurate or incomplete. Some fields may need verification documents before we change them, especially if they affect payments, identity checks or account access.

Retention depends on the record type and the reason it was collected. Account, payment, tax, dispute and security records may stay for required periods, then be deleted, anonymised or separated from identity.

Cookies help keep you logged in, remember basic preferences and detect risky access. You can manage cookies in your browser, but blocking required security cookies may affect account access or payment checks.

Privacy requests go to trained support and data staff who need access to handle the case. We limit internal access, verify identity before action and avoid asking for secret payment credentials.