Reference

Privacy Policy for hitamtoto Accounts

hitamtoto Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby on mobile or desktop.

Account dataWallet recordsDevice controlsPolicy contact
hitamtoto Privacy Policy for hitamtoto Accounts
CONTACT YOUR WAY

Where To Ask About Privacy

A clear contact path matters when a phone number, wallet reference or device record needs attention.

Account help route Use the privacy contact form beside your account settings when you want to ask…
Wallet receipt question If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction date…
Access concern When an unfamiliar device reaches your account, contact us from the account help area…
DATA HANDLING

What We Do With Your Details

We keep privacy work tied to real account actions rather than collecting details without a purpose.

Account records

We use registration details and phone verification to identify your account during login and privacy requests.

Device signals

A mobile browser and a desktop browser can create different login and session signals.

Cookies and sessions

Cookies can keep your session active, remember selected settings and help the account path work between login and the lobby.

Payment references

We retain the payment rail, reference and status needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account…

Retention choices

Some records can be removed or corrected after we confirm your identity.

Request verification

For a data copy, correction or access question, we may confirm your phone number, email or recent account action.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often from people preparing an account or checking a wallet record. They cover the data behind login, phone verification, device access, cookies, payment references and policy requests. If your question concerns eligibility, access depends on local law, and the account help route remains the right place to ask for a case-specific response.

It covers account details, phone verification, login and device signals, cookies, payment references and messages sent through account help. We use those categories to protect access, match DANA, OVO, GoPay or QRIS activity, answer requests and meet applicable retention duties.

Phone verification helps us confirm that the person asking about an account is connected with that account. It can be needed before we discuss private records, change account details or respond to a request about a wallet reference.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use the minimum reference needed to match a receipt or investigate a status question.

Open your account help area and select the privacy request route. Tell us whether you want access, correction or another data action, then provide the profile identifier used for registration. We may complete a phone or email check before replying.

Cookies can maintain a login session, remember selected settings and support the path from account access to the lobby. Your browser controls can restrict them, but that may cause an extra login or prevent some privacy request steps from working.

You can send a deletion request through account help. We first verify the account and then explain what can be removed. Certain records may need to remain for security, dispute handling or a legal duty, where local law permits that retention.

Contact us through the account help route and mention whether the access came from a mobile browser or desktop browser. Do not send your password. We may ask for phone verification, review the session details and explain the next account-security step.