Reference

otp77 Privacy Policy for Your Account

The otp77 Privacy Policy explains what we collect when you open an account, use the lobby, or check a DANA, OVO, GoPay or QRIS status.

Account recordsWallet statusCookie choicesSecurity checks
Explore Our Lobby Read FAQ
otp77 otp77 Privacy Policy for Your Account
CONTACT PATHS

Ask About Your Privacy Policy Data

A direct support request gives you a practical way to ask what data is linked to your account or why a verification step appeared. Start from the support route while signed in, describe the issue, and include the relevant payment reference rather than sending wallet credentials. We can then check the account record, device event or receipt status connected with your question. If access is unavailable, use the contact route shown on otp77 and provide the account contact detail you used. We handle requests according to the Privacy Policy and where local law permits.

Team online

Account data request

Ask us to identify the account details, sign-in records or verification information connected with your profile. We may request an account step or contact confirmation before discussing private data, so a different person cannot obtain your records.

Wallet record question

For a DANA, OVO, GoPay or QRIS concern, send the payment reference and approximate date shown in your receipt. We use that detail to locate the status record without asking you to disclose a wallet password or security code.

Correction or deletion

Tell us which detail needs correction or which account record you want considered for removal. We assess the request under the Privacy Policy, including any retention needed for security, payment reconciliation or a legal duty.

HANDLING DETAILS

How otp77 Handles Privacy Requests

We keep the Privacy Policy practical by separating account access records from wallet credentials and by limiting staff access to information needed for a support task.

Account information

We may hold the contact detail used for your account, verification results, support messages and activity needed to connect you with the right account. Keeping these records together helps us avoid exposing one account's details during a payment or login query.

Payment references

A deposit or withdrawal check can include a transaction reference, channel name and status result for DANA, OVO, GoPay, QRIS, bank transfer or virtual account. These details help us reconcile a receipt; they are not a request for your wallet PIN.

Cookies and browsers

Cookies can preserve a language or session preference and help us understand technical errors. You can manage browser cookie settings on your device, although removing them may require another sign-in or cause some account pages to load differently.

Device security

We may record device type, browser signals, IP-related technical data and sign-in time to identify unusual access. If a check interrupts your route from login to the lobby, contact support rather than sharing a password or verification code.

Retention choices

We do not keep every record forever by default. Retention depends on why the data was collected, including account security, payment reconciliation, dispute handling and legal requirements. A deletion request may therefore have limits that we explain in our reply.

Request handling

When you ask to access, correct or delete data, we first confirm that the request comes from the account holder. Give us a clear account contact and the record involved; we will assess it under the Privacy Policy and local requirements.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account and payment questions we expect you to ask before opening access. They explain what may be collected, how device and wallet records are used, and how to contact us about a correction or deletion request. For a case involving your own account, use the support path with the relevant reference so we can check the correct record.

The Privacy Policy covers contact details, account verification, sign-in events, device signals, support messages and activity records needed to operate and protect your account. We use the minimum context needed to answer access questions and do not ask for your wallet password.

We may store a payment reference, channel name, amount status and related timing so we can match a receipt or investigate a cashier question. The Privacy Policy does not mean we need your wallet PIN, password or security code.

Cookies may remember session or language settings and provide technical signals about page errors. You can manage them through your browser controls. Removing cookies can sign you out or make you repeat an account step when returning from mobile or desktop.

Yes, where local law permits. Contact us through the account support path, identify the account contact used at registration, and describe the records requested. We may confirm your identity first so private account information is not released to another person.

You can ask us to correct inaccurate account or contact information. Include the old detail, the replacement detail and a reason or supporting context where useful. We assess the request against account security, payment records and applicable local requirements.

Retention depends on the purpose of each record. Account security events, payment reconciliation, disputes and legal duties can require longer storage than a temporary cookie. If you ask us to delete information, we explain any record that must remain.

It describes how we handle information connected with access from Indonesia, but eligibility and access depend on local law. If you are in Semarang or another Indonesian location, check the applicable rules and contact support when a policy question affects your account.

Related Pages

otp77 Indonesia Access guide Account information About Us LinkAja Deposit Guide