Reference

ojktoto Privacy Policy Made Clear

Our Privacy Policy explains what ojktoto collects when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice signalsPrivacy requests
ojktoto ojktoto Privacy Policy Made Clear
CONTACT ROUTES

Get Privacy Help Through Your Account

A clear contact path helps you ask about personal data without repeating your account story.

Account access If phone verification or sign-in fails, contact support from the account path shown on…
Wallet reference For a DANA, OVO, GoPay or QRIS question, send the payment reference and date…
Privacy request To ask for a copy, correction or removal where permitted, identify the account phone…
DATA PRACTICES

How ojktoto Handles Your Records

We separate the data needed to operate an account from signals used to protect a session.

Account security

Phone verification links access to the account step you started.

Cookie choices

Cookies can keep a sign-in session or remember a setting on your browser.

Payment records

We retain transaction references for matching receipts and status checks.

Device access

On mobile, the path from phone verification to the account area may create login and device events.

Retention period

We keep personal data for the account, security or payment purpose that requires it, then remove or restrict it when…

Data changes

You can request correction, a copy or clarification through the support contact displayed in your account.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or sending a payment reference. We keep each answer tied to a practical step, from phone verification and mobile access to DANA, OVO, GoPay and QRIS records. If your question is not covered, use the support contact displayed in your account.

It explains how we handle account details, phone verification, device signals, cookies, payment references and support messages. It also describes your choices to request access, correction or removal where local law permits.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references for matching, status checks and account support.

Device and browser signals help us recognise a sign-in path and investigate unusual account entry. On a mobile phone, these records can connect a phone verification event with the session that follows.

Use the support contact displayed inside your account and identify the linked phone number plus your request for a data copy. We may verify ownership before releasing account-related records.

Yes. Send a correction request through the displayed support path, naming the field that is wrong and the accurate detail. We review the request against the account record and local requirements.

We keep payment references only while they support reconciliation, security, support or a valid legal requirement. This can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference.

Account access and eligibility depends on local law. The Privacy Policy still explains our data practices for supported access, and you can ask support how a request applies to your account.