Reference

ori33 Privacy Policy for Your Account

Our Privacy Policy shows what we collect when you open an account, complete phone verification, and use DANA or QRIS.

Account dataWallet recordsYour privacy choices
ori33 ori33 Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Through Your Account

A clear contact route matters when you want to ask what data we hold or why a wallet record appears. Start from the support link inside your signed-in account and include the account email, phone number, or payment reference concerned. We use those details to locate the right record without asking you to send a password or full wallet credentials.

Team online

Account support link

Use the support route inside your account for Privacy Policy questions, access requests, correction requests, or concerns about a phone verification record.

Payment reference

Include the DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference when asking us to trace a receipt or explain stored transaction data.

Access clarification

If a sign-in or wallet status is held for checking, contact support through the account path; we can explain the data step involved where local law permits.

DATA HANDLING

Your Data Choices Across ori33

We treat this policy as an account tool, not a page to skim once. The choices below explain how data handling connects with login, wallet checks, mobile browsing, and requests sent to…

Account details

We collect details you submit when opening an account, including contact information and phone verification data, so we can identify the account and respond to account-related requests.

Cookies and devices

Cookies and device signals can remember login state, support security checks, and keep the mobile path working. You can manage browser permissions, although some account functions may then need another check.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we keep references needed to match status, receipts, and account questions without requesting your wallet password.

Account security

We record sign-in events, verification steps, and selected device details to investigate unusual access. If you see activity you do not recognise, use the signed-in support path and describe the event.

Retention periods

We retain account, support, and transaction records only for the period needed for stated services, security checks, dispute handling, or legal duties; the exact period can depend on the record type.

Change requests

You can ask us to access, correct, or clarify personal data through account support. Include the relevant record and contact detail so we can verify the request before making a change.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we hear before an account is opened or a wallet is connected. We keep each response tied to a practical step: phone verification, a mobile login, a payment reference, a cookie setting, or a request sent through account support. Where access is discussed, the applicable rule depends on local law.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references, retention, disclosures, and the requests you can send about your personal data.

We do not ask for or store your wallet password through account support. We may retain a DANA or QRIS transaction reference and status so we can match a receipt with your account question.

Phone verification helps connect the correct contact detail with your account and supports access checks. We record the verification result and related event, then handle it under the Privacy Policy.

Yes. Send an access request through the support link inside your account, identify the contact detail involved, and complete any checks needed to confirm that the request is yours.

Use account support and describe the field that needs correction, such as an email or phone detail. We may ask for verification before changing the record linked to your account.

Cookies can keep your login state, remember selected settings, and support security checks on the mobile path. Browser controls let you manage them, but restricted cookies may interrupt account access.

Account access and eligibility depend on local law. Read the current Privacy Policy, use the account path only where local law permits, and contact support if you need clarification about a data-related access step.