Reference

Privacy Policy for Your usaha66 Account

usaha66 Privacy Policy shows what we collect, why we use it and how you can ask for changes before opening an account.

Clear data purposesWallet records explainedAccount request pathIndonesia access wording
usaha66 Privacy Policy for Your usaha66 Account
CONTACT ROUTES

Where To Ask About Your Data

A clear contact route matters when a name, phone number or wallet reference needs attention. From your account help path, send a request about the usaha66 Privacy Policy and include the registered phone number plus the specific record you want checked. We may ask for an account step or payment reference to confirm that the request concerns you, not another account. Keep receipts and status details ready when the question involves DANA, QRIS or a bank transfer.

Team online

Account help route

Use the account help path for Privacy Policy questions about your registered phone number, sign-in record or verification step. We use the account details you provide to locate the correct record and may request a matching account action before discussing private data.

Wallet status request

For a DANA, OVO, GoPay or QRIS reference, include the payment date and status shown to you. Our support route can compare that reference with the account record without asking you to send a wallet password or private security code.

Policy change request

Ask us to correct account details, explain a stored device signal or clarify retention through the same support path. State the requested change plainly; we will check identity first and tell you if a legal or security reason limits the action.

DATA PRACTICE

Six Controls Behind Our Data Handling

We keep the Privacy Policy practical by linking each data action to an account task. The controls below describe how we handle cookies, device behaviour, account security, retention and requests from you.

Account records

We use your phone number and account details to identify the correct account, complete the stated verification step and respond to a data request. We do not need a wallet password to check a DANA, OVO, GoPay or QRIS reference.

Device signals

A phone or browser may send device type, session time and security signals when you sign in. These details help us spot an unusual account path, such as a new device during a wallet status check, and support a safer response.

Cookie choices

Cookies can retain a session setting or help us understand which policy page was opened. Your browser controls whether cookies remain. Removing them may require you to repeat the phone verification or account sign-in step.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match an account action with its status. We separate that reference from sensitive wallet credentials and do not ask for private wallet codes.

Retention timing

We retain account, security and payment records for the period needed to provide the requested account service, resolve disputes or meet applicable duties. When a record is no longer needed for those purposes, our handling follows the policy.

Your requests

You can ask for a copy, correction or explanation of personal data through account help. We verify the request, identify any account or legal restriction, then explain the next step rather than exposing another person’s record.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers cover the account and wallet questions we expect before you open an account. They explain what to prepare, how to contact us and what can affect a request. If your question concerns local eligibility, access depends on local law and the wording below does not replace that requirement.

It covers account details, phone verification, device signals, cookies, payment references and activity records connected with your account. It also explains our purposes, retention approach, security checks and the route you can use to request access or correction.

We use your phone number to create and identify the account, complete the stated verification step and connect a support request to the correct record. If you ask about DANA, OVO, GoPay or QRIS activity, it helps us locate the related account entry.

Yes. It covers payment references and status details linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account references. We use these details to match an account action, not to request your wallet password or security code.

Open the account help route and request a copy under the usaha66 Privacy Policy. Include your registered phone number and describe the records you need, such as verification or wallet status. We first confirm the request belongs to you before responding.

You can request a correction through account help when your name, phone number or another account detail is inaccurate. Tell us what is wrong and what should replace it. We may request verification, and a legal or security duty may restrict changes.

The retention period depends on why the record exists. Account, security and payment entries may remain while we provide the requested service, handle a dispute or meet applicable duties. The Privacy Policy explains that records are handled according to those purposes.

The policy explains our data handling for Indonesia, while account availability and eligibility depends on local law. Whether you connect from Yogyakarta, Denpasar or another location, where local law permits, the same request and contact path applies.