Reference

rezekihoki Privacy Policy For Indonesia

Our Privacy Policy explains how rezekihoki collects, uses and protects the details connected with your account, wallet activity and mobile access.

Account dataWallet recordsMobile browsingPolicy requests
rezekihoki rezekihoki Privacy Policy For Indonesia
HELP WITH DATA

Contact Us About Privacy Requests

A clear support route helps you act on this Privacy Policy without searching through the lobby.

Account access request Use the account support path when you need a copy of personal data linked…
Wallet record question For a DANA, OVO, GoPay or QRIS record, share the transaction reference and approximate…
Correction or deletion Tell us which personal detail needs correction or which request you want assessed.
DATA HANDLING

How We Apply This Privacy Policy

We keep the policy practical by connecting each data use to an account action you can recognise.

Account records

We use your account details to create access, complete phone verification and respond to account requests.

Payment references

DANA, OVO, GoPay and QRIS activity can create references, timestamps and status information in our records.

Device and browser data

When you sign in from a mobile browser, we may receive device type, browser settings, IP address and security events.

Cookies and similar tools

Cookies can keep a session active, remember selected settings and help us understand whether an account page loads correctly.

Retention periods

We keep personal data only for as long as needed for the purpose collected, account administration, security checks or legal…

Policy changes

If we change how personal data is handled, we update this Privacy Policy and show the revised date or notice…

Privacy Policy Questions For Your Account

These Privacy Policy answers focus on the searches we hear before account access: what data is collected, why wallet references appear, how device records are used and how to request a change. We keep the answers tied to the actual account steps, from phone verification to a QRIS receipt check. If your situation is different, contact support with a safe description of the issue.

The rezekihoki Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, payment references and security records. It explains why we use each category, how retention works and how you can request access, correction or another privacy action.

We use your phone number to create and protect the account access path, including the verification step before account details are discussed. It can also help support locate the correct account. We do not ask you to send a password or wallet PIN in a support message.

Yes. The Privacy Policy includes references created when you use DANA or QRIS, such as a transaction identifier, timestamp and payment status. These records help us reconcile a request and answer a receipt question; they are not a request for your wallet PIN.

A mobile browser session may provide device type, browser settings, IP address and security events. We use these signals to keep account access secure, investigate unusual sign-ins and resolve loading issues. You can manage cookies in your browser, though sign-in may be affected.

Contact account support and identify the detail you believe is inaccurate, such as a phone verification record or contact field. We may confirm account ownership first, then assess the request against security and legal record duties before explaining the available correction.

You can submit a deletion request through the support path named in this Privacy Policy. We assess whether the data is still needed for account security, payment reconciliation or a legal duty. Where local law permits, we remove or de-identify eligible records and explain any exception.

Retention depends on why the record exists. A support message may be kept for account assistance, while a DANA, GoPay, bank transfer or virtual account reference may remain for reconciliation and lawful record duties. The period can therefore differ by data category and request.