Reference

Privacy Policy for Your Wallet Details

ace138 slot Privacy Policy explains how we handle the account details connected with DANA, OVO, GoPay and QRIS, including information used when you complete phone verification before account…

Clear data purposesWallet detail controlsPhone verification contextIndonesia access wording
ace138 slot Privacy Policy for Your Wallet Details
PRIVACY HELP ROUTES

Contact Paths for Privacy Questions

A clear contact route helps you resolve a privacy question without sending sensitive details through the wrong place.

Account help path When you are signed in, use account help to ask about stored details, cookie choices or a correction. We may confirm your phone verification first, which keeps a privacy request connected to the right account without exposing records to another person.
Privacy contact route For access questions from a mobile browser, follow the contact link on this Privacy Policy page. Tell us whether your request concerns account data, device records or deletion, and we will use the details you provide to locate the correct case.
Wallet reference check If a privacy question involves DANA, OVO, GoPay or QRIS, share the transaction reference only through the account help path. We use that reference to check the related record and do not need your wallet password or security code.
DATA CONTROL POINTS

Data Controls Behind Your Account

Our privacy process follows the same account steps you already recognise: sign in, complete phone verification when requested and use the account help path for a data question.

Account details

We use the details you enter to create and maintain your account, confirm requested changes and respond to privacy contacts. If a field is wrong, tell us the correction you need; we may request phone verification before changing it.

Cookie choices

Necessary cookies help keep your mobile browser session connected, while preference cookies can remember selected settings. You can adjust browser controls, and our privacy contact route can clarify which cookie category relates to a specific account function.

Security checks

Phone verification before account access helps us distinguish an account holder from an unfamiliar sign-in. Never send a password or complete wallet code to support. If access looks unusual, use the account help path before sharing any further personal detail.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained to match a receipt or investigate a status question. These references are handled as transaction context, not as permission to request unrelated wallet credentials.

Retention questions

We keep personal records for the time needed for account operation, security checks, support history or legal needs. You can ask why a record remains and request removal where applicable; access depends on local law and the record involved.

Change requests

To request access, correction or removal, contact us through the privacy page or signed-in account help. Describe the request clearly, identify the relevant account step and provide only safe verification details so we can assess it accurately.

Privacy Policy Questions From Indonesia

These answers address the privacy questions you may have before opening an account or returning through a mobile browser. We explain how the ace138 slot Privacy Policy relates to phone verification, cookies, wallet references, account access and requests for changes. If your situation needs a record-specific answer, use the privacy contact route and share only the minimum details needed for us to identify your request.

It covers account details, phone verification, device and browser signals, cookies, support records and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to request access, correction or removal where local law permits.

Yes. The Privacy Policy explains that wallet and bank references help us match a receipt, check a status question and protect account records. We do not need your wallet password or complete security code for a privacy request.

Use the privacy contact route or signed-in account help and ask for an access request. State which account details or device records you want checked. We may confirm phone verification before sharing records, and access depends on local law.

You can request a correction through account help or the privacy page contact route. Identify the incorrect field and the replacement detail, then complete any needed verification. We assess the request against account security needs and applicable local law.

Necessary cookies support sign-in continuity, while preference cookies can store selected settings. Your browser controls can adjust optional cookies. If changing them affects account access, contact us through the Privacy Policy route so we can explain the relevant function.

We retain records while they serve account operation, security, support or legal needs. When those needs end, records may be removed or anonymised. You can ask why a particular record remains, although the answer depends on local law and its purpose.

Start with the contact link on this Privacy Policy page, or use signed-in account help when available. Explain whether the concern involves account access, cookies, a DANA or QRIS reference, or a change request, and avoid sending passwords.