Reference

aman788 Privacy Policy For Your Account

The aman788 Privacy Policy explains what account, device and wallet details we use when you open the lobby, why we need them, and how you can ask about…

Clear data purposesPhone verification contextWallet record handlingRequest path included
aman788 aman788 Privacy Policy For Your Account
CONTACT ROUTES

Where To Ask About Privacy

A direct account route helps when you need an answer about your Privacy Policy rights or a wallet record.

Account privacy request Use the support route inside your account to ask for a copy, correction or…
Wallet record question For DANA, OVO, GoPay or QRIS status questions, include the transaction reference and date…
Access concern If phone verification or sign-in blocks your request, tell us which account step stopped.
DATA PRACTICES

Six Ways We Handle Your Data

Privacy work is part of the account path, not a separate promise. We limit collection to details needed for account operation, security, payment matching and support.

Purpose before use

We use your phone number to create and protect account access, and we use verification responses to confirm the person making a sign-in or privacy request.

Cookies and sessions

Cookies and session signals help keep a mobile or desktop sign-in connected to the right account. You can manage browser cookie settings, though some account steps may then need repeating.

Payment references

Our records can contain DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We use them to match status and receipts, not to request your wallet password.

Account protection

Phone verification before account access helps us distinguish your account from an unfamiliar sign-in. Do not share verification codes, passwords or wallet credentials through a support request.

Retention choices

We retain account and transaction records for the period needed for security, support, dispute handling and legal duties. When a record is no longer needed, our process removes or anonymises it.

Changes and requests

You can ask us to correct account details, explain a data use, provide available records or address a deletion request. We may confirm your identity before changing or disclosing anything.

Privacy Policy Questions Answered

These questions focus on the searches we hear most often about the aman788 Privacy Policy. The answers explain the account step, device records, payment references and contact route in plain terms, while access and eligibility depends on local law. If your situation is different, use the privacy contact path with enough detail for us to locate the right record.

It covers account details, phone verification, sign-in and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification before account access to connect the sign-in with the correct account and reduce mistaken or unauthorised access. We do not ask for your wallet password in that step.

No. Our records may show a payment reference, amount status or receipt detail needed for account matching, but your DANA, OVO, GoPay and QRIS credentials remain outside that record.

Yes. Send a request through the support link in your account area and identify the phone number on the profile. We may ask for identity confirmation before releasing account-linked records.

Use the account support route and state which detail is wrong, what the corrected value should be and why. We check the request against your account before making an amendment.

We keep records for the time needed for account security, receipt and status checks, dispute handling and legal duties. Once a record is no longer needed, we remove or anonymise it.

Access and eligibility depends on local law. Check the current Privacy Policy and account access wording for your location, and contact us if you need clarification before opening or using an account.