Reference

coop4d Privacy Policy For Your Account

coop4d Privacy Policy explains how we handle your account details while you move between Live Blackjack Prestige, Aviator Mobile Play and local wallet steps.

Clear data purposesWallet status contextAccount access requestsCookie choices
coop4d coop4d Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Help Beside Your Account

A privacy question should not leave you guessing which route to use. Our support path connects account access, wallet status and data requests in one place, so you can explain the issue with the relevant phone verification or payment reference. If you are reaching us from Medan or another Indonesian city, include the device path you used, such as mobile browser or desktop browser. We can then direct your request without asking you to repeat unrelated account details.

Team online

Data request

Ask us what personal data is linked to your coop4d account and why it is used. Include your registered phone number and the request type so we can check identity before discussing account records.

Wallet reference

For a DANA, OVO, GoPay or QRIS privacy question, share the relevant transaction reference rather than sending a full wallet password. We use the reference to locate status details while limiting unnecessary exposure.

Access concern

If your phone verification or Two Factor Setup record looks unfamiliar, contact our account support path promptly. We can review the session details, explain the security step and help you request a correction.

HANDLING DETAILS

How coop4d Handles Your Privacy Choices

Privacy controls work best when each account step has a defined purpose. We separate identity details from ordinary browsing signals where our systems allow, restrict account access through verification checks and use…

Account data

We use your phone number and verification result to connect you with the correct account. Before discussing private records, our team may ask for an account step that confirms you are the person making the request.

Cookie controls

Cookies can preserve a sign-in session, remember a device preference or help identify unusual access. Ask our support path which cookie category applies to your browser and request changes where that option is available.

Payment records

DANA, OVO, GoPay and QRIS references help us match a wallet status or receipt question. We do not need your wallet password for that check, and we keep the reference tied to the relevant account event.

Security events

Two Factor Setup and device-session records help us investigate an unfamiliar login. If you switch from a mobile browser to a desktop browser, that change may appear as a security event for account protection.

Retention timing

We retain personal data only while a stated purpose remains active, or when a security, dispute or legal need requires it. You can ask which category applies to a record and whether restriction or deletion is available.

Correction route

Send a correction or access request through our support path with the affected account step. We review the request, confirm identity and explain the result instead of changing records from an unverified message.

Privacy Policy Answers For coop4d

These Privacy Policy answers address the questions we expect you to ask before opening an account from Indonesia. They explain which data is connected to account access, how wallet references are handled, what cookies do on mobile and desktop browsers, and how to request a change. If your situation is specific, send the account step or payment reference through our support path so we can respond to the actual record rather than a general description.

The coop4d Privacy Policy covers account details, phone verification, device-session data, cookies, payment references and support requests. It explains why we use each category, how we protect access and how you can ask about, correct or restrict a record where local law permits.

We may collect the phone number and verification result used for account access, along with technical session details from your mobile or desktop browser. Payment activity may add a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, QRIS and the other listed payment rails. We use those references to check a receipt or wallet question, and you should never send a wallet password through support.

Cookies may keep a session active, remember a browser preference or help detect unusual access to your account. A mobile browser and desktop browser can create different session records. Contact support to ask which cookie category applies and what change options exist.

You can ask for access to the personal data linked to your account or request a correction. Send the request through our support path with your registered phone number and the affected account step; we confirm identity before discussing private records.

We keep records while they support account security, service delivery, dispute handling or a legal requirement. A DANA, OVO, GoPay or QRIS reference may remain for the related purpose. Ask us which retention reason applies to a specific record.

Yes. Account access and eligibility depend on local law. Our Privacy Policy still explains how data is handled when you use an available account path, and our support team can help you submit a privacy request without assuming access is available everywhere.