Reference

tomathoki Privacy Policy For Your Account

Our Privacy Policy explains what tomathoki collects when you open an account, check the Live Dealer Lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet details explainedAccount requests coveredCookie choices included
tomathoki tomathoki Privacy Policy For Your Account
DATA HELP ROUTE

Privacy Questions Start With Your Account

A clear support route helps you resolve a Privacy Policy question without sending sensitive wallet credentials. Sign in first when possible, then use the account help path to identify the relevant profile or payment reference. If you are in Semarang or elsewhere in Indonesia, include the device and account step where the issue appeared so we can narrow the request.

Team online

Account access

Tell us which phone verification step or sign-in screen you reached. We use the account reference you provide to locate the relevant record without asking for your DANA, OVO or GoPay password.

Wallet status

For QRIS, bank transfer or virtual account questions, attach the payment receipt reference rather than private wallet credentials. We compare the reference with the account record and explain the status check.

Data request

Ask us to view, correct or remove eligible personal details through the account help path. We may confirm ownership before changing records, especially when the request concerns phone verification or payment history.

HANDLING YOUR DATA

Six Privacy Checks Behind Your Account

We keep our Privacy Policy practical by tying each data use to an account action. Phone verification helps confirm who is signing in; device signals help us spot unusual access; and payment…

Collection

We receive details you enter during account creation, such as your contact details and verification response. We also record service events created when you sign in, change account settings or contact support.

Cookies

Cookies and similar browser storage can remember session state, language choices and security checks. You can manage browser permissions, but restricting essential storage may interrupt sign-in or return you to phone verification.

Device signals

Browser type, operating system, IP address and event timing help us investigate unusual account access. These signals are used for security and troubleshooting, not as a substitute for the account details you provide.

Account security

We use phone verification and sign-in event checks before allowing account activity. Never send a wallet PIN or password in a support message; a payment reference is enough for a receipt or status check.

Retention

We keep personal data only for the period connected to its purpose, account needs and applicable legal duties. Payment references may remain longer than a browser session when reconciliation or a lawful record requires them.

Your request

You may ask what data we hold, request a correction, ask about use, or seek deletion where applicable. We confirm account ownership first and explain if a lawful record must remain retained.

Privacy Policy Answers For tomathoki

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. Each answer reflects the way we handle phone verification, browser signals, payment references and requests from Indonesia, while access remains subject to local law.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to confirm account ownership before access and to protect account changes. We do not ask you to send a wallet PIN or password when checking a support request.

Yes. The policy covers transaction references, status results and receipt details linked to DANA and QRIS. We use these records to reconcile activity, while your private wallet credentials remain with the wallet provider.

We may record browser type, operating system, IP address and security event timing when you sign in or request help. These details help investigate unusual access and diagnose an account issue.

Use the account help path and state whether you want access, correction, an explanation of use or eligible removal. Include your account reference, and we may verify ownership before responding.

Retention depends on the purpose, account needs and applicable legal duties. Session data may expire sooner, while payment references can remain when reconciliation, security review or a lawful record requires them.

Access and eligibility depend on local law. If you can access your account, use the policy request path for privacy questions; do not send sensitive wallet credentials through support messages.