Reference

ratugacor Privacy Policy for Wallet Access

Our Privacy Policy explains how ratugacor handles the details connected with your account, wallet status and device access.

Account clarityWallet contextDevice awarenessRequest access
ratugacor ratugacor Privacy Policy for Wallet Access
REQUEST ROUTES

Account Messages For Privacy Requests

You can raise a Privacy Policy question from the support route linked inside your account area, so we can connect your request with the right account record. Include the email or phone detail attached to your account, the device path you used and the subject of your request. We may ask for an account step to confirm that the request comes from you.

Team online

Account contact

Open the support contact path after login and state whether you want a copy, correction or deletion request under this Privacy Policy. We will use the account details you provide to locate the right record.

Wallet receipt

If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, attach the relevant receipt or status detail. This helps us separate your payment record from another account before responding.

Access concern

For an unfamiliar login or device event, tell us the approximate time and whether you were using a mobile browser or desktop. We can then review the account-security record connected with that session.

DATA PRACTICE

Cookies And Mobile Account Security

We keep this policy practical by linking each data purpose to an account action you recognise. Login details support account access, payment references support reconciliation, and support messages let us answer a…

Data collected

We may receive your account contact details, verification records, login timestamps, device or browser signals, support correspondence and payment references. The exact data depends on the account step you complete and the service action you request.

Purpose of use

We use account data to authenticate access, connect wallet status with the correct account, investigate unusual sessions and respond to Privacy Policy requests. We do not need every detail for every action.

Cookie settings

Cookies or similar browser storage can remember session state and help us identify whether a login continues on mobile or desktop. You can manage browser storage through your device or browser settings.

Security checks

A phone verification step and device-session review can help protect account access. If a login appears unfamiliar, we may ask you to confirm account details before changing information or discussing wallet records.

Retention period

We keep records only while they support account operation, payment reconciliation, security review, dispute handling or a legal requirement. Retention can differ by record type and the reason that record was created.

Change request

Use the support contact path inside your account to ask for correction, access or another permitted change. Tell us which record is concerned, and we may verify your identity before acting.

Privacy Policy Questions For Indonesia Accounts

These Privacy Policy answers cover the account, wallet, device and contact questions you may have before opening an account. If your situation is not listed, use the account support route and describe the specific record or access event you want us to check.

It covers account details, phone verification, login and device events, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS or bank transfer activity.

We use payment references and status details needed to reconcile an account action. The Privacy Policy does not require us to publish your wallet balance, and access to records is limited to the relevant purpose.

After login, open the support contact path and ask for an account-data request. Include your attached phone or email detail; we may complete an account verification step before releasing records.

Yes, you can ask us to correct an inaccurate account, contact or device record through support. Describe the change clearly, and we may request verification so another person cannot alter your account.

Cookies or similar storage can keep your session connected and help distinguish mobile-browser access from desktop access. You can review or remove browser storage through your phone or computer settings.

Retention depends on the record and its purpose, such as account access, payment reconciliation, security review, dispute handling or legal duties. We remove or manage records when the applicable need ends.

Use the support route inside your account and provide the approximate time, device type and contact detail attached to the account. We can then examine the related session and explain the next step.