Reference

cincin303 Privacy Policy for Your Account Data

Our Privacy Policy explains how cincin303 handles the account details connected with DANA, OVO, GoPay and QRIS activity, from phone verification through wallet status checks.

PHONE VERIFICATIONWALLET RECORDSCOOKIE CHOICESACCOUNT REQUESTS

Explore The Lobby Read FAQ

How Our Privacy Policy Applies

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

This Privacy Policy describes the data we collect when you open an account, complete phone verification, sign in from a mobile browser, or ask us to check a DANA, OVO, GoPay or QRIS transaction. We may record account identifiers, contact details, device signals, login events, wallet

1
references and support messages so we can confirm the right account and investigate a status question. We do not treat a payment reference as permission to use unrelated account data. We use these records for account access, fraud checks, support handling, legal duties and service security.
2
Retention depends on the purpose of the record and any applicable legal requirement. Where local law permits, you can ask what personal data we hold, request a correction, or ask about deletion after account closure. Access and eligibility depends on local law; our policy does not
3
change that requirement.

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

POLICY HELP ROUTES

Get Help With Privacy Requests

A clear contact path helps when your account data does not match your wallet record or when you want to ask about this Privacy Policy.

Account data request Use the account support path to ask for a copy of the personal data linked to your login. We may verify your phone before sending details to the account holder.

Wallet record question For a DANA, OVO, GoPay or QRIS record, share the date, amount reference and account identifier through support. Do not send a wallet PIN or full security code.

Correction or deletion Tell us which account detail needs changing or which data request you are making. We can explain retention steps and any legal reason a record must remain stored.

DATA HANDLING PRACTICE

How We Manage Privacy Day To Day

Our privacy process follows the account actions you can recognise: phone verification before account access, a mobile browser session, wallet status checks and support messages.

Collected account data

We use your account identifier, phone details, login events and transaction references to connect a request with the correct account. We collect only details needed for access, support and required checks.

Cookies and device signals

Cookies can keep a mobile browser session working and help us detect unusual sign-in behaviour. Device signals may include browser type, time and security events rather than wallet PIN data.

Account security

Phone verification comes before account access, while login and cashier events help us spot activity that needs checking. We may pause a request until account ownership is confirmed.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status. We do not ask you to place a wallet PIN inside a support message.

Retention periods

We keep account and transaction records for the period needed to provide support, resolve disputes, protect the service and meet legal duties. The period can vary by record type.

Changing your details

Ask support to correct a phone number, account name or other personal detail connected with your account. We first confirm ownership, then explain the change or removal path.

Privacy Policy Questions for Indonesia

These answers cover the Privacy Policy questions we expect before you open an account or send a data request. Each answer points back to a practical account step, payment record or contact route.

It covers account details, phone verification, login events, device signals, cookies, support messages and DANA, OVO, GoPay or QRIS references used with your account.

We use phone verification to confirm account ownership before access or a data request. It helps prevent another person from receiving account details or changing your contact record.

Yes. The Privacy Policy covers cookies and security signals from the mobile browser you use to sign in, including browser type, session events and unusual login activity.

We may keep account-linked references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us check status without asking for your wallet PIN.

Use the account support route and state that you want a copy of your personal data. Include your account identifier, then complete the ownership check before we respond.

You can ask us to correct inaccurate account details or discuss removal after closure where local law permits. Some transaction or security records may remain for legal or dispute needs.

Yes, access and eligibility depends on local law. Our Privacy Policy explains data handling, but it does not override Indonesian requirements or any rule applying to your location.

cincin303 Privacy Policy for Your Account Data

Get Help With Privacy Requests

How We Manage Privacy Day To Day

Collected account data

Cookies and device signals

Account security

Payment references

Retention periods

Changing your details

Privacy Policy Questions for Indonesia

01 What does the cincin303 Privacy Policy cover?

02 Why does cincin303 need phone verification?

03 Does the Privacy Policy cover mobile browser data?

04 What payment data does cincin303 keep?

05 How can I request a copy of my data?

06 Can I ask cincin303 to correct or remove data?

07 Does access under this Privacy Policy depend on location?

Related Pages