Reference

Privacy Policy For Your carte66 Account

Our Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact steps

Browse Our Lobby Read FAQ

How Privacy Policy Covers Wallet Data

carte66 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you submit for an account, including your phone number, verification status, sign-in records, device details, support messages, and payment references. We use these details to connect the right account with wallet activity, check unusual access, and answer a receipt or status

1
question without exposing another person’s records. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references may appear in our records when you choose those routes. We keep access subject to where local law permits and apply the policy to your use of the account, lobby,
2
and related support path.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP PATHS

Where To Ask About Privacy Policy

A clear contact route helps when a Privacy Policy question concerns your account rather than a general request.

DATA PRACTICE

How carte66 Handles Your Policy Choices

Privacy Policy choices should be practical, so we describe the records behind everyday account actions rather than using broad promises.

Account data handling

We use your phone number, verification state, sign-in events, and account choices to maintain the correct profile. These details also help us distinguish your request from another account when support checks a record.

Cookies and browser use

Cookies can help remember a session or device setting while you move from login to the lobby. Your browser controls can clear or restrict them, although some account steps may then need to be repeated.

Wallet references

A DANA, OVO, GoPay, QRIS, virtual account, or bank transfer reference can be stored with the related account action. We use that reference to check status and receipts, not to request your wallet password.

Account security

Phone verification comes before account access, and device signals can help identify an unfamiliar sign-in. If your phone is shared or replaced, sign out where possible and use the support path for an access concern.

Retention approach

We retain account, payment-reference, and support records for the period needed for their stated purpose or an applicable legal requirement. A retention question can be sent from your signed-in account support route.

Changes and contact

To request a correction, access copy, or eligible deletion, identify the account phone number and describe the record involved. We may need an account check before changing data linked to your profile.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the account actions you are most likely to ask about before opening an account or returning from a mobile device. We explain what may be connected to wallet records, how to request a change, and why a phone or browser check can appear. If your question is not covered, use the account support path and include only the details needed to locate your profile.

The carte66 Privacy Policy covers account details, phone verification, sign-in and device records, cookie use, support messages, and payment references. It explains why we use each category, how retention works, and how you can ask for access, correction, or an eligible deletion.

We use your phone number to identify your account and complete the phone verification step before account access. It can also help us match a Privacy Policy request to the right profile. Do not place a one-time code in a support message.

Yes. Privacy Policy treatment includes references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. We may use a reference and date to check a receipt or status, but we do not need your wallet password for that check.

Open the signed-in support path, identify the phone number on your profile, and ask for an account-data access request. Describe the category you need, such as device records or wallet references. We may verify account control before responding.

You can request a correction when an account detail is inaccurate or incomplete. Send the request through support with the relevant category and the corrected detail. We may ask for a verification step before changing information tied to your account.

Cookies may remember a session or browser setting as you move from login to the lobby on a phone. Clearing or blocking them can remove that convenience and require another sign-in. Your browser settings control this choice, subject to account security steps.

Yes. Account access and eligibility depend on local law. The Privacy Policy explains how we handle records when access is available, while your location, account checks, and applicable rules may affect whether you can continue from a particular device or region.

Privacy Policy For Your carte66 Account

Where To Ask About Privacy Policy

How carte66 Handles Your Policy Choices

Account data handling

Cookies and browser use

Wallet references

Account security

Retention approach

Changes and contact

Privacy Policy Questions About Your Account

01 What does the carte66 Privacy Policy cover?

02 Why does carte66 need my phone number?

03 Does Privacy Policy cover DANA and QRIS records?

04 How can I request my carte66 account data?

05 Can I ask for a correction under the Privacy Policy?

06 How do cookies affect my mobile account access?

07 Does access to carte66 depend on local law?

Related Pages