Reference

turkitoto Privacy Policy For Your Account

turkitoto Privacy Policy explains how we collect, use and protect details connected with your account, device and payment activity in Indonesia.

Account dataDevice controlsPayment recordsCookie choices
turkitoto turkitoto Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help Near The Account Path

If you have a privacy question, we keep the request close to the same account path used for login and wallet status checks.

Account privacy request Use the account support path to ask what personal details we hold, why a login record was created, or how your contact information is used. Include the account identifier connected with the request, but never include your password, DANA PIN, OVO PIN or other wallet secret.
Payment record check For a DANA, GoPay, QRIS, bank transfer or virtual account question, provide the payment reference and approximate date so we can locate the relevant record. We use this route to separate a receipt-status query from a request to change personal data.
Access and device concern If your account opens differently on mobile and desktop, describe the device type, browser path and time of the event. We use those details to investigate access records while keeping your account credentials and wallet security codes out of the conversation.
DATA CONTROL ROOM

What We Do With Your Account Details

Privacy decisions affect more than a registration form, so our policy explains the working records behind account access and payment checks.

Account collection

When you create or verify an account, we may collect your name or chosen account label, contact detail, verification result and sign-in history. We use these fields to connect your access requests and prevent a privacy response from being sent to the wrong person.

Wallet references

A DANA, OVO, GoPay or QRIS activity can leave a reference, amount, currency and status connected with your account. Bank transfer and virtual account records follow the same purpose: matching a transaction without asking us to store your wallet password or banking login.

Cookie settings

Required cookies support sign-in and security functions, while other cookies may remember preferences or help us understand page performance. You can review available browser controls before opening the lobby, although blocking required cookies may interrupt account access.

Device protection

We may record browser type, operating system, IP-related signals and session timing when you use mobile or desktop access. These details help us spot unusual sign-ins and explain why your account path differs between a phone and a computer.

Retention choices

We keep personal data only while it supports account administration, payment reconciliation, security review or a legal requirement. When a retention period ends, we delete, anonymise or restrict the relevant record according to the purpose described in this Privacy Policy.

Change request

You can ask us to access, correct or delete eligible personal data, or object to a particular use where local law provides that right. We may request account verification first, then explain any limit that applies to payment, security or legal records.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account questions we expect before you create access or connect a local payment rail. We keep the explanation practical: what we collect, how device records work, what happens to DANA or QRIS references, and how you can contact us. If a request involves eligibility or access, the result depends on local law and the rules that apply to your location.

The Privacy Policy covers personal details, account verification, sign-in events, device signals, cookies, payment references and support messages connected with your use of the site. It also explains retention, security checks and requests to access, correct or remove eligible data where local law permits.

We may collect the details needed to create and verify your account, such as a contact detail, account identifier, verification result and sign-in history. Device and session signals can also be recorded to protect access. We do not ask for your DANA, OVO or bank login password.

Yes. The policy covers payment references, status, timing and account links created when you use DANA, OVO, GoPay or QRIS. Bank transfer and virtual account records are handled for matching and reconciliation. Wallet PINs and banking credentials should never be sent to our support path.

Contact us through the account support path and state whether you want access, correction or deletion of eligible data. Include your account identifier and the specific record involved. We may verify ownership before responding, and some security or payment records may have legal retention limits.

A phone or browser record helps us connect a session with your account, identify unusual sign-ins and investigate an access problem between mobile and desktop. We may use browser type, operating system, IP-related signals and session timing for security and support purposes.

We retain payment references only for the period needed to administer your account, reconcile DANA, QRIS, bank transfer or virtual account activity, investigate security matters or meet an applicable legal duty. After that purpose ends, we delete, anonymise or restrict the record.

Yes. Your privacy rights, account access and eligibility depend on local law. Where local law permits, you can ask about processing, request a correction or seek deletion of eligible data. We will explain the request path and any reason a record must remain restricted.