Reference

jdtoto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from an Android or iPhone browser, and use DANA, OVO, GoPay or QRIS.

Clear data purposesCookie choicesWallet record controlsAccount contact path
jdtoto jdtoto Privacy Policy for Your Account
HELP WITH YOUR DATA

Get Privacy Policy Help Without Guesswork

A clear contact path matters when a privacy question appears beside an account or wallet issue.

Data access request Ask which account details and sign-in records we hold by sending your registered contact detail through our support route. We may ask for account verification before releasing personal data.
Correction request If your phone detail, account name or payment reference appears incorrect, tell us the exact field and the account step where it appeared. We will assess the requested change.
Wallet privacy query For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date, not your wallet password or PIN. This helps us separate payment matching from sensitive credentials.
HOW WE HANDLE RECORDS

Keep Account Data Clear And Protected

Privacy work is practical: we separate account identity, device signals, cookie preferences and payment references so each record has a clear reason to exist.

Data collection

We collect details you enter during account creation, verification responses, browser signals and transaction references. We use each category for the stated account, security, support or payment-matching purpose.

Cookie controls

Cookies can keep a sign-in session connected to your browser and remember selected settings. You can adjust browser cookie controls, though switching them off may affect account access or saved preferences.

Account security

Phone verification helps connect the account to the person requesting access. Never send a password, wallet PIN or one-time code in a privacy message or support request.

Retention practice

We keep account, security and payment-reference records only for the period needed for their stated purpose, account support and applicable legal duties. Retention can differ by record type.

Correction path

You can ask us to correct inaccurate contact or account details. Include the old value, the requested value and enough account context for us to verify the request safely.

Policy contact

Use the privacy contact path when you want access, correction, deletion assessment or a cookie explanation. We may verify your identity before discussing records connected with your account.

Find Answers Before Opening An Account

These Privacy Policy answers focus on the searches you may make before creating an account or asking about a wallet record. If your situation is not covered, contact us with the account step, device path or payment reference involved, while keeping passwords and wallet PINs private.

The jdtoto Privacy Policy covers account details, phone verification, browser and device records, cookies, payment references, support requests, retention and requests to access or correct eligible personal data.

We use payment references to match account activity with DANA, OVO, GoPay or QRIS transactions. Do not send a wallet PIN or password to us; those credentials remain with you and the relevant provider.

Send a privacy request through our support route using your registered contact detail and the account step involved. We may verify your identity before explaining or releasing records connected with your account.

Yes, you can ask us to assess a correction for an inaccurate name, phone detail or account record. State the field, the correct value and enough context for safe account verification.

Cookies can connect your browser session to sign-in and remember selected settings. If you block them on an Android or iPhone browser, some account or preference functions may not work as expected.

Retention depends on the record type and the reason it is needed, including account support, security, payment matching and applicable legal duties. Ask us to explain the period for a specific reference.

Use our privacy contact path for access, correction, deletion assessment or cookie questions. Include your account contact detail and request purpose, and avoid sharing passwords, wallet PINs or one-time codes.