Reference

republik62 Privacy Policy, Made Clear

Our Privacy Policy explains what we collect when you open a republik62 account, why a phone verification step may appear, and how you can ask about your records.

Account dataWallet recordsCookie choicesPrivacy requests
republik62 republik62 Privacy Policy, Made Clear
REQUEST HELP DIRECTLY

Get Privacy Help Beside Your Account

A clear support route matters when you want to ask about personal data rather than a wallet status. From your account area, use the support link beside the cashier path and describe the request in plain English, including the phone number or email connected with your account. We use those details to locate the right record, while you should avoid sending a password or full payment credentials. The same route can help when a privacy request follows a DANA receipt, QRIS reference or account-access question.

Team online

Account privacy request

Use the support link beside your account and state whether you want access, correction or clarification. Include the contact detail attached to your account so we can distinguish your request from another account record.

Wallet record question

If your question concerns DANA, OVO, GoPay or QRIS activity, provide the relevant date and reference while hiding sensitive credentials. We can then check the payment record without asking you to share a wallet password.

Access concern

When a phone verification step or account sign-in raises a privacy concern, explain what appeared on your device. We will use the account support path to identify the issue and respond about the related data use.

YOUR DATA CONTROLS

Know What We Keep And Why

We handle privacy as part of the account path, not as a separate promise hidden from you. The policy describes contact details, verification records, payment references, device signals and cookies in practical…

Account details

We use the contact details you enter to create and maintain your account, including the phone verification step before access. Check that your phone number is current, because an incorrect detail can prevent us from matching a privacy request to your account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount status and time record. These details help us trace a cashier event without storing your wallet password or requesting full card credentials.

Cookies and device use

Cookies and device signals can help keep your session connected as you move between the mobile lobby and desktop account path. Your browser settings provide a way to manage cookies, although changing them may affect sign-in or saved preferences.

Account security

We treat phone verification and sign-in details as account-protection data. Do not share your password, one-time code or wallet credentials with support. If a sign-in looks unfamiliar, use the account support link and describe the device activity.

Retention questions

The Privacy Policy explains why certain account, verification and payment records may remain after an action is completed. Retention can depend on the record and applicable rules, so ask us which category applies instead of assuming every record follows one period.

Changes to your data

You can ask us to correct inaccurate contact details or clarify how a record is used. Send the request through the account support route, identify the relevant account step, and include only enough detail for us to verify ownership.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data behind phone verification, wallet references, cookies, access requests and account changes. If your situation is not listed, use the support link beside the cashier path and describe the exact screen, payment reference or account step involved. We will keep the request focused on the relevant privacy record.

It covers account details, phone verification, cookies, device signals, payment references and privacy requests connected with your account. It also explains why some records are retained and how to contact us when you want clarification, correction or access to data.

Phone verification helps connect the account to the contact detail you provided before account access. It also helps us identify the correct record when you ask about privacy. Keep your code private, and contact support if the verification screen does not match your action.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS actions can create payment references, status details and timestamps. Bank transfer and virtual account steps can create similar records. These references help us check a cashier event without requesting your wallet password.

Cookies can keep your session connected and remember selected settings when you use a mobile browser or desktop. You can manage them through browser controls. If you block certain cookies, sign-in or account preferences may not work as expected.

Use the account support link beside the cashier path and state whether you want access or a correction. Include the phone number or email attached to the account, but never send your password, one-time code or full wallet credentials.

The retention period can differ between contact details, verification records, payment references and security logs. Our Privacy Policy explains the reason for keeping each category. Ask support about the specific record and we will point you to the applicable policy basis.

You can read this Privacy Policy from the republik62 site before opening an account. Account access and eligibility depends on local law or where local law permits. If your location or account status creates uncertainty, ask support before submitting personal details.