Reference

proslot Privacy Policy For Your Account

Your account details, wallet status and device access are covered clearly in the proslot Privacy Policy.

Account dataWallet referencesDevice controlsClear contact path
proslot proslot Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Policy Help From Account

A clear contact route matters when a name, phone number or wallet reference needs attention. Start from your signed-in account area and use the support request path to ask about personal data held under your account. Include the account step involved, such as phone verification or a QRIS status check, so we can identify the relevant record without asking you to send a wallet password. If you cannot sign in, use the available account-help route and provide only the details needed to locate your request.

Team online

Account request

Use the support path inside your account to ask which personal details we hold, why they are used, or how a correction request should be submitted. Mention your phone verification step so our team can connect the privacy question with the correct account record.

Wallet reference

If DANA, OVO, GoPay or QRIS appears incorrectly in your account history, contact us through the account-help route. Share the payment reference and date shown to you, but never send a wallet password, one-time code or full security credential.

Access problem

When sign-in prevents you from reaching the Privacy Policy request path, tell us whether you are using a mobile browser or desktop. We use that detail to direct the request while keeping the amount of personal data in your message limited.

YOUR DATA CHOICES

What We Do With Personal Data

We keep this policy practical by connecting each data category to an account task. Phone verification supports account ownership, device details help protect a sign-in session, and wallet references help match a…

Collection

We collect details you enter during account creation, including your phone number and verification response. We also receive technical details from the browser or device used to sign in. These records help us connect a request to your account rather than to an unknown session.

Payment data

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep the references needed to identify a payment request and its status. We do not ask for your wallet password. A payment partner may handle the transaction within its own privacy terms.

Cookies

Cookies may keep your signed-in session active or help us understand whether a policy page loads correctly. You can manage browser cookie settings, although blocking essential cookies may interrupt phone verification, account access or the path used to send a privacy request.

Account security

We use phone verification and device-session signals to reduce mistaken access to your account. Never share a verification code with another person. If your device changes or a sign-in looks unfamiliar, contact support from the account-help route as soon as you can.

Retention

We retain personal data for as long as it supports the stated account purpose or a legal, payment-reconciliation or security requirement. When a record is no longer needed, we remove it or separate it from direct account identifiers where that process applies.

Your request

You may ask what data we hold, request a correction, question its use or ask whether eligible records can be removed. Send the request through account support and describe the exact item, such as a phone detail or QRIS reference, so we can respond accurately.

Privacy Policy Questions For proslot

These Privacy Policy answers address the account and payment questions you may have before opening an account. We keep the wording tied to actual steps: phone verification, mobile-browser access, wallet status and requests made through account support. If your situation depends on a local requirement, access depends on local law, and we will handle the request within the rules that apply to your region.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references and support requests. It explains why we use each category, when a service partner may process a task, how long records may remain, and how you can request access or correction.

No. Our Privacy Policy concerns the payment reference and status needed to match your account request, not your wallet password. For DANA, OVO, GoPay and QRIS, send only the reference shown in your account when support needs to investigate a record.

Phone verification helps connect account access to the person who opened the account and helps us respond to account-data requests safely. We may use the verification result for sign-in protection, but you should never share the code itself with support or anyone else.

Yes. Use the support request path in your account and name the record you want checked, such as your phone detail, device session or payment reference. We may need to confirm account ownership before responding, and any request remains subject to local law.

On a mobile browser, cookies may maintain your session and help essential account pages load in the right order. Browser settings can limit them, but blocking required cookies may interrupt phone verification or the path for sending a Privacy Policy request.

We keep records while they serve the stated account, security or payment-reconciliation purpose, and for any period required by applicable rules. Once a record is no longer needed, we remove it or separate direct identifiers where that method is appropriate.

Start with the support route shown after you sign in. If access fails, use the available account-help path and explain whether the issue concerns phone verification, a device session or a wallet reference. Access depends on local law and is available where local law permits.