Reference

padi4d Privacy Policy for Your Account

Our Privacy Policy explains how padi4d handles your account details, phone verification, wallet records and device access from the first account step onward.

Account dataWallet recordsCookie choicesAccess requests
padi4d padi4d Privacy Policy for Your Account
CONTACT PATHS

Reach Us About Your Privacy Policy

A direct privacy request helps us identify the right account record without exposing details to the wrong person. Use the support contact path shown inside your account when you need help with data access, correction, deletion eligibility or a cookie question. Tell us the email or phone linked to your account and the subject of your request; do not send wallet passwords, PINs or one-time verification codes.

Team online

Account contact

Use the support path inside your account for a Privacy Policy request. Include your registered phone or email so we can match the request before discussing account data.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the transaction reference through support. We can check the account record without asking for your wallet PIN.

Access request

Ask for a copy, correction or eligible removal of personal data through the same contact path. We may request account verification before releasing or changing private records.

DATA PRACTICES

Browse How padi4d Handles Privacy

Clear handling steps help you understand what sits behind an account request. We separate identity details, device signals, payment references and support messages by their operational purpose, then limit access to staff…

Account data

We use your account contact details and phone verification status to create, protect and maintain access. We do not need your DANA, OVO or GoPay PIN to match a payment record.

Device signals

When you move from mobile login to the lobby, we may record browser, device and security-event signals. These details help identify unusual access without treating your game choices as identity proof.

Cookies

Cookies can keep a session connected and remember selected settings. You can manage browser cookie controls, although removing necessary cookies may interrupt account access or require another login.

Payment references

For QRIS, virtual account or bank transfer activity, we retain transaction references and status details needed for account matching and support. The bank or wallet provider remains responsible for its own records.

Retention steps

We keep personal records for the period needed for account security, transaction checks, dispute handling or legal duties where local law permits. After that, records may be deleted or anonymised.

Security requests

If you suspect someone accessed your account, contact us through the account support path and change your password. We may pause a data request until phone or account ownership is checked.

Explore Privacy Policy Answers

The questions below address the practical parts of the padi4d Privacy Policy that matter during account access. We explain what we collect, why payment references appear, how cookies work on mobile, and how you can request access or a correction. Where eligibility or access is discussed, it depends on local law.

It covers account details, phone verification, device signals, cookies, payment references, support messages, retention and requests to access or correct eligible personal data.

We use your phone number for account identification and the verification step before account access. It also helps us investigate an access or security request tied to your account.

Yes. We may keep DANA, OVO, GoPay, QRIS, virtual account or bank transfer references to match account activity and check support questions, but wallet credentials remain with the provider.

Use the support contact path inside your account and state that you are making a Privacy Policy access request. Include your registered phone or email, then complete any ownership check we require.

You can request a correction through account support. Describe the incorrect field and provide the updated detail; we may verify your account before changing records connected to phone, email or payment status.

Necessary cookies can maintain your login session while you move from a mobile browser to the lobby. Browser settings can remove them, but you may need to authenticate again afterward.

You may request eligible removal through support. We assess the request against account security, transaction checks and legal duties; where local law permits, records no longer needed can be deleted or anonymised.