Reference

Open the iso288 Privacy Policy

Clear data choices sit alongside your account path at iso288, so you can understand what happens before using DANA, OVO, GoPay or QRIS.

Account dataWallet detailsCookie choicesPhone checks

Explore Our Lobby Read FAQ

Check Privacy Scope Before Access

iso288 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy describes how we receive, use, store and protect details connected with your iso288 account. This can include your contact details, phone verification result, sign-in records, device and browser signals, support messages, payment status and account activity needed to process a request. DANA, OVO,

1
GoPay, QRIS, bank transfer and virtual account references may appear as transaction context, while wallet providers and banks handle their own records under their terms. We use these details to provide account access, check payment status, address security concerns and respond to privacy requests. Access or
2
eligibility depends on local law, and any local restriction takes priority over this policy. We may update this page when our data practices change, with the latest version available at this address.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Contact Us About Your Privacy

A clear contact path helps when a privacy question sits beside an account or wallet issue.

DATA PRACTICE

See How We Handle Account Data

Privacy work is tied to practical account events rather than vague promises. We separate profile details from payment references, review device signals when access protection requires it and keep a record of…

Account details

We may use your name, contact route and phone verification result to create, maintain and protect your account. We do not need your password in a support message.

Cookies and devices

Cookies and browser signals can help remember a session or identify unusual access. Your mobile browser may present different cookie controls from a desktop browser.

Account security

Phone verification is part of the access path, while sign-in records and device signals help us investigate an unfamiliar session. We may pause a privacy response until identity is confirmed.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us trace payment status. The relevant wallet or bank remains responsible for records held in its own systems.

Retention requests

We keep records only for the period needed for the stated account, security, support or legal purpose. You can ask us what remains connected with your profile and why.

Changes and access

To request a correction, copy or deletion where available, use the account support contact and describe the exact detail involved. We may ask for a matching account step first.

Browse Privacy Policy Questions

These answers address the searches we hear most often about the iso288 Privacy Policy. They cover account records, wallet references, cookies, mobile access and the steps needed to ask for a change. If your situation involves a local restriction, access or eligibility depends on local law, so contact us with the specific account context.

It covers details linked to your account, including contact data, phone verification, sign-in records, device signals, cookies, support messages and payment status references. It also explains how we use, retain, protect and respond to requests concerning those details.

It covers the payment references we receive when you use DANA or QRIS, such as a status or receipt reference needed for account support. DANA and QRIS may hold separate records under their own terms, which this policy does not replace.

Use the support contact shown in your account area and ask for a privacy access request. Include the phone or email linked to your profile, but never send your password or full wallet credentials. We may confirm ownership before responding.

Yes. Send a correction request through the account support path and identify the exact field that needs changing. We may check your phone verification or another account step before editing the record, so the request is attached to the correct profile.

Cookies and browser signals can support session continuity and security checks. On a mobile browser, your available controls may differ from desktop settings. Review the cookie choices shown on your device and contact us if a privacy control is unclear.

Retention depends on the purpose, such as account support, security, payment tracing or a legal requirement. Our Privacy Policy explains the reasons for keeping records. You can ask what remains linked to your account and request deletion where available.

Start with the support contact displayed inside your account and describe the privacy issue in plain English. For a wallet concern, add the relevant DANA, OVO, GoPay or QRIS receipt reference, while leaving out passwords and full payment credentials.

Open the iso288 Privacy Policy

Contact Us About Your Privacy

See How We Handle Account Data

Account details

Cookies and devices

Account security

Payment separation

Retention requests

Changes and access

Browse Privacy Policy Questions

01 What does the iso288 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 How can I request a copy of my account data?

04 Can I ask iso288 to correct my personal details?

05 How does the Privacy Policy handle cookies on mobile?

06 How long does iso288 keep account details?

07 Where can I ask a question about the Privacy Policy?

Related Pages