Reference

Open sensentoto Privacy Policy for Your Account

Your account details, phone verification and wallet records receive clear handling rules in the sensentoto Privacy Policy.

Account access recordsWallet status clarityPrivacy request routes
sensentoto Open sensentoto Privacy Policy for Your Account
CONTACT REQUEST PATHS

Ask About Privacy Through Account Support

A clear contact path helps when you want to check a record, correct a phone number or ask why a wallet status appears in your account history. We handle Privacy Policy questions through the account chat and support form, so your request can stay connected to the right account. Include the email or phone linked to your account, but never send a password or wallet PIN.

Team online

Account chat

Use the account chat for a quick Privacy Policy question about phone verification, device access or a session record. We may ask for a safe account identifier before discussing details.

Support form

The support form suits requests to access, correct or remove personal data. Describe the request clearly and attach only the payment receipt or account detail needed to locate it.

Receipt check

For DANA, OVO, GoPay, QRIS or bank transfer records, send the reference number through account support. We use it to check status without asking for your wallet password.

HOW WE HANDLE DATA

Explore sensentoto Data Controls and Security

We keep the Privacy Policy practical by linking each data use to an account step, from phone verification to wallet reconciliation.

Collection purpose

We collect account and contact details to create your login, complete phone verification and respond to support. Payment references help us match DANA, QRIS and bank transfer status to the correct account.

Cookie choices

Cookies can keep your session active, remember basic preferences and help us detect unusual access. You can manage cookie storage in your mobile or desktop browser, though some account steps may then require another login.

Account security

We use phone verification, session controls and access checks to reduce the chance of another person entering your account. Never share your password, wallet PIN or verification code through chat.

Payment records

A payment reference, amount status and receipt detail can remain attached to your account history so we can reconcile a deposit or withdrawal question. Wallet credentials are not requested for this check.

Retention approach

We keep personal data only for the account, security, support or legal purpose that requires it. When a record is no longer needed, we delete it or remove details that can identify you.

Change requests

Ask us to access, correct or delete eligible personal data through account chat or the support form. We verify the request against your account before making a change or explaining a restriction.

Browse Common Privacy Policy Questions

These Privacy Policy answers address the account questions you are most likely to have before opening access. We explain the records linked to local wallets, mobile sessions, cookies and support requests in plain English. If your situation is different, send the details through account chat or the support form and we will check the relevant record.

It covers personal data collected through your account, phone verification, mobile browser sessions, cookies, payment status and support contacts. It also explains our security controls, retention approach and ways to request a data change.

When you use DANA or QRIS, we may receive a transaction reference and status needed to match the payment with your account. The Privacy Policy explains this handling; we do not ask for your wallet password.

No. Our payment checks use transaction status, reference details and receipt data supplied through the payment flow. Your OVO or GoPay password and wallet PIN should never be sent to account chat or support.

Send an access request through the support form or account chat using the phone or email linked to your account. We verify your identity first, then explain which records can be supplied under local requirements.

Yes. Contact account support with the incorrect detail and the replacement detail you want recorded. We may repeat phone verification before changing access data, helping keep another person from taking over the account.

Cookies can preserve a session and basic preferences when you move from login to a lobby such as Aviator or Mega Fishing. Browser controls let you clear them, but clearing cookies may require another account login.

We retain records for the account, security, support or legal purpose that needs them, rather than keeping them without a reason. When that purpose ends, we delete or anonymise the relevant data where possible.