Reference

Privacy Policy For Your minitoro Account

Our minitoro Privacy Policy explains what account details we collect, why we use them, and how you can request access or changes.

Account dataCookie choicesPayment recordsSecurity steps
minitoro Privacy Policy For Your minitoro Account
PRIVACY HELP PATH

Where To Ask About Your Privacy Policy

A clear contact route matters when you want to understand a record or change an account detail.

Account support form Use the support form connected to your account when you want to ask about stored contact details, phone verification, cookie choices or a request to access your personal data. Include the account email or verified phone path so we can locate the correct record.
Cashier privacy route If your question concerns a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, use the support route beside the cashier path. We can explain which payment record is attached to your account without asking you to resend a wallet PIN.
Device access request When a mobile or desktop session looks unfamiliar, contact account support through the signed-in help path and mention the device behaviour. We can review the access context, explain the security step and record your request to change or restrict account access.
DATA HANDLING

Your Data Path From Login To Retention

Privacy is handled through ordinary account actions rather than hidden steps. We connect phone verification, cookie settings, device sessions and payment references to the purpose for which they are needed.

Account details

We use details such as your contact information and verified phone path to create, secure and maintain your account. Before we discuss account-specific data, support may ask you to complete an identity check through the signed-in account path rather than relying on an unverified message.

Cookies and sessions

Cookies can keep a session available on your chosen device and help us identify unusual sign-in behaviour. Your browser controls can remove them, but doing so may require another login. We explain the effect of cookie changes when they affect account access or security checks.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are handled as payment references connected to an account action. We use the reference to reconcile status and receipts, not to request your wallet PIN, one-time code or unrelated wallet contents.

Account security

Phone verification before account access helps us distinguish the account owner from an unfamiliar sign-in. If your device changes from mobile to desktop, we may use session or verification signals to protect the account and ask support to review access when something does not match.

Retention periods

We retain each data category for as long as its stated account, security, payment or legal purpose requires, then remove or restrict it according to our internal process. A Privacy Policy request can ask which category applies and whether the retention period has ended.

Changes and contact

You can ask us to correct account details, explain a data use, provide an accessible copy or record an objection where available. Send the request through account support with the relevant category; we may verify your account before making a change or sharing details.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to ask before opening access. They cover personal data, cookies, device sessions, local wallet references and requests sent through support. If your situation is specific, use the account contact path so we can check the relevant record without exposing information in a public message.

The minitoro Privacy Policy covers account details, phone verification, cookie activity, device sessions and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account use. It also explains retention, security handling and the route for access, correction or other privacy requests.

Phone verification helps connect an account request with the person controlling the verified contact path. We may use it before account access or before discussing account-specific data. If the number is no longer available, contact support through the signed-in route so the request can be checked.

Yes. The Privacy Policy covers payment references created when you use DANA or QRIS, along with OVO, GoPay, bank transfer and virtual account entries. We use these references to match status and receipts with the right account, and we do not need your wallet PIN.

Use the account support form and state that you want to access your personal data. Name the category, such as contact details, cookies, device sessions or payment references. We may verify your account first, then explain what can be provided and how the request proceeds.

You can send a correction request through the signed-in support path. Tell us which detail is wrong and what should replace it, without including a wallet PIN or one-time code. We may verify the account before changing contact information or recording the correction.

Cookies can maintain a session and help identify unusual access on mobile or desktop. Your browser can remove or restrict them, although that may lead to another login or a security check. The Privacy Policy explains their purpose, and support can clarify a specific cookie question.

You can ask support whether removal applies to the data category you name. We assess the request against its account, security, payment or legal purpose. Where access or eligibility is discussed, it depends on local law, so some records may need to remain restricted or retained.