Reference

paus805 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a paus805 account, sign in from a phone or desktop, and use wallets such as DANA, OVO, GoPay…

Account dataWallet recordsYour choices
paus805 paus805 Privacy Policy for Your Account
REQUEST HELP

Contact paus805 About Your Privacy Policy

A clear support route helps when you want to ask about a Privacy Policy request, correct account data or check a wallet record. Start from the support path inside your account and include the phone number tied to your profile, the affected payment rail and a short description. We use those details to locate the right record without asking you to send a wallet password.

Team online

Data correction

Ask us to correct a phone number, profile detail or account record through the account support path. We may request verification before changing information.

Access request

Request a copy or explanation of personal data connected with your paus805 account. Include your registered phone number so we can identify the correct record.

Wallet status

For DANA, OVO, GoPay or QRIS questions, share the payment reference and status shown in your account. Never send a wallet password or security code.

DATA HANDLING

How We Protect Account Data

Privacy work is tied to practical account steps, not vague promises. We limit access to records used for verification, payment matching and support, and we separate wallet references from wallet credentials.

Account security

We use phone verification before account access and may check device or sign-in details when activity looks unusual. This helps protect your profile from unauthorised access.

Cookie use

Cookies can keep your session active, remember essential settings and help us detect repeated failed sign-ins. Browser controls may let you remove or restrict them.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to your account without storing wallet passwords.

Data retention

We keep account, payment and security records for the period needed to operate the account, resolve disputes or meet applicable legal duties, then review deletion needs.

Device access

When you move between a mobile browser and desktop, we may record device type, session details and security events to protect the same account path.

Policy requests

Use the support route in your account to ask about access, correction, deletion or processing concerns. We may verify ownership before discussing personal records.

Privacy Policy Questions for Indonesia Accounts

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. They explain the practical route for data access, corrections, device records and wallet references when access is available where local law permits.

It covers account details, phone verification, device and session records, cookies, payment references, support requests, retention and the choices available to you. It applies where local law permits access.

No. Our Privacy Policy allows us to record payment references and status for DANA or OVO, but your wallet password and security code should remain with the wallet provider.

We use your phone number for account creation, verification, sign-in assistance and support identification. If you request a change, we may confirm ownership before updating the account record.

Yes. Use the account support path and ask for a data access request. Include your registered phone number and follow any ownership check needed before records are shared.

Send a correction request through account support, naming the field that is wrong and the replacement detail. We may compare the request with your verification record before making changes.

We retain payment references, account details and security records only for operational, dispute or legal needs. The exact period can vary by record type and applicable local law.

Yes. Ask through the account support path for details about cookies, session records or device signals linked to your profile. Browser settings can also control some cookie activity.