Reference

republik77 Privacy Policy For Your Account

republik77 Privacy Policy shows how we use the details needed for account access, wallet checks and support, from your phone verification to a DANA or QRIS receipt.

Clear data purposesWallet record handlingCookie choicesAccount contact path
republik77 republik77 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Help Beside The Cashier Path

A clear contact route matters when a privacy request and a wallet receipt meet.

Account privacy request Ask us to access, correct or restrict personal data through the account support route.
Wallet record query For a DANA, OVO, GoPay or QRIS receipt question, share the payment reference and…
Device access concern Tell us if a phone or browser session looks unfamiliar.
DATA HANDLING

What We Do With Your Privacy Choices

Privacy controls work best when each request has a defined account step. We separate identity checks from payment references, explain why cookies are used and keep security events available only as long…

Account details

We use your contact details to create and protect the account, complete clear phone verification before access and respond to requests about your stored records.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile account activity. We do not need your wallet PIN or banking password.

Cookies

Cookies can keep a session open, remember selected settings and support security checks. You can manage browser cookie controls, although some account steps may then require another login.

Device security

We may record browser type, device signals, login time and failed access events to identify unusual sessions. These checks help protect your account without exposing your activity publicly.

Retention periods

We keep account, payment and support records for operational, dispute and legal needs. When a record is no longer needed, we remove it or restrict further use.

Change requests

Contact us through the account support path to request correction, access or restriction. We verify your identity first, then explain the action available where local law permits.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. We keep the replies practical, including phone verification, payment references, cookies, device sessions and requests made through account support. If your situation is not covered, contact us with the smallest set of details needed to locate your record.

It covers account details, phone verification, payment references, cookies, device signals, support records and retention. It also explains how to request access or correction where local law permits.

Phone verification helps connect the account to the correct contact detail before access and support changes. We use it as an account check, not as permission to request your password.

Yes. We may store a DANA or QRIS reference, date and status to match a wallet event with your account. Send the reference for a query, never your wallet PIN.

You can request correction through the account support route. Include the contact detail linked to your profile, and we will verify your identity before changing the relevant record.

Cookies can maintain a login session, remember settings and support security checks. Browser controls let you manage them, but disabling cookies may require you to sign in again.

Retention depends on operational, dispute and legal needs. We remove or restrict records when they are no longer needed, subject to requirements that depend on local law.

Use the support contact inside your account and state whether you need access, correction or restriction. Add a payment reference only when needed, and do not include passwords.