Reference

55wealth Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a 55wealth account, sign in from a mobile browser, use DANA or QRIS, and contact account support.

Account dataWallet recordsCookie choicesContact routes
55wealth 55wealth Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you resolve a privacy question without exposing more account data than needed. Start from the account help route when your request concerns sign-in, phone verification, or a device record; use the cashier-linked help route when a wallet reference needs checking. We keep the request tied to the relevant account step, so you can ask about a correction, copy, deletion, or policy concern without sending your password.

Team online

Account help path

For a Privacy Policy question about your name, phone verification, sign-in history, or mobile browser record, open account help and identify the account step involved. We use that context to locate the relevant record and may ask for a verification detail before discussing it.

Cashier-linked help

If your request concerns DANA, OVO, GoPay, QRIS, bank transfer, or virtual account data, use the help route beside the cashier path. Include the payment reference and date, not your wallet password, so we can check status while limiting the data shared.

Policy request path

For a copy, correction, deletion request, or concern about cookies, send a policy request through account support. We confirm that the request belongs to you, explain any record that must remain for reconciliation or legal duties, and tell you what action follows.

DATA PRACTICES

What We Do With Your Account Data

Privacy at 55wealth is handled through practical account controls rather than broad promises. Phone verification helps us connect a sign-in to the right account, while device and browser signals help us spot…

Collection purpose

We collect registration and phone details to create and protect your account, then use sign-in and device signals to assess whether an access attempt fits your account history. Payment references from DANA, OVO, GoPay, and QRIS help us match a cashier event without needing your wallet password.

Cookie controls

Our browser pages may use cookies or similar signals to keep an account session working, remember a selected setting, and help identify unusual sign-in behaviour. You can clear cookies in your browser settings, but doing so may require phone verification again on that device.

Account security

Phone verification is required before account access in the relevant flow, and we do not ask for your password in a support message. Keep your sign-in details private and contact account help if a computer or mobile browser shows activity you do not recognise.

Payment matching

When you ask about a wallet or bank record, we use the payment method, reference, date, and account context to check the status. This applies to QRIS, DANA, OVO, GoPay, bank transfer, and virtual account steps without requesting a private wallet passcode.

Retention approach

We keep account, payment, support, and security records only while a stated operational, reconciliation, dispute, security, or legal purpose requires them. When that purpose ends, the record is deleted or separated from direct account access according to our internal handling process.

Changes and requests

You can ask us to correct account data, provide a copy, explain a collection purpose, or delete eligible records. We verify the requester first, then explain any limit where a record must remain for a payment check, account security matter, or legal duty.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. They cover the data created by phone verification, mobile browsing, payment references, cookies, and support requests. If your situation is different, use the policy request path and describe the account step, device, or payment reference involved.

The 55wealth Privacy Policy covers registration details, phone verification, sign-in and device signals, cookies, payment references, support messages, and requests about your data. It explains why we use each category, how we protect account access, and when a record may be retained for reconciliation or legal duties.

Phone verification helps connect account access to the person who created the account and helps us respond safely to data requests. If you ask for a copy, correction, or deletion, we may use the same verification step before discussing records linked to your account.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account steps. We use the reference, date, method, and account context to investigate a receipt or cashier status without asking for your wallet password.

Open the policy request path through account support and state whether you want a copy or a correction. Include the affected account step, such as phone verification or a QRIS reference, but do not send your password. We verify your identity before making a change or sharing account records.

Cookies can keep your account session active, remember a setting, and help us identify unusual access on a mobile browser. You can clear them through your browser controls. After clearing cookies, you may need to sign in and complete phone verification again before account access.

We retain data for the period needed to operate your account, check payment reconciliation, handle support or disputes, protect security, or meet a legal duty. The exact period depends on the record and purpose. You can ask us which purpose applies to a specific account or payment record.

You may request deletion of eligible account data through the policy request path. We first verify that the request is yours, then check whether a record must remain for payment reconciliation, security, dispute handling, or legal duties. We explain any retained record and the reason it remains.