Reference

Open Privacy Policy Before Account Access

redmitotolink Privacy Policy explains how we handle the account details, wallet references and device signals connected with your access.

Account dataWallet referencesCookie choicesContact requests
redmitotolink Open Privacy Policy Before Account Access
ACCOUNT HELP ROUTE

Browse Privacy Support From Your Account

A clear contact path matters when you have a question about the Privacy Policy or a data request. Sign in, open the account help area and include the phone number or email linked to your account, plus the subject of your request. We use those details to locate the correct record without asking you to send wallet passwords, one-time codes or full payment credentials. If you are in Surabaya or elsewhere in Indonesia, the same account path applies where local law permits.

Team online

Data request

Ask us which account, device or payment-reference data is connected with your profile. Include the email or phone number used during verification so we can check identity before discussing private records.

Correction path

If your phone number, email or account detail is incorrect, contact us through the signed-in help area. We may request a verification step before changing data that controls access to the account.

Wallet question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, send the transaction date and status shown in your account. Never include a wallet password or one-time security code.

DATA HANDLING

Switch Through Privacy Controls With Clarity

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account records

When you open an account, we record the details needed to create and maintain that profile. Phone verification helps connect the request to you before account access, while incomplete details may prevent us from completing the requested change.

Device signals

The mobile and desktop browser used for sign-in can provide device and session signals. We use them to recognise unusual access and help investigate login problems, not to request your device password or private wallet code.

Cookie settings

Cookies can remember a session, language choice or account-area setting so you do not repeat the same step. You can manage cookies through your browser controls, although limiting them may affect sign-in or policy access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may appear as reference details or status events. We use these records to connect a wallet question with the right account without asking for secret credentials.

Retention checks

We retain account, security and support records for the period needed for their stated purpose or applicable legal duties. Ask through the signed-in help area if you want us to explain why a particular record remains stored.

Your request

You can ask what data we hold, request a correction, ask about deletion or raise a concern about handling. We may verify your identity first, and the response or available action depends on local law.

Ask About redmitotolink Privacy Policy

These Privacy Policy answers focus on the account and wallet questions you may have before opening access. We keep the wording tied to actual steps, from phone verification and cookie controls to DANA or QRIS status checks. If your situation is not covered, use the signed-in account help path and describe the record or request clearly. Eligibility and available actions depend on local law.

The redmitotolink Privacy Policy covers account details, phone verification, login and device signals, cookies, support records and payment references. It explains why we use each category, how retention works and how you can ask about access, correction or deletion where local law permits.

Yes. The Privacy Policy covers payment references and status records connected with DANA, OVO, GoPay and QRIS. We can use a reference to trace an account question, but you should not send a wallet password, one-time code or full private credential through support.

We may collect the account details needed for registration, the phone number used for verification, sign-in records, device signals and support messages. The exact fields can depend on the account step and local requirements. We explain the relevant use through this Privacy Policy.

Sign in and use the account help area to ask what data is connected with your profile or to request a correction. State the phone number or email used for verification and describe the change. We may confirm your identity before sharing or editing private records.

On a mobile browser, cookies may keep your session and selected account settings available between steps. Browser controls let you limit or remove them. If you block required cookies, phone verification, sign-in or access to the Privacy Policy area may not work as expected.

We keep account, security, payment-reference and support records only for the stated operational purpose or as required by applicable legal duties. Retention can differ by record type. You can ask us to explain a record's retention through the signed-in help path.

You can submit a deletion request through the account help area and identify the profile concerned. We will assess the request under the Privacy Policy and local requirements. Some records may need to remain available for security, dispute handling or legal duties where local law permits.