Reference

Privacy Policy for Your drips4d slot Account

The drips4d slot Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account data explainedWallet records coveredCookie choices availableSupport contact path
drips4d slot Privacy Policy for Your drips4d slot Account
ACCOUNT HELP

Contact Us About Your Privacy Choices

A clear contact route matters when an account detail looks wrong or a wallet record needs explanation. Our support desk can help you identify the correct account, locate a payment reference and send a privacy request for handling by the appropriate team. Include the phone number linked to your account, the relevant date and the exact issue, but do not send a password or full wallet credentials. We keep the request focused so your personal details are not repeated across unnecessary messages.

Team online

Privacy request

Use our support contact path to ask what account details we hold, why a record was used, or how to request a correction. Include your account phone number and a clear description so we can check the right profile without requesting your password.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears beside the wrong account, send the receipt reference and transaction date through support. We compare the record with the account history and explain the status without asking you to share your wallet PIN.

Access concern

For an unfamiliar sign-in or a phone verification problem, contact the support desk before trying repeated account changes. We may ask for limited identity details to protect the profile, then record the request and explain the next privacy step.

DATA PRACTICES

Browse How We Handle Account Data

Privacy work follows the same account path you use from phone verification to the lobby. We separate login details from payment references, limit internal access to people handling account or security tasks…

Collection at signup

When you open an account, we collect the phone number and login details needed to create the profile. Phone verification confirms that you control the contact route before account access, while optional messages are kept separate from core sign-in records.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references may appear in account records when you use a supported payment route. We use the reference, amount and status to reconcile activity, not to store your wallet PIN or bank password.

Cookie controls

Cookies can keep a session active, remember a language or device preference, and show whether a page loaded correctly. Your browser settings let you delete or block them, although some account screens may ask you to sign in again afterward.

Security signals

We may assess device type, browser details, approximate connection data and sign-in timing when protecting an account. A new phone or unusual pattern can trigger an extra check; this helps us separate a genuine login from an access attempt.

Retention period

We keep account, support and payment-reference records only for the period needed for account operation, security checks, dispute handling and legal duties. When a record no longer serves one of those purposes, we delete it or remove identifying links.

Change request

You can ask us to correct an inaccurate phone number, contact detail or account record through support. We may verify ownership before making a change, and we will explain if a record must remain because a security, dispute or legal need still applies.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. We explain the data linked to sign-in, payment references, cookies, device checks and support requests in plain terms. If your situation is not covered, contact us with the account phone number and a short description; where local law permits, we will assess the request through the same privacy process.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. The policy also explains why we use each category, how long records may remain, and how you can ask about access or correction where local law permits.

We use your phone number to create the account, send the verification step and help match a privacy request to the correct profile. It also helps us investigate an unfamiliar login. We do not need your wallet PIN or bank password for this process.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, including a receipt reference, date and status. We use those details to reconcile account activity and answer support questions, while wallet PINs and bank passwords remain outside our records.

Contact our support desk with your account phone number, the request type and the specific record you want checked. We may verify account ownership before responding. Where local law permits, we will provide the available details or correct an inaccurate record.

Cookies may keep your session active, remember a device preference and show whether account pages load correctly. You can remove or block them in your browser settings. Blocking some cookies may end your session or require another phone verification step.

We retain information for the time needed to operate the account, protect sign-in, address payment disputes, answer support requests and meet legal duties. After that need ends, we remove the record or separate it from identifying account details.

Contact support promptly and provide the account phone number, approximate sign-in time and device details if available. Do not send a password, wallet PIN or bank password. We will record the concern, check security signals and explain the next account-protection step.