Reference

Privacy Policy For Your cip138 Account

cip138 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and enter the lobby from a phone or computer.

Account clarityWallet recordsDevice controlsDirect requests
Explore Our Lobby Read FAQ
cip138 Privacy Policy For Your cip138 Account
HELP PATHS

Get Privacy Help Beside Your Account

A clear support route helps you ask about Privacy Policy handling without explaining your whole account from the beginning. Start from the support path connected to your cip138 account and include the email or phone detail used at sign-in, plus a receipt reference when your request concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record, while access and any response remain subject to local law.

Team online

Data request

Ask what account, device or wallet records we hold by using the support path linked to your account. Include your registered contact detail so we can match the request before discussing any personal record.

Wallet question

When a DANA, OVO, GoPay or QRIS receipt appears unclear, send the transaction reference through account support. We use that reference to separate a payment-status question from a request about how your personal data is handled.

Access concern

If phone verification or a sign-in event looks unfamiliar, contact us through the account support route and describe the device path involved. We can then check the related access record without asking you to post private details publicly.

DATA PRACTICE

What We Do With Your Privacy Requests

Privacy Policy requests are handled against the records that actually support your account: sign-in events, phone verification, wallet references and support messages.

Account details

We use the contact detail you submit during account creation and phone verification to identify your account, respond to requests and connect a wallet record to the correct account. Please keep that detail current when you ask for a change.

Device signals

A phone or computer sign-in can create device, browser and session signals. We use them to spot unusual access and investigate a login concern; they also help us understand which access path needs attention when you contact support.

Wallet records

DANA, OVO, GoPay and QRIS can produce references that sit beside your account activity. We use those references to reconcile a receipt or status question, while the payment provider may keep its own separate record under its terms.

Cookie choices

Cookies and similar session tools help keep your sign-in path working and remember the state of an account page. You can control browser storage through your device settings, though changing it may interrupt access or require another phone verification step.

Retention checks

We retain account, payment-reference and support records for the period needed to operate the service, resolve disputes or meet legal duties. When a record is no longer needed for those purposes, our handling moves toward removal or restricted storage.

Change requests

To request correction, access or clarification, contact us through the support path connected to your account. State the request plainly and provide your registered contact detail; we may verify ownership before changing or releasing personal data.

Privacy Policy Answers For cip138

These Privacy Policy answers address the account, wallet and device questions we expect before you open access. Each answer points you toward the relevant account step or support path, so you can decide what to share and how to request a change. Access depends on local law and remains available where local law permits.

The cip138 Privacy Policy covers account details, phone verification, sign-in and device signals, wallet references, cookies, support messages and retention. It explains why we use each category to provide account access, investigate security concerns, match payment receipts and respond to your data requests.

When you open an account, we collect the details needed to create and verify it, including your registered contact detail and phone-verification result. Sign-in events and device signals may also be recorded so we can investigate unfamiliar access and connect a support request to your account.

Yes. The Privacy Policy covers payment references and account records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. The relevant payment provider may retain its own transaction record, while we use the reference to check status and answer your account question.

Use the support path connected to your cip138 account and state which detail is inaccurate, such as a contact record or account field. Include your registered contact detail so we can verify ownership before correcting the record or explaining why a change cannot be made.

You can ask about device and session signals through account support. Tell us which sign-in or phone path concerns you, without posting private credentials. We may verify account ownership first, then explain the relevant record and its purpose under the Privacy Policy.

We keep wallet references, account events and support messages for as long as needed to operate access, settle a dispute, investigate security or meet a legal duty. Once those purposes end, the record may be removed or placed in restricted storage.

Yes. Access depends on local law, and our handling applies where local law permits. If your location or eligibility affects access, we use the account and support details needed to address that question. The Privacy Policy does not override requirements that apply in Indonesia.

Related Pages

cip138 Indonesia dotabet About Us Access guide betso88