Data used across OCBET account routes
Privacy context covers data used for login, registration, device security, payment checks, support messages, cookies and fraud prevention. The user should know which details are needed and which details should never be shared in chat.
Related OCBET routes
Data, cookies and support
Privacy explains how account, communication, payment, cookie, security and support data can be handled. Users should understand what information may be used for login, verification, fraud prevention and case support.
When a query involves payment or identity, support may ask for references or screenshots, but not a full password. The policy also connects with terms and responsible gaming.
Data in the user journey
- Read what data is used during registration.
- Review cookies and analytics.
- Understand what is shared with support.
- Use contact for privacy requests.
Information types
| Data | Use | Care |
|---|---|---|
| Account | Login and support | Keep correct |
| Payment | Reconciliation | Save proof |
| Cookies | Experience and measurement | Manage browser |
Privacy and data questions
Does support ask for password?
No.
Why save payment proof?
To verify operations.
Where to ask data questions?
Contact and privacy.
Safe data-sharing examples
It is reasonable to share an account email, approximate time, payment method and transaction status with support. It is not safe to send a full password, card security code, OTP or private wallet seed phrase.
How privacy applies to login, app and cashier
Login uses credentials and device signals, the app uses browser or install data, cashier actions use payment and verification details, and support may request status screenshots without requiring passwords or security codes.
Enter OCBET Mexico
Use the internal route first, review bonus, balance and payment status, then continue only from the verified ocbetmx.org access path.