Reference

99aset Privacy Policy For Your Account

Our 99aset Privacy Policy explains what account details we collect, why we use them and how you can ask about them before opening an account.

Clear collection purposesWallet record clarityAccess request pathCookie choices
99aset 99aset Privacy Policy For Your Account
REQUEST HELP

Three Ways To Ask About Privacy

A clear contact path matters when you need a copy, correction or explanation of your account data.

Account menu Open Support from your signed-in account, choose the privacy subject and describe whether you need access, correction or deletion. We use your account phone number to connect the request to the right record.
Cashier record If your question concerns DANA, QRIS, OVO, GoPay, bank transfer or virtual account data, include the transaction reference only. Never send a wallet PIN, password or full authentication code.
Sign-in recovery When you cannot reach the account menu, use the sign-in help path and state that your request concerns the Privacy Policy. We may ask for account details to confirm that the request is yours.
DATA HANDLING

How We Handle Account Privacy

Privacy choices work best when each data purpose has a clear account step. We limit internal access to records needed for account service, verification, security checks or support, and we do not…

Account details

We may hold your phone number, account identifiers and verification status to create and protect access. Keep your phone available during verification, and tell us through Support if a detail needs correction.

Device signals

Sign-in time, browser type and device signals can help us spot an unusual access attempt. These signals support account security; they are not a request for your device password or wallet PIN.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained to match a cashier event with your account. We do not need your wallet password for that check.

Cookies

Cookies and related browser storage can keep a session connected and remember selected settings. You can manage browser storage through your phone or desktop settings, though some account paths may then require another sign-in.

Retention

We keep records only for the period needed for account service, security checks, dispute handling and legal duties. A deletion request may be limited where a record must remain for one of those purposes.

Policy changes

If this Privacy Policy changes, we will publish the revised wording on the policy page. Check that page before using your account, and contact Support if a change needs clarification.

Privacy Policy Questions Answered

These questions cover the account and device situations you are most likely to face before or after opening access. Each answer points back to the Privacy Policy and the account route we use for verification, corrections and privacy requests.

It covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Open Support from your signed-in account and request access to your data under the Privacy Policy. Include your account phone number so we can confirm ownership before responding.

No. We do not need your DANA, OVO, GoPay or QRIS wallet PIN for a payment reference check. Do not send wallet credentials, passwords or authentication codes in a support message.

Cookies or browser storage can keep a session connected and remember settings. If you clear them through phone or desktop settings, you may need to complete sign-in and phone verification again.

Yes, ask through the account Support route and identify the detail that needs correction. We may request account verification before changing phone, identity or payment-related records.

We retain records for account service, security checks, dispute handling and legal duties only as needed. Some records cannot be removed immediately when a legal or security purpose still applies.

Yes. Account access and any privacy request outcome depends on local law. Where local law permits, we will explain the available route through Support and identify any required verification.