Reference

Privacy Policy for Your padi4d Account

Your padi4d account keeps login, wallet, cookie, and support data under one Privacy Policy, so you can open an account with clear data terms before you enter Aviator…

Login and cookie dataDANA OVO GoPay QRISChat and email requests
padi4d Privacy Policy for Your padi4d Account
PRIVACY HELP

Contact Us About Privacy Requests

Fast privacy help matters when a wallet record, login device, or chat transcript looks wrong. We keep privacy requests close to your account so our team can verify you before changing anything. Use live chat for current sessions, WhatsApp for follow-up screenshots, or email when you need a written trail for correction, export, or deletion requests. We answer in English and Indonesian phrases that match your account details.

Team online

Live chat

Use live chat from 09:00 to 02:00 WIB when you need us to check login history, cookie consent, or a payment reference while you are still signed in to your account.

WhatsApp follow-up

Send screenshots through the WhatsApp contact listed in your account footer when a DANA, OVO, GoPay, or QRIS privacy query needs context. We verify your account before discussing personal data.

Email privacy desk

Email our privacy desk at [email protected] for correction, export, or deletion requests. Include your username, registered phone, and the date range so we can locate the right records.

ACCOUNT CONTROLS

Account Data Controls You Can Use

Privacy controls work better when you know where to look. Inside the account menu, we separate profile data, wallet references, cookie choices, and login devices so a privacy request does not become…

Account data collected

We ask for the account data needed to create and protect your login: username, phone or email, password hash, IP area, and device marker. Extra data is requested only when a support case needs it.

Payment record handling

DANA, OVO, GoPay, and QRIS references are stored with wallet activity so we can match transfers, answer disputes, and meet bookkeeping duties. Card numbers or wallet passwords are not stored by us.

Cookie choices

Cookies keep your session active and remember language choices. On Android Chrome, check Chrome > Settings > Privacy and security > Third-party cookies if you want to clear or block browser storage.

Login device checks

Open Account > Security > Login Devices to see recent device sessions linked to your account. If you spot a device you do not recognise, contact live chat before changing personal data.

Retention periods

We keep records while they are needed for account service, payment disputes, fraud prevention, and legal duties. After that, we delete, anonymise, or restrict access where our systems allow it.

Change requests

You can ask us to correct profile details, export eligible account data, or delete data that we no longer need. We verify your identity first so another person cannot change your record.

Privacy Questions Before Opening Your Account

Before you open an account, the Privacy Policy should answer practical questions, not legal fog. These answers explain what we collect, how payment records are tied to you, how cookies behave on mobile, and how you can contact us when a record needs correction. If your case needs more detail, use the support paths above. We keep the wording plain so you can decide calmly.

We collect the details you give during account creation, including username, phone or email, password hash, IP area, device marker, wallet references, and support messages. Each record is tied to security, account service, or payment matching.

Yes. DANA, OVO, GoPay, and QRIS references are covered because they can point back to your wallet activity. We use them for reconciliation, dispute checks, and legal bookkeeping where required.

Cookies remember your session, language choice, and risk signals on your phone browser. You can clear them through Chrome Settings or your browser privacy menu, but you may need to log in again.

Yes. Contact live chat or email with your username, registered phone, and the field that looks wrong. We verify your account before changing profile, contact, or wallet-related data.

We keep chat and payment records while they are needed for account service, disputes, fraud prevention, and bookkeeping duties. When the reason ends, we delete, anonymise, or restrict the record.

Only staff and service providers with a work reason can access your account data. Payment processors, hosting teams, and support tools receive limited fields needed to complete their task.

Access depends on local law and is available only where local law permits. If a rule affects your account, we may limit access, keep required records, or ask for extra verification.