Reference

Privacy Policy for paus66 Accounts

paus66 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet activity and support requests.

Clear data purposesWallet activity recordsPolicy access anytimePhone verification context
paus66 Privacy Policy for paus66 Accounts
CONTACT PATHS

Privacy Questions Reach Our Support Team

A clear contact path helps you ask what we hold, why we use it or how to correct an account detail. Send your privacy request through the support route linked from your account area and include the email or phone detail attached to your paus66 account. We may ask for an account step or verification detail before discussing private records. This protects your information when a request concerns wallet status, login history or a receipt linked to DANA, OVO, GoPay or QRIS.

Team online

Account request

Use the support path inside your account when you want to ask about stored profile details, phone verification or a sign-in record. We use the account identifier you provide to locate the correct record and may request confirmation before sharing any private account detail.

Wallet query

If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the payment receipt and the related account detail through support. We use that information to trace the status without asking you to post wallet credentials or security codes in an open message.

Policy request

For a copy, correction or privacy question, mention Privacy Policy in your support message and describe the requested change. We assess the request against account security and local requirements, then explain the next account step through the same protected contact path.

DATA PRACTICES

How paus66 Handles Your Data

We separate account details from the operational records needed to keep access and wallet checks orderly.

Account data

We use the profile details you submit to create and maintain your account, complete phone verification and respond to account…

Cookies

Cookies can keep a sign-in session working, remember basic browser choices and help us see whether a page loads correctly…

Security records

We may retain device, session and sign-in signals to investigate unusual access and protect your account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a payment status with your account.

Retention

We keep account, security and payment records for the period needed for access management, dispute handling, fraud checks and applicable…

Your request

You can ask us to access, correct or clarify personal details connected with your account, subject to identity checks and…

Privacy Policy Questions About paus66

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening an account. We explain the practical path for checking data, cookies, payment references and security records without turning the policy into a general description of the lobby. If your question concerns a specific record, use the protected support route and identify the account detail involved.

The paus66 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can ask about or correct a record, where local law permits.

We use phone verification to connect account access with the contact detail you provide and to reduce account confusion during sign-in. The verification event may be retained as an access record. We will not ask you to place a one-time security code in a support message.

Yes. Privacy Policy coverage includes payment references linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use the relevant receipt or reference to check status and resolve a question, while avoiding requests for your wallet password or private security code.

You can request a correction through the account support path. State which detail is wrong and provide the account contact used for verification. We may ask for an additional account step before changing the record, then retain the request and outcome for account security.

Cookies can maintain a browser session, remember basic settings and help us identify page loading issues on your phone or desktop. Browser controls let you remove or block them. If necessary cookies are blocked, you may need to sign in again or repeat phone verification.

Retention depends on the type of record and the reason we need it, such as account access, payment checking, security investigation or dispute handling. Privacy Policy requests about a specific record can receive a more precise explanation after we confirm your account contact.

Use the protected support route connected with your paus66 account and write that your message concerns Privacy Policy. Ask for access, correction or an explanation of a data use. We verify account ownership first and respond according to local requirements where local law permits.