Reference

prediksi77 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS payment records.

Account dataWallet recordsCookie choicesSecurity requests
prediksi77 prediksi77 Privacy Policy for Your Account
CONTACT DATA CARE

Check Your Privacy Contact Path

A clear contact route helps you resolve a data question without repeating your account story. When login, phone verification or a wallet status stalls, send the relevant account identifier and payment reference…

Account data request Ask us to access, correct or clarify personal details connected with your account. Include the phone number used during account setup so we can locate the right record.
Payment record check For DANA, OVO, GoPay, QRIS or bank transfer questions, provide the transaction reference rather than a wallet password. We use that reference to trace status safely.
Security concern If a sign-in, device change or phone verification looks unfamiliar, contact us promptly. We may pause a request while confirming ownership and protecting the account.
HOW DATA IS HANDLED

Explore prediksi77 Data Controls

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

Account details

We collect details needed to create and protect your account, including contact data and phone verification results. You can ask us to correct an inaccurate entry through the privacy contact path.

Device and login records

Mobile and desktop sign-ins may create time, browser and device records. We compare these signals when an unfamiliar device attempts account access or a sensitive request.

Cookie choices

Cookies can remember session settings and help us understand whether a page request belongs to your active account. Your browser controls can limit cookies, though some account functions may change.

Wallet references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity may produce reference numbers and status details. We do not ask you to provide a wallet password in support messages.

Retention approach

We retain records only as long as needed for account security, dispute handling, service records or legal duties. When a record is no longer needed, our process removes or separates it.

Changes and contact

You may request a copy, correction or explanation of relevant personal data. We may verify ownership first, then respond through the contact route connected with your account details.

Browse Privacy Policy Answers

These questions cover the points Indonesian account holders usually raise before opening an account or sending a payment query. If your situation involves a different device, an unfamiliar sign-in or a wallet reference that does not match, contact us with the smallest useful set of details.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect an account request with the correct account holder and detect unusual access. We may request confirmation before changing details or discussing a sensitive payment record.

Yes. Send a data request through our support contact path with the phone number or account identifier used during setup. We may confirm ownership before providing, correcting or explaining relevant records.

We use DANA and QRIS references to match payment status with your account and investigate a receipt query. Please send the reference number, not a wallet password or private security code.

Cookies may retain session settings and support account continuity on a phone or desktop browser. You can adjust browser controls, but limiting necessary cookies may affect sign-in or policy access.

Retention depends on the record and its purpose, such as account security, dispute handling, service history or legal duties. We remove or separate records when the applicable need ends.

Contact us promptly with the account identifier, approximate sign-in time and device details if available. We may verify ownership and restrict a sensitive account request while checking the event.