Reference

Privacy Policy for your testogel account

Our Privacy Policy explains what testogel collects when you create an account, sign in from a phone, browse Live Roulette or use DANA and QRIS.

Account dataWallet recordsDevice accessPolicy requests
testogel Privacy Policy for your testogel account
HELP WITH PRIVACY

Where to ask about stored details

A clear contact route helps when you want to understand a Privacy Policy entry or question a record connected with your account. Send your request through the account support path and include the phone number or sign-in detail linked to your profile, without sending a password. We can then locate the relevant account event, wallet reference or device session. If your question concerns DANA, OVO, GoPay or QRIS, include the receipt reference so we can separate our records from the payment provider’s records.

Team online

Account privacy request

Use the support route connected to your account when you want a copy, correction or explanation of personal details. We may ask you to complete phone verification before discussing account-specific records.

Wallet record question

For a DANA, OVO, GoPay or QRIS query, send the transaction reference and approximate time. We use those details to trace the record without asking you to share a wallet password or full security code.

Access concern

If a new phone or browser appears in your account history, tell us through support and include the device path you used. We can explain the related sign-in record and direct you to the account access step.

DATA HANDLING

What we do with account information

We keep the Privacy Policy practical by linking each data use to an account task: access, verification, wallet reconciliation, security checks or customer support.

Account creation

When you open an account, we use the details you submit to create your profile and complete phone verification before account access. The Privacy Policy explains which fields support that step and which records remain after a request.

Device and browser signals

Signing in from a mobile browser can create records such as session time, browser type and security signals. We use these details to recognise unusual access, including a change from one phone to another.

Cookies and sessions

Cookies and similar session tools help keep your account path active while you move from login to the lobby. Our Privacy Policy explains their purpose, and you can control many browser cookie settings on your device.

Wallet reconciliation

DANA, OVO, GoPay, QRIS and bank transfer activity can produce references, amounts and status events on our side. We retain enough transaction context to match a receipt, investigate a stalled status and answer your account question.

Account protection

We use sign-in history, phone verification and session signals to help protect your profile. Never send us a password or one-time security code; if access looks unfamiliar, contact support from the account path you can still reach.

Changes and retention

You can ask us to correct details, explain a data use or clarify retention through the privacy contact route. We assess the request against account needs and local requirements, then explain any record we must keep and why.

Privacy Policy answers for Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. We keep the wording tied to actual steps, from phone verification on a mobile browser to receipts from DANA, OVO, GoPay and QRIS. If your situation is not covered, contact us with the smallest useful detail and we will route the request.

The testogel Privacy Policy covers account details, phone verification, sign-in and device records, lobby activity needed for service operation, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use phone details to create and verify your account before access. Device and browser signals help us recognise a session, investigate unfamiliar sign-ins and explain an access event without asking you to reveal a password.

Yes. The Privacy Policy includes transaction references and status information generated when you use QRIS, DANA, OVO or GoPay. The payment provider may also have its own terms, so its handling is separate from our account records.

Use the account support path and ask for a data copy or correction. Include the phone number linked to your profile and describe the record you mean. We may request phone verification before discussing account-specific information.

Retention depends on why the record exists, such as account access, wallet reconciliation, security checks or a support request, and on applicable local requirements. Contact us for the retention context of a particular account or transaction record.

Yes. Tell support the approximate time and device path, such as a mobile browser or desktop session. We can explain the related sign-in record and help you follow the account access step if the activity was not yours.

The service and your eligibility depend on local law. Where local law permits, you can read this Privacy Policy, open an account and submit a request about your stored details through the available support path.