Reference

Privacy Policy For Your dht22 Account

The dht22 Privacy Policy explains what we collect when you open an account, sign in, use the lobby and choose a local payment route.

Account accessWallet recordsCookie choicesContact route
dht22 Privacy Policy For Your dht22 Account
CONTACT YOUR WAY

Get Privacy Help Near Account Support

A clear contact route matters when your Privacy Policy question concerns an account record, device session or wallet status.

Account message Send your Privacy Policy request through the account support path and include the email…
Payment record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the payment…
Security concern If a sign-in or device session looks unfamiliar, contact account support promptly and change…
CONTROL AND CLARITY

What We Do With Your Personal Data

Privacy Policy controls are part of the account process, not a separate payment screen.

Data handling

We use personal data for account access, verification, support routing, payment reconciliation and security review.

Cookies

Session cookies can keep your signed-in path working between the lobby and account screens.

Account security

Password, phone verification and device signals help protect the account from an unfamiliar sign-in.

Retention

We retain information for the period needed to provide access, resolve a payment receipt question, review security events or meet…

Correction requests

If your name, phone number or account detail is inaccurate, tell support which field needs attention and provide the account…

Policy contact

Questions about this Privacy Policy can be sent through the account support route.

Privacy Policy Answers For dht22

These Privacy Policy answers cover the points you are most likely to need before opening or using a dht22 account. They explain the information connected with login, local payment activity, cookies, device checks and personal requests. If your situation is unusual, use the support route with an account identifier and a short description of the issue. Do not include passwords, PINs or one-time codes. Where access or eligibility is relevant, it depends on local law.

The dht22 Privacy Policy covers information connected with account creation, phone verification, sign-in, device use, support messages, cookies and payment status. It also explains how we handle access, correction, deletion and other personal-data requests where local law permits.

We may handle your name, phone number, account identifier, verification details, device and browser information, IP address, session records and support messages. Payment activity can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and status.

A payment reference lets us match an account-side receipt or status with the correct request without receiving your wallet password or PIN. The Privacy Policy covers that reconciliation record, while the payment provider handles its own payment credentials and separate data practices.

Cookies can preserve a session between sign-in, the lobby and account screens, and some technical storage helps diagnose browser issues. You can remove or restrict cookies in your browser. Required session storage changes may sign you out or interrupt a requested account action.

Yes. Send an access or correction request through account support with the phone or account identifier connected to dht22. State which information you need reviewed. We may verify your identity before responding, and the available outcome depends on local law and retention duties.

Use the support route and ask for a deletion assessment, naming the account identifier and request type. We review whether the information is still needed for security, payment disputes, service records or legal duties. We explain any limit before taking the next step.

Change your password through the normal account path, avoid sending security codes to anyone and contact support with the approximate sign-in time and device details. We use account security records to route the concern and may require verification before discussing personal information.