Reference

100ml Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details needed for your 100ml account, including phone verification before account access and wallet records for DANA…

Clear data purposesCookie choicesAccount access stepsWallet record context
100ml 100ml Privacy Policy For Your Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact path helps you resolve a Privacy Policy question without guessing which team to reach.

Account access request Use the support link connected to your account when you need a copy of personal data, a correction to your phone details or help understanding which account records the Privacy Policy covers. We verify the account before sharing information, so your request stays with the right person.
Wallet record question For a payment-status or receipt question, send the reference from DANA, OVO, GoPay or QRIS through our support path. We use that reference to trace the relevant record without asking you to share a wallet PIN, password or full authentication code.
Security concern If you notice an unfamiliar login, device session or account message, contact support through the account help path and change your password before sending details. We can review the security event, explain the related data handling and guide you through the next account-access step.
DATA HANDLING

How We Apply The Policy

The Privacy Policy is put into practice through ordinary account and security controls rather than broad collection for its own sake.

Account information

We use your account details to create access, complete phone verification and respond to requests about the Privacy Policy. If you ask us to correct a phone number or another eligible detail, we may request an account check before changing the record so the update is not made by an unauthorised person.

Payment references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, amount and status record for reconciliation. Bank transfer and virtual account records may follow the same purpose. We do not need your wallet PIN or password to answer a Privacy Policy question about a receipt.

Cookies and sessions

Cookies help keep a sign-in session active, remember selected preferences and identify unusual access patterns. You can adjust cookie controls in your browser, although refusing some cookies may affect account access or require another login. The Privacy Policy explains why each retained cookie category is used.

Mobile and desktop

When you move from a phone browser to desktop, the site may treat the new device as a separate security event. We use device and session signals to protect the account, not to replace the policy rights available to you. Sign out of shared devices after checking your data or payment status.

Retention decisions

We keep personal data only while it supports account operation, security checks, payment reconciliation, support history or a legal requirement. Retention can differ by record type, so a request to remove one detail may not remove every associated transaction reference. We explain the applicable reason when responding.

Changes and requests

You can contact us to ask what information we hold, correct an inaccurate detail, question a cookie or request deletion where local law permits. Include your account phone number and the specific record involved. We may request verification, then respond with the action available under the Privacy Policy.

Privacy Policy Answers For 100ml

These Privacy Policy answers address the account questions that matter before you open access or send a data request. They cover phone verification, wallet references, cookies, device sessions, retention and the route for correcting or removing eligible information. If your question involves access, eligibility depends on local law, and support may need to verify the account before discussing personal records.

The Privacy Policy explains that we collect account details needed for access, phone verification, security checks and support. It also describes how we handle device sessions, cookie preferences and payment references. We use each category for a stated account, security, reconciliation or legal purpose rather than treating all data alike.

Phone verification connects an account request to the person seeking access and helps us answer a data request safely. It can also help identify unusual login activity. If you ask about your Privacy Policy records, we may verify the phone number linked to your account before sharing or changing personal details.

Yes. The Privacy Policy covers payment references that appear in our records when you use DANA, OVO, GoPay or QRIS, including a status or receipt reference used for reconciliation. The relevant wallet or bank provider has its own privacy terms, so its handling may be separate from ours.

Cookies can keep a mobile session active, store selected preferences and help identify unusual access. You can change cookie controls in your browser, but refusing necessary cookies may require another login or affect account access. The Privacy Policy explains the purpose of the cookie categories used on the site.

You can contact support through the account help path and request access to eligible records or correction of an inaccurate detail. Include your account phone number and describe the requested change. We may verify your identity first, then handle the request according to the Privacy Policy and local law.

We retain information for the period needed for account access, security review, payment reconciliation, support history or a legal obligation. Retention differs by record type, so deleting an account detail may not remove a transaction reference. If you ask, we can explain the reason a specific record remains.

Use the support route connected to your account and state that your request concerns the Privacy Policy. For payment records, add the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. Do not send a wallet PIN or password; we will request only the verification needed.