Reference

Privacy Policy For Your aladdin4d Account

aladdin4d Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount access choicesContact path included
aladdin4d Privacy Policy For Your aladdin4d Account
HELP WITH YOUR DATA

Get Privacy Policy Help Through Support

A direct support route helps you resolve a Privacy Policy question without repeating your account story across different teams.

Privacy requests Use support chat for a copy of your stored account details, a correction request…
Wallet references Include the DANA, OVO, GoPay or QRIS payment reference when your request concerns a…
Account verification We confirm that a privacy request comes from the account holder before sharing personal…
CONTROL YOUR RECORDS

What Our Privacy Process Covers

Privacy work is part of the account path, not a separate promise hidden from the cashier screen.

Collected details

We may handle your phone number, account label, sign-in events, device signals, payment references and support messages.

Cookies and sessions

Cookies and similar browser signals help maintain your session and remember selected settings.

Account protection

Clear phone verification before account access helps us connect a request to the right account.

Payment matching

A QRIS receipt, bank transfer reference or virtual account record can be matched with your account status.

Retention choices

We keep account and transaction records for the period needed for service, security or applicable legal duties.

Request changes

Ask us to correct inaccurate details, explain a processing purpose or remove eligible records through support chat.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. They cover the practical points: which details we handle, how payment references are used, what happens on a phone, how long records remain and how you can contact us. If your situation is not listed, send the account context through support chat during 09:00-22:00 WIB.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains why we use those records, how we protect account access, when retention ends and how you can ask for a copy or correction.

No. The Privacy Policy allows us to record a DANA, OVO, GoPay or QRIS reference needed to match a transaction status, but we do not need your wallet password. Send only the receipt or reference requested through our support chat.

Open support chat between 09:00-22:00 WIB and state that you want an account-data copy. Include your registered phone number and request details. We verify account ownership first, then explain the records available and any lawful reason a record must remain.

Yes, you can ask us to correct an inaccurate account label, phone detail or other eligible record through support chat. Tell us what is wrong and what it should say. We may request phone verification before changing information connected to wallet status.

When you use an Android or iPhone browser, cookies and device signals can maintain your session, remember settings and flag unusual sign-in activity. Clearing browser data may sign you out. The same Privacy Policy applies when you return through the mobile lobby.

We keep payment references, account records and support messages only for the period needed for service, security or applicable legal duties. A bank transfer, virtual account or QRIS receipt may therefore remain after a session ends, then be removed or anonymised.

You can request deletion of eligible personal records through support chat. We first verify the request and check whether a record must remain for security, payment reconciliation or a legal duty. Where local law permits, we remove or anonymise data after that check.