Reference

api 288 Privacy Policy For Your Account

api 288 Privacy Policy explains how we handle the details you provide when you open an account, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesSecurity requests

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

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

Our Privacy Policy covers details linked to your account, such as your name, phone number, verification result, login activity and selected wallet rail. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain transaction references so we can match a

1
receipt with the correct account. Device type, browser settings and security events may also be recorded to protect access. We use these records to provide account services, answer requests and investigate unusual activity. Access to the service depends on local law, and this policy applies where
2
local law permits.

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

CONTACT ROUTES

Ask About Privacy Through Support

A direct support route helps you resolve a privacy question without guessing which team to contact. We can help you identify an account record, explain a wallet reference or direct a request about cookies and access. Use the support channel shown on our site between 09:00 and 23:00 WIB each day. Keep your registered phone number ready, but never send a password, one-time code or full wallet credential. We will ask for account details only when they are needed to locate your request.

Team online

Account privacy

Ask us to explain the account fields connected with your registered phone number. We can clarify why a verification step appears before access and route a correction request to the team handling account records. Send your request through the on-site support channel during 09:00-23:00 WIB.

Wallet records

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact support with the transaction date and reference ending. We use that limited detail to locate the record without asking you to share a password or one-time code. Bank transfer questions follow the same account-based check.

Access concerns

A login or device concern can be raised through the same support route. Tell us whether you used a phone or desktop browser, the approximate time, and the message shown. We can then review the access event and explain the next account-security step without requesting private credentials.

DATA PRACTICES

How We Handle Your Privacy Choices

We keep this Privacy Policy practical: you should know what enters our records, why it is used and how to ask for a change.

Data collection

We collect account details you submit, verification outcomes, login timestamps, device signals and support messages. Payment records may include a rail name, reference and status rather than your wallet password. This lets us connect a receipt to your account while keeping sensitive access credentials out of support conversations.

Cookie settings

Cookies can remember a selected setting, maintain a session and help us understand which policy pages receive attention. Your browser controls whether cookies are accepted. If you clear them, you may need to sign in again or repeat a display preference on the next device visit.

Account security

Before account access, phone verification can confirm that the request belongs to the registered contact. We also compare sign-in timing, browser details and device signals when a session appears unusual. Never share a password or one-time code with support, even when asking about a privacy matter.

Retention period

We keep account, support and transaction references only while they serve account operation, security checks, dispute handling or a legal requirement. When a record is no longer needed, our process can remove it, restrict it or separate it from direct account identifiers.

Change request

You can ask us to correct an inaccurate phone number, name or account detail through the site support channel. Include the registered contact and a short description of the error. We may verify ownership before making a change, so another person cannot alter your account record.

Policy contact

Questions about this Privacy Policy can be sent through support between 09:00 and 23:00 WIB. Mention the section or record concerned, such as a QRIS receipt, cookie setting or device sign-in. We will explain the available route and any ownership check before responding.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an account or checking a wallet record. We keep the wording tied to api 288 account activity, device access and local payment references, rather than describing unrelated lobby features. Where a request needs account verification, we explain the reason before taking action. Service access depends on local law and is available where local law permits.

The api 288 Privacy Policy covers account details, phone verification, login and device signals, cookie settings, support messages and transaction references. It explains why we use those records, how long we retain them, and how you can ask about correction, access or removal through support.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We may retain the rail, amount status and reference needed to match a receipt with your account, but support does not need your wallet password or one-time code.

Phone verification helps us check that an account-access request belongs to the registered contact. We may also compare the device and browser used for the sign-in. If a check is triggered, support can explain the next step after confirming enough account detail to protect your records.

You can request a correction through the on-site support channel from 09:00 to 23:00 WIB. State which detail is wrong, such as a phone number or name, and provide the registered contact. We may confirm account ownership before changing the record.

Cookies may keep a session active, remember a setting or show us which policy pages are used. Your browser provides controls for accepting or clearing them. Clearing cookies can sign you out and remove saved preferences, but it does not automatically erase account or transaction records.

We retain account, security, support and payment references while they are needed for account operation, security checks, disputes or legal duties. We then review whether each record remains necessary. You can contact support to ask what type of record is held and which action is available.

Use the support channel displayed on our site between 09:00 and 23:00 WIB and mention Privacy Policy in your request. Include the relevant topic, such as a cookie, device sign-in or QRIS receipt. Do not include your password, one-time code or full wallet credentials.

api 288 Privacy Policy For Your Account

Ask About Privacy Through Support

Account privacy

Wallet records

Access concerns

How We Handle Your Privacy Choices

Data collection

Cookie settings

Account security

Retention period

Change request

Policy contact

Privacy Policy Answers For Indonesia

01 What does the api 288 Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS records?

03 Why does api 288 need phone verification?

04 Can I ask api 288 to correct my account data?

05 How does the Privacy Policy handle cookies?

06 How long does api 288 keep my personal data?

07 How do I contact api 288 about this Privacy Policy?

Related Pages