Reference

alohatoto Privacy Policy: Know Your Data

Our Privacy Policy explains what alohatoto collects when you open an account, sign in from a phone, or check wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice detailsCookie choices
alohatoto alohatoto Privacy Policy: Know Your Data
CONTACT ROUTES

Ask About Your Account Data

A clear contact route helps when a Privacy Policy question concerns your own account rather than a general page. Start from the support link shown after sign-in and include the account phone number, the relevant date and the wallet reference if your question involves DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a password or one-time code.

Team online

Account access

If your phone verification or sign-in stalls, use the account support path and describe the step you reached. We can check the access record and explain which data was used for that Privacy Policy request without asking for your password.

Wallet records

For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and approximate time through support. We use that reference to locate payment status while keeping your wallet PIN, password and one-time code out of the message.

Data requests

To ask for a copy, correction or deletion assessment, identify the account phone number and state the request clearly. We may ask for an account check before responding so that private records are not sent to the wrong person.

DATA PRACTICE

How We Handle Data And Cookies

Our data practice follows the account steps you take: opening access, confirming your phone, entering the lobby and checking a wallet record.

Account details

We use the phone number and account details you submit to create access, complete phone verification and connect your requests to the correct account. If a detail changes, contact us through the signed-in support route rather than sending credentials in plain text.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction can create a reference, amount and status record. We use those fields to reconcile the account step and investigate a mismatch; we do not need your wallet PIN.

Device signals

When you move from a mobile browser to desktop, we may record device and browser signals linked to a sign-in session. These signals help us spot unfamiliar access and protect the account; they are not a substitute for your phone verification.

Cookies and storage

Browser cookies and local storage can retain session settings, sign-in state and selected page preferences. Clearing them may sign you out or remove those choices, but it does not automatically erase account records held for support or transaction reconciliation.

Security checks

We may compare a new sign-in with recent account activity and request an additional account check when the pattern changes. Keep your password and verification code private, and contact support if a device or wallet action appears that you do not recognise.

Retention and changes

We keep records for as long as needed for account support, transaction reconciliation, security checks and applicable legal duties. You can request access, correction or deletion review through support; the result can depend on local law and the record involved.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account and wallet questions we expect you to ask before opening access. They explain the practical route for checking records, changing details and contacting us, including the device and payment references that help us locate the correct account. Access or eligibility depends on local law, so a request may receive a different response when a local requirement applies.

The alohatoto Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It applies when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account in connection with your account.

We collect the details needed to create and protect your account, including your phone number, verification result, sign-in information and relevant device signals. If you use a wallet or bank route, we may also keep a transaction reference and status for account support.

Use the support path available after signing in and ask for an account data copy. Include your account phone number and the records you mean, such as a QRIS status or device sign-in. We may complete an account check before sending private data.

You can ask support to correct inaccurate details or assess deletion of a record. Tell us which account field or transaction reference is involved. We review the request against security, support and legal retention needs, and the outcome depends on local law.

Cookies and browser storage can retain your session state and page choices when you use a mobile browser. Clearing them may sign you out or reset preferences. Account records, phone verification history and payment references are handled separately from those browser files.

Yes. The Privacy Policy covers the account and transaction references created when you use DANA, OVO, GoPay or QRIS, as well as bank transfer and virtual account routes. We use those records to check status and respond to a specific account request.

Contact us through the support link shown in your signed-in account and describe the privacy concern clearly. Include your account phone number, relevant date and record type, but never send a password, wallet PIN or one-time verification code.