Reference

Privacy Policy for totomenanglink Accounts

Our Privacy Policy explains how we collect, use and protect the details connected with your totomenanglink account, including wallet records from DANA and QRIS.

Account dataDANA and QRIS recordsCookie choicesPhone verification
totomenanglink Privacy Policy for totomenanglink Accounts
CONTACT ROUTES

Privacy Questions Reach Our Support Path

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages. We direct account questions to the support path shown after login, where you can identify the account email or phone number involved. For wallet records, include the DANA, OVO, GoPay or QRIS reference and the date shown in your cashier history. We use those details to locate the correct record, while access remains subject to local law.

Team online

Account privacy request

Use the account support route to ask what personal details are linked to your login, request a correction or ask how your information is being used. Include your verified phone number so we can match the request without asking for your password.

Wallet record check

If a DANA, OVO, GoPay or QRIS status appears incorrectly, send the transaction reference from your account history. We compare that reference with the recorded status and explain what can be corrected under this Privacy Policy.

Security concern

For an unfamiliar login, device session or account change, contact us through the visible support route and change your password first. We review the event against phone verification and login records before discussing account details.

DATA PRACTICES

How We Handle Your Privacy Requests

We designed this Privacy Policy around the account events we can actually check: login, phone verification, wallet status, cookie consent and support contact.

Data we receive

We may receive your account name, phone number, contact details and verification status when you open access. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account help us match a status without requesting your wallet credentials.

Cookies on your device

Cookies can keep a session active, remember a language or region choice and help us detect repeated login failures. On a phone or desktop browser, you can adjust cookie settings through the browser controls and still contact us about the choice.

Account security checks

Phone verification, login timestamps and device signals help us check whether an account request comes from the right person. We do not ask you to send a password through support, and we may ask for a reference rather than sensitive wallet credentials.

Retention of records

We keep account, payment-status and security records for the period needed to operate the service, investigate disputes or meet applicable legal duties. When a record is no longer needed for those purposes, our handling follows the retention rules that apply.

Requesting a correction

You can ask us to correct an inaccurate phone number, contact detail or transaction reference through the support path shown in your account. Describe the change clearly; we may verify your account before editing a record or sharing its contents.

Requesting access

To ask what personal data we hold, mention your account identifier and the category you want, such as login, cookie or wallet-status records. We assess the request under this Privacy Policy and where local law permits, explain the available response.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the searches we expect you to make before opening or using an account. We explain the records connected with login, payments, devices and selected lobby activity, along with the practical route for asking us to check or change something. Where a right or response depends on local law, we will assess the request against the rules that apply to you.

It covers account details, phone verification, login and device records, cookie settings, support messages and payment-status references. That includes activity linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks. It also explains retention, security and how to request access or correction.

Phone verification helps us connect an account request with the person controlling the registered number and helps protect account changes. We use the verification status for access and security checks, not as permission to request your wallet password. Any access decision depends on local law.

Yes. We may store a transaction reference, amount status and time needed to match a DANA or QRIS update with your account. Similar records can apply to OVO, GoPay, bank transfer and virtual account activity. We use these details for status checks and account support.

When you sign in from a phone, tablet or desktop, technical records may include browser type, device signals, login time and security events. These details help us identify unusual access and keep a session working. They are handled for service, security and legal purposes described in the Privacy Policy.

Contact us through the support route visible in your account and name the detail that needs correction, such as a phone number or contact record. We may verify your identity before making a change. Requests are assessed under the Privacy Policy and where local law permits.

We retain account, payment-status, support and security records only while they are needed for service operation, dispute handling, security checks or applicable legal duties. The period can differ by record type and local requirements. Once the purpose ends, handling follows the relevant retention process.

You can contact us to ask about deletion or restriction of personal data, and we will assess the request against the rules that apply to your account. Some records may need to remain for security, dispute or legal reasons. Access and eligibility depend on local law.