Reference

justoto Privacy Policy For Your Account

The justoto Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, use DANA or QRIS, and contact our support…

DANA recordsQRIS checksCookie choicesAccount requests
justoto justoto Privacy Policy For Your Account
REQUEST ROUTES

Get Privacy Policy Help Before Account Access

A clear request route helps when you need to ask about a record, cookie choice, or wallet reference. Contact our account support path with the email or phone detail linked to your account, and include the date, device path, and payment rail involved. For example, a QRIS receipt and sign-in timestamp help us locate the right event without asking you to send unrelated personal material. We handle requests about the Privacy Policy as account matters, with extra checks before changing or disclosing information.

Team online

Account records

Ask us what account details we hold and why they are used. Include your registered contact detail and the account step involved, such as phone verification or a sign-in attempt, so we can match the request to the correct record.

Wallet references

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, send the transaction reference and date rather than a wallet password or full secret. We use the reference to check payment status and explain the related data entry.

Policy changes

If you want a correction, deletion request, or explanation of a cookie choice, use our support route and state the exact action you want. We may ask for account confirmation before changing records, especially when the request affects access to your account.

DATA CONTROL POINTS

Six Privacy Policy Checks We Keep Clear

Privacy Policy questions often concern small operational details, so we explain them in the same terms used in your account flow.

Data collection

We collect details you enter for account creation and verification, along with technical signals such as browser type, device path, login time, and security events. These records help us provide account access and investigate unusual activity without treating every page visit as a separate identity.

Cookie choices

Cookies can remember a selected setting, keep an account step working, or show us how a page is used. Your browser controls can remove or restrict them, although some account functions may then require another sign-in or may not display the same way.

Account security

We use sign-in records, phone verification steps, and account activity checks to reduce unauthorised access. We will not ask for your password or one-time code in a policy request. If a login stalls, tell us the device and time so we can check the event safely.

Wallet matching

A payment reference lets us connect a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account event with the right account status. We keep the operational details needed for reconciliation and support, while asking you to hide private credentials from receipts or screenshots.

Retention period

We retain account, security, and transaction records for as long as needed for the stated service purpose, dispute handling, security checks, and applicable legal duties. When a record is no longer needed, we remove it, anonymise it, or restrict it according to the relevant rule.

Change requests

You can ask us to correct account data, explain its use, or request removal where the applicable rule allows it. Send the request through support with your registered contact detail; we confirm identity first and explain any record we must retain for security or legal reasons.

Privacy Policy Questions About justoto

These Privacy Policy answers address the questions we expect before you open an account or connect an Indonesian wallet. They explain what you can ask us to do, which records support account and payment checks, and how a request moves through verification. If your situation is not covered, send the relevant account step and payment reference through our support path, without sharing a password or one-time code. Access and eligibility remain subject to local law.

The justoto Privacy Policy covers account details, phone verification, device and browser events, cookies, support requests, and payment references. It explains why we use each category, how we protect account access, how long records may remain, and how you can ask about correction or removal where applicable.

DANA and QRIS appear because a wallet action creates a reference and status that must be matched to your account. We use those operational details to check whether a deposit step was received or needs attention. Do not send wallet passwords, one-time codes, or hidden credentials to support.

You can contact us through the account support route and ask which personal details we hold. Include the registered phone or email and describe the account step, such as registration or phone verification. We confirm identity before responding, and some records may remain restricted for security or legal reasons.

The Privacy Policy allows cookies to remember settings, keep account steps working, and help us understand page activity. Your mobile browser can block or delete them. If you do, sign-in preferences may not remain saved and some pages may ask you to repeat an account step.

Send a correction request through support using the contact detail connected to your account and identify the field that is wrong. We verify the request before changing it. If the field relates to a DANA, OVO, GoPay, or QRIS record, include its reference so the update is matched correctly.

We keep records for the period needed for account operation, security investigations, payment reconciliation, dispute handling, and applicable legal duties. Retention differs by record type. When a record is no longer needed, we remove, anonymise, or restrict it under the relevant rule.

Yes. Any account access or eligibility decision depends on local law, and our Privacy Policy is applied where local law permits. If a local rule affects your request or a record we must retain, we explain that limitation through the account support path rather than asking for unnecessary personal details.