Reference

Open jostoto Privacy Policy Before Account Access

The jostoto Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
jostoto Open jostoto Privacy Policy Before Account Access
CONTACT THE TEAM

Ask About Privacy Policy From Your Account

A direct support route helps when a Privacy Policy question meets a practical account issue.

Account data request Ask us to locate or explain account records through the account support path. Include your linked phone number, but never send a password, verification code or wallet PIN.
Wallet status question If a DANA, OVO, GoPay or QRIS entry looks incorrect, share its reference and date. We can compare the payment record with the account activity held for that request.
Login access concern When a sign-in or phone verification step stalls, describe the device path and account email or phone detail. We use this context to check access without exposing private records.
DATA CONTROL POINTS

Explore Data Controls Across Your Devices

Your privacy choices should remain understandable whether you use a phone or desktop. We separate account identity, wallet references, device signals and browsing preferences so each request can be handled with the…

Data we receive

We may receive your phone number, verification details, sign-in events, device signals and support messages. Payment references from DANA or QRIS help us connect a transaction question with your account.

How we use it

We use account and device data to provide access, confirm phone verification, identify unusual sign-in patterns, answer support requests and reconcile wallet activity with the correct account.

Cookies on your device

Cookies can keep a session active and remember selected page settings. You can manage cookie permissions in your browser, although changing them may affect sign-in or saved preferences.

Account protection

We use phone verification and session signals to reduce mistaken or unauthorised access. Keep your password and verification code private, and contact account support if a sign-in looks unfamiliar.

Retention approach

We keep records for the period needed to operate the account, resolve payment or access questions, protect the service and meet applicable legal duties, then assess whether continued storage is needed.

Request a policy change

For a copy, correction or eligible removal request, contact us through account support with the record concerned. We may need to confirm account ownership before changing private data.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening access. We explain the practical route for data requests, device activity, cookies and transaction references, while keeping eligibility wording tied to local requirements. If your case is not covered, use the account support path and describe the exact record or sign-in step involved.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, wallet references and retention. It also explains how to request access, correction or eligible removal where local law permits.

We use your phone number to create and identify the account, complete phone verification and help resolve access questions. It can also help us match a support request without requesting your password.

Yes. The policy covers transaction references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account when those details are used to match payment status or answer an account question.

Device and session signals help us recognise sign-in patterns, protect account access and investigate an unfamiliar session. They can also explain why a phone and desktop show different active sessions.

You can ask through account support for a copy or explanation of eligible records. Provide the linked phone detail and describe the data needed; we may confirm ownership before responding.

Send a correction or eligible removal request through account support and identify the record concerned. We assess the request under applicable requirements, because retention may still be needed for security or legal duties.

Yes. Account access and any data request outcome depends on local law. We apply the policy where local law permits and explain any restriction affecting your specific request.

Related Pages

jostoto Indonesia MotoGP Betting About Us Prosperity Fortune Tree Account information