Reference

Privacy Policy for d200mslot Accounts

d200mslot Privacy Policy shows how we handle the details connected with your account, DANA or QRIS activity, device access and cookie choices.

Account clarityWallet data contextCookie choicesDirect contact route
d200mslot Privacy Policy for d200mslot Accounts
CONTACT YOUR WAY

Where Privacy Questions Go

A clear contact route matters when your account record or wallet reference needs attention.

Account contact Use the privacy contact path linked from your account area when you want to…
Wallet reference If your request concerns DANA, OVO, GoPay, QRIS, a bank transfer or a virtual…
Correction request For a name, phone number or contact detail correction, tell us what is inaccurate…
DATA IN PRACTICE

What Your Privacy Settings Cover

We keep this policy practical by connecting each data choice to an account action you can recognise.

Account security

Phone verification helps us distinguish an account request from an unknown sign-in attempt. We use account checks before discussing personal details, and we do not ask you to disclose a password, wallet PIN or one-time security code through a privacy request.

Device signals

When you move between a mobile browser and desktop, technical signals such as browser type, session time and device settings may help us keep the account session secure. These signals are used for service protection and troubleshooting, not as a substitute for your account details.

Cookies

Cookies can remember a session, support page preferences and help us understand whether a page loads correctly. Your browser provides controls for removing or blocking them, although changing those settings may affect sign-in continuity or the way the Privacy Policy page is displayed.

Payment records

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account reference can help match a cashier request with your account. We limit what we retain to the details needed for reconciliation, account protection, dispute handling and any legal recordkeeping that applies.

Retention timing

We keep personal data only for as long as its stated purpose, account security, dispute handling or an applicable legal duty requires. When a retention period ends, records are removed, anonymised or isolated according to the process used for that data type.

Change requests

You can ask whether we hold a particular account detail, request a correction or ask a question about its use through the privacy contact route. We may need identity checks, and some records may remain when a legal or transaction duty requires continued retention.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and device questions we expect you to ask before opening an account. They explain what to include in a request, how wallet references are treated and why an identity check may be needed. If your situation is not covered, use the contact route above and mention the exact page or account action involved.

It covers details supplied during account creation and phone verification, plus records linked to sign-in, cookies, device sessions, support requests and payment references. It also explains our reasons for using data, retention approach, security checks and the contact steps available to you.

Phone verification helps connect an account request with the correct account holder before access or a privacy response is provided. It can also reduce mistaken or unauthorised requests. We will not ask you to send a password, wallet PIN or one-time security code.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity on your account. The relevant payment provider may also keep separate records under its own terms, so check that provider when needed.

Use the privacy contact path from your account area and describe the inaccurate detail, such as a phone number or contact name, together with the requested correction. We may verify your identity first, then record the request and apply the change where permitted.

The retention period depends on why the record exists. We may keep account, security, payment or request records for the time needed to perform that purpose, resolve a dispute or meet a legal duty. Afterward, data is removed, anonymised or isolated.

You can use your browser controls to block or remove cookies, including those that remember a session or page preference. Some account pages may then behave differently, such as asking you to sign in again. Cookie choices do not automatically erase account records.

Yes. Account eligibility and access depend on local law, including the rules that apply where you are located. This Privacy Policy explains data handling; it does not change those requirements. Check the applicable local position before submitting personal details or opening an account.