Reference

cordoba99: Privacy Policy for DANA and QRIS Accounts

Our Privacy Policy explains how cordoba99 handles the details connected to your account, device, wallet status and support requests.

Clear data purposesWallet checks explainedPolicy access on mobileAccount contact path
cordoba99 cordoba99: Privacy Policy for DANA and QRIS Accounts
CONTACT ROUTES

Get Policy Help Beside Cashier Status

A direct support route helps when a Privacy Policy question appears beside a login or wallet-status issue.

Policy support form Ask about data use, cookies, correction or deletion through the support form inside your account path. Add only the details needed to identify your request and avoid sending wallet passwords.
Wallet status check For DANA, OVO, GoPay or QRIS questions, attach the payment receipt reference rather than wallet credentials. We can compare the account record with the cashier status and explain the next policy step.
Account access route If phone verification blocks access, use the account help route linked beside login. Tell us whether you are on Android, iPhone or desktop so we can separate device trouble from a data request.
DATA PRACTICES

Cookies, Devices, and Dragon Tiger Access

Privacy choices should remain practical when you move from a phone to a desktop account session.

Account details

We use the name, contact detail and phone-verification result you submit to create and protect your account. Keeping these details accurate helps us answer access requests without confusing one account with another.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event to your account. We ask for transaction evidence when a status question requires a precise check.

Cookies and sessions

Cookies can keep a chosen setting and help us recognise an active session. Our Privacy Policy explains their purpose, while your browser settings provide a way to remove or restrict them.

Device signals

Browser type, device pathway and security events may be recorded to detect unusual access. We use these signals to protect the account, not to request your wallet password or expose private credentials.

Retention approach

We retain account and payment records only for the period needed for account administration, security, dispute handling and applicable legal duties. The policy explains the reason for keeping each category.

Changes and requests

You can ask us to correct account details, explain a data use, provide an available copy or remove eligible information through support. We may verify account ownership before making a change.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the searches we hear most often before account access. Each response points you toward a practical step, from checking cookies on a mobile browser to sending a correction request through the account support path.

It covers account details, phone verification, device and session records, cookies, payment references, support requests, security checks and the reasons we retain or remove those records.

Phone verification helps connect account access to the contact detail you supplied and supports security checks. We use the result for account protection and access handling, not as a request for wallet credentials.

Yes. It explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match a payment event with your account and answer a receipt question.

Open the account support form and request a correction, naming the affected field. Include the contact detail linked to your account; we may verify ownership before changing the record.

You can send a data access request through support. Tell us which account contact detail identifies you and what category you want clarified, such as cookies, device signals or wallet references.

Cookies may preserve settings and help maintain a browser session. If you remove them, login or policy preferences may need to be entered again; your browser controls can restrict their use.

Read the policy beside the account access path, then contact support with your region and question. Eligibility depends on local law, so we explain the route shown for your location.