Reference

388hero Privacy Policy for Your Account

388hero Privacy Policy explains what we collect when you open an account, sign in on mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataCookie choicesWallet recordsRequest support
388hero 388hero Privacy Policy for Your Account
REQUEST ROUTES

Browse Contact Paths for Privacy Requests

A privacy question should not require guesswork. We keep the request route close to your account area, so you can identify the account concerned and describe…

Account support link Open the support link after signing in and state whether your request concerns account…
Sign-in assistance If you cannot reach your account, use the sign-in help route and provide only…
Payment record check For an OVO, GoPay or QRIS record, include the visible reference and date rather…
DATA PRACTICES

Switch Privacy Choices From Your Account

The Privacy Policy is practical because it connects each data choice to an account action. We separate sign-in protection from wallet references, explain browser cookies, and give you a route to request…

Data we receive

We may receive account details you enter, verification information, device and browser signals, and records showing whether a sign-in or wallet action completed. The Privacy Policy explains why each category is used.

Cookie controls

Cookies can keep your session active and remember selected settings. You can manage browser permissions on your mobile or desktop device, though blocking necessary cookies may interrupt account access.

Account protection

We use sign-in checks and account details to help identify unusual access. If you receive an unexpected verification prompt, contact support through the account path and do not disclose your password.

Retention rules

We keep records for account administration, security review, dispute handling and legal duties only as needed for those purposes. The Privacy Policy explains how retention can differ by record type.

Correction requests

If your contact detail is wrong, ask us to correct it through support with the account identifier requested. We may verify the request before changing information connected to your account.

Removal requests

You can ask whether removal is available for a particular record. Some details may need to remain for security, dispute or legal reasons, and we explain the outcome through the same request path.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers cover the account, device and wallet questions we expect before you create an account. If your situation is not listed, use the support route described above and tell us which part of your data you want us to address.

The 388hero Privacy Policy covers account details, verification records, device and browser signals, cookies, wallet references and requests to access, correct or remove data where local law permits.

Yes. The Privacy Policy explains that we may retain DANA and QRIS references and status details to match a payment event with your account. We do not need your wallet PIN or password.

You can send a data access request through the support link connected to your account. We may verify your identity first, then explain which records can be supplied under local rules.

Use the account support path and identify the detail that needs correction, such as a contact record. We may request an account check before changing information attached to your sign-in.

On a mobile browser, cookies can keep your session active and remember settings. Your browser controls them, but blocking necessary cookies may interrupt sign-in or return you to the account entry step.

We retain each record for account administration, security checks, dispute handling or legal duties only as needed. The Privacy Policy explains that the period can differ between account and payment references.

Start with the support link inside your account. If sign-in is unavailable, use the sign-in assistance route and provide only the requested identifying details, never a password or wallet credential.