Reference

Open prima66 Privacy Policy Before Account Access

prima66 Privacy Policy shows how we handle your account, device and wallet details before you open the lobby.

Account dataWallet recordsDevice choicesPolicy requests
prima66 Open prima66 Privacy Policy Before Account Access
ASK OUR TEAM

Contact Us About prima66 Privacy Policy

A clear support route helps when a privacy question is tied to an account event. Use the help path available after sign-in and include your account identifier, the date of the request, and the wallet reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a password or full wallet credentials. If you cannot sign in, use the contact route displayed on the access page and explain that your request concerns the Privacy Policy.

Team online

Account help path

For an account data question, open the support route after sign-in and state whether you want access, correction or deletion. We may ask for a phone verification step before discussing private account records.

Wallet record check

If your question follows a DANA, OVO, GoPay or QRIS transaction, send the visible reference and date rather than wallet passwords. We can use that reference to locate the related privacy record.

Login access route

When sign-in itself is blocked, follow the contact option shown on the login page. Tell us which device path you used and whether phone verification appeared, so we can protect the account while handling your request.

DATA IN PRACTICE

Explore Account Security And Data Choices

We keep the Privacy Policy connected to the steps you actually take: account creation, phone verification, wallet selection and mobile sign-in.

Account records

We use the details you enter during account creation, including contact details and verification status, to maintain the account and respond to requests. We do not need your password in a support message.

Cookies and sessions

Cookies and similar session details help keep your login connected to the right account across a mobile browser. You can clear browser data, but doing so may require another phone verification step at the next sign-in.

Device signals

A device type, browser setting and session timestamp can help us identify unusual access or repeated account changes. These signals support account protection and are not a request for access to your private files.

Wallet matching

When you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we retain the reference needed to match a status update to your account. Wallet passwords and secret codes should stay with you.

Security checks

Phone verification may be required before we disclose account details or change a privacy contact. This step helps prevent another person using a saved browser session from receiving your records.

Retention and requests

We keep records only as long as needed for the stated account, security, dispute or legal purpose. Where local law permits, contact us to ask for a copy, correction, restriction or deletion assessment.

Browse Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often before account access. We connect each answer to a real prima66 step, such as phone verification, mobile sessions or a DANA and QRIS reference. If your request is unusual, contact us through the account help route and include only the details needed to locate it.

It covers account details, phone verification, device and session data, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security checks and how to ask about your records.

Phone verification helps connect an account request to the person who controls the registered contact. We may require it before changing account details or releasing private records, especially when a request comes from a new browser or an unfamiliar device.

Yes. The Privacy Policy covers the reference, amount status and timing details needed to match a DANA or QRIS event to your account. It does not ask you to send a wallet password, secret code or full authentication credential through support.

Where local law permits, you can ask for a copy or correction through the signed-in help path. Include your account identifier and the type of record involved. We may complete phone verification first, then explain any limits that apply to the request.

Mobile cookies and session records help keep your sign-in connected while you move between account pages and the lobby. Clearing them can end the session and trigger phone verification again. Your browser settings control some cookies, while necessary session records support account security.

Retention depends on why the record was created. Account, security, payment-reference and support records may remain while needed for service, dispute handling, fraud prevention or legal duties. Where local law permits, you can ask us to assess deletion or restricted handling.

Yes. Access to the service and some privacy requests depends on local law. We assess requests using the policy that applies to your account and region. If eligibility is unclear, contact us through the displayed support route before sending extra personal details.