Reference

caqurbet Privacy Policy for Your Account

DANA and QRIS records, phone verification, device access and account messages are covered in the caqurbet Privacy Policy, so you can see what we collect and why before…

Account dataWallet recordsCookie choicesContact requests
caqurbet caqurbet Privacy Policy for Your Account
POLICY HELP PATH

Find Privacy Help From Your Account

A clear contact route helps you ask about personal data without sending sensitive wallet credentials. From your account area, use the support contact path and include the email or phone linked to caqurbet, the subject of your request and any relevant payment reference. We use those details to locate the correct record and respond about this Privacy Policy.

Team online

Account data request

Use the support contact route from your signed-in account to ask which personal data we hold, why it is used and whether a correction request can be opened.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unclear, share the transaction reference only through our support path so we can check the matching account record.

Access and privacy

When you cannot reach the account area, contact support through the available caqurbet access route and state that your request concerns the Privacy Policy.

HANDLING YOUR DATA

See How We Protect Policy Details

Privacy work is tied to practical account events rather than vague labels. We separate login activity, device signals, payment references and support messages so a request can be checked against the right…

Account data

We use the account details you submit, including contact identifiers and phone verification status, to link your login to the correct account and answer requests about your stored data.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain transaction references and status details needed to trace a cashier event without requesting your wallet password.

Cookies and devices

Cookies and device signals help remember session settings, detect unusual login behaviour and keep the mobile path connected to the right account while you move between pages.

Account security

Phone verification and sign-in checks help us distinguish an account holder from an unfamiliar device. Never place a password, one-time code or wallet PIN in a support message.

Data retention

We keep account, payment and support records for as long as needed for the stated service purpose, account security, dispute handling and applicable legal duties, then assess removal.

Change requests

To ask for a correction, access copy or deletion assessment, contact us through the account support path with your linked contact detail and a precise request about the record.

Check caqurbet Privacy Policy Answers

These questions cover the account and payment situations most likely to make you pause before submitting personal data. Each answer stays focused on our Privacy Policy, including what we collect, how we use it and which route you can use when a detail needs attention.

It covers account details, phone verification, login and device activity, cookies, support messages, payment references and the ways you can ask about, correct or assess removal of your personal data.

We use phone verification status to connect account access with the correct contact detail and help identify unusual sign-ins. The Privacy Policy explains this account-security use before you continue.

Yes. It explains that DANA, OVO, GoPay and QRIS references may be used to match a payment status with your account. Wallet passwords and PINs should not be sent to support.

Cookies can keep session settings available, support sign-in continuity and help detect unusual activity. Your browser controls some cookie choices, while necessary session functions may still be required.

You can request a data copy through the account support path. Include the contact detail linked to your account and describe the records you want us to locate under the Privacy Policy.

Send a correction request through support with your linked email or phone and the relevant transaction reference. For DANA, OVO, GoPay or QRIS, avoid including any wallet PIN.

Yes. Account access and any related eligibility depend on local law. Our Privacy Policy applies to the data process described here where local law permits, subject to applicable legal duties.