Reference

Open with ratutogel Privacy Policy

Our ratutogel Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS for account transactions.

Account dataWallet recordsCookie choicesAccess requests
ratutogel Open with ratutogel Privacy Policy
CONTACT PATHS

Contact us about your account data

A clear support route helps you ask about the Privacy Policy without posting personal details in a public message. Sign in first when you can, then use the support path connected to your account or cashier record. Include the relevant payment reference, device type or request category, but never send a password or one-time code. We use the details you provide to locate the right record and respond to the specific privacy question.

Team online

Account data request

Use the account support path to ask what personal details are connected with your profile. We may ask you to confirm account information before discussing it, so a request reaches the correct person rather than exposing records to someone else.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, include the transaction reference shown in your account. Our support path can check whether a receipt or status record is attached, while keeping your wallet PIN and login credentials out of the conversation.

Access and correction

If a detail is wrong or you cannot reach the privacy page, contact us through the signed-in support route or the cashier-linked help path. Access depends on local law, and we may verify your account before changing or releasing personal data.

DATA PRACTICE

Protect your login and wallet records

Privacy is handled through the same account steps you already use: sign in, check the relevant record, and send a focused request through support.

What we collect

We may collect your account details, contact information, verification responses, sign-in events, browser or device signals, support messages and transaction references. We collect only what helps provide account access, confirm a request, check a payment record or protect the account.

Cookies and sessions

Cookies can keep a session active, remember selected settings and help us understand whether a page loaded correctly. Your phone and desktop may show different cookie behaviour. You can manage browser cookie settings, though changing them may affect sign-in or policy-page access.

Account security

We use sign-in checks, account verification and activity records to reduce unauthorised access. If a login or wallet status looks unusual, we may pause a request until account details are confirmed. Never share your password, wallet PIN or one-time code with support.

Payment matching

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference helps us connect a payment status with the correct account. We use the reference and status needed for reconciliation, rather than asking support to handle your private wallet credentials.

Retention choices

We keep personal and transaction records only as long as needed for account operations, security checks, dispute handling or legal duties. Retention can vary by record type. Where local law permits, we remove or restrict material that no longer has a valid operational need.

Change requests

You can ask us to access, correct or clarify personal data through the account support path. State which detail needs attention and provide enough account context for verification. Some records may remain when retention is required by law or needed to resolve a dispute.

Find answers about Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or sending a payment-status request. We keep the wording practical: what is collected, why wallet references appear, how cookies behave on a phone, and which account path to use for access or correction. If your case is unusual, send the details through support rather than sharing them in an open message.

The ratutogel Privacy Policy covers account and contact details, verification information, sign-in activity, device signals, cookies, support messages and payment references. It also explains why we use those records, how long they may be retained, and how you can request access or correction.

We record the payment status and reference needed to match DANA or QRIS activity with your account. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. We do not need your wallet PIN or password for that matching step.

Yes. The Privacy Policy covers cookies and session signals used for sign-in continuity, settings and page performance. A phone browser can behave differently from a desktop browser. You can adjust cookie controls in your browser, although some account functions may then require another sign-in.

Sign in and use the account support route to request access to personal data connected with your profile. Describe the record you need, such as contact details or a payment reference. We may verify account ownership first, and access depends on local law.

You can ask us to correct or clarify an account detail through the signed-in support path. Identify the incorrect field and explain the change needed. We may retain an earlier transaction or security record where local law permits or where it is needed for a dispute.

Retention depends on the record and its purpose. Payment references may remain for reconciliation, security review, dispute handling or legal duties. When that need ends, we remove or restrict the material where local law permits. Support can explain the request path for a specific record.

Use the support route connected to your account, especially when your question involves a login, DANA, OVO, GoPay, QRIS or bank transfer reference. Share the request category and relevant reference, but not your password or wallet PIN. We will direct the Privacy Policy concern to the appropriate account process.