Reference

Open the ion55 Privacy Policy

ion55 explains how we collect, use and protect details connected with your account, wallet activity and policy requests.

Account clarityWallet recordsCookie choicesSecurity steps
ion55 Open the ion55 Privacy Policy
REQUEST A RESPONSE

Use the account path for privacy help

A clear request helps us locate the right account record without asking you to send unnecessary details. Start from your signed-in account area when possible, or use the support route linked beside account and cashier help. Tell us whether you need access, correction, deletion, cookie clarification or a payment-record explanation. We may ask for an account identifier and a verification step before discussing personal data.

Team online

Account request

For an access or correction request, include the account phone number and the exact change you need. We use the account path first so we can check identity before showing details linked with your login.

Wallet record

If your question concerns DANA, OVO, GoPay or QRIS, provide the payment reference and date rather than a wallet password or full security code. We check the receipt trail and reply with the smallest useful detail.

Policy contact

For a Privacy Policy question, quote the relevant section and explain your requested outcome. We may request identity confirmation, especially where a change could affect account security or another person’s information.

DATA CONTROL ROOM

Explore the controls behind your privacy

We separate ordinary account operation from requests that require a higher level of confirmation. Your phone verification supports account access, while session and device signals help us detect suspicious sign-ins.

Collected details

We may receive your account phone number, verification result, device and browser signals, support messages, payment references and activity needed to operate the account. We aim to collect what serves a stated account, security, payment or legal purpose.

Cookie handling

Cookies can keep a session active, remember language or display settings and help us diagnose a page issue. Browser controls may restrict them, although some account functions can behave differently when required cookies are blocked.

Account security

Phone verification comes before account access, and security events may be recorded when a sign-in or device pattern needs checking. Never place a password, one-time code or wallet credential inside a support message.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a transaction status without needing the secret credentials used inside your financial app. We use payment data for reconciliation, support and required records.

Retention timing

We keep information only for the operational, security, dispute or legal period connected with its purpose. A payment record may remain longer than a routine support message where accounting, fraud checks or local rules require it.

Change request

You can ask us to access, correct or remove eligible personal details through the account support path. We verify the requester, explain any restriction and tell you when a record must remain for security, payment or legal reasons.

Find answers about Privacy Policy

These Privacy Policy answers focus on the account actions Indonesian customers most often need to understand before sending details or using a wallet. The current policy remains the controlling text, and access depends on local law. If your situation is unusual, send a focused request through the account support route so we can check the relevant record.

It covers account details, phone verification, device and cookie data, support messages, payment references and security events. It also explains why we use those records, how long they may remain, when disclosure is restricted and how you can request access or correction.

We use the phone number to create and identify your account and to complete the verification step before access. It can also help support locate the correct record. We will not ask you to place a password or one-time code in a support message.

Yes. The policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use these details to match receipts, resolve status questions and keep required transaction records.

Use the signed-in account support path when you can, state that you are making a personal-data request and identify the records involved. We verify your identity before sharing details, then explain the scope, timing and any lawful reason a portion cannot be supplied.

You may request correction or removal of eligible information through support. Tell us exactly what is wrong or what you want removed. Some payment, security or dispute records may need to remain, and we will explain that restriction where local law permits.

On a phone browser, cookies may support your session, remember settings and help us diagnose loading problems. You can use browser controls to restrict them, but blocking required cookies may affect login or account pages. The same policy applies on desktop access.

Yes. Account access and eligibility depends on local law. Before submitting personal details, check that access is permitted in your location. We may limit an account or a request where legal, security or identity requirements prevent us from completing the requested action.