Reference

Privacy Policy For Your paus slot Account

Our Privacy Policy explains what we collect when you open a paus slot account, sign in from a mobile browser, or check DANA and QRIS status.

Account clarityWallet contextCookie choicesSecurity steps
paus slot Privacy Policy For Your paus slot Account
CONTACT ROUTES

Where To Ask About Privacy Policy

Privacy questions should reach the same account route that handles login and wallet status issues.

Account help Use the account help route when you want to ask what personal data is…
Cashier status For a privacy question about a DANA, OVO, GoPay, or QRIS reference, contact support…
Change request Ask for access, correction, or deletion through support with the email or phone detail…
DATA PRACTICE

How We Handle Account Data

We handle privacy as an account operation, not as a separate promise hidden from your wallet flow.

Account records

We collect the details needed to create and maintain your account, including contact information and phone verification status. A clear account path helps us connect your request to the correct record instead of relying on a name alone.

Device signals

When you sign in through a mobile browser, we may record device and session signals used to spot unusual access. These details help us distinguish a normal return to the lobby from an account event that needs an extra check.

Cookie controls

Cookies can keep a session active, remember selected settings, and help us understand whether a page request worked. You can manage cookies through your browser controls, although removing them may require you to sign in again.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we handle reference numbers and status data rather than wallet passwords or PINs. This lets support check a receipt while limiting the sensitive payment details we hold.

Retention checks

We retain account, security, payment-reference, and support records only for the period needed for their stated purpose, account administration, dispute handling, or legal duties. When a record is no longer needed, our handling process moves it toward removal or anonymisation.

Your requests

You can ask what data we hold, request a correction, or ask about deletion through the support route. We may verify your phone or account detail first, then explain any record that must remain for security, payment reconciliation, or legal reasons.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the records you create through account access, phone verification, browser sessions, and local wallet references. We keep each answer tied to a practical action you can take. If your question concerns eligibility or account access in Indonesia, that position depends on local law and the conditions that apply where local law permits.

It covers account details, phone verification, browser and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains why we use those records, how we protect them, and how you can make a request.

We use phone verification to confirm account access and reduce the chance that another person changes your details. The record shows that the verification step occurred; it does not give us your phone password or wallet PIN. We may repeat the check before processing a sensitive privacy request.

Yes. When you sign in from a mobile browser, we may handle session times, device signals, cookie settings, and security events. These details help us investigate unusual access and keep your account path working. Browser controls let you manage cookies, though clearing them can end an active session.

We use payment references, timestamps, and status information to match a DANA or QRIS transaction with your account and receipt. We do not need your wallet password or PIN for that check. If you contact us, share the reference shown on the receipt rather than private wallet credentials.

You can contact support through the account help route and ask for access to your personal data or correction of an inaccurate detail. Include the account phone or email so we can locate the right record. We may verify ownership before disclosing or changing information.

You may submit a deletion request through support, and we will assess the records involved. Some account, security, payment-reference, or support records may need to remain for legal duties, dispute handling, or transaction reconciliation. We will explain the reason if a record cannot be removed immediately.

Yes. Access and eligibility depends on local law, and this Privacy Policy is applied where local law permits. The applicable rules can affect what data we must retain, what request rights are available, and how we confirm an account before making a privacy-related change.