Reference

zippo365 Privacy Policy: Clear Account Data Rules

Our Privacy Policy shows what we collect when you create an account, complete phone verification, open the lobby on mobile, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet contextMobile privacy

Explore The Lobby Read FAQ

See How Wallet And Account Data Moves

zippo365 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to details you submit during account creation, including your phone number and verification status, plus records created when you use the cashier path. A DANA, OVO, GoPay or QRIS selection may produce payment reference data, while bank transfer or virtual account activity

1
can show a bank rail such as BCA, BRI, Mandiri or BNI. We use these records to match account actions, check payment status and protect the account from unauthorised access. Device type, browser settings and sign-in events may also be recorded when you open the lobby
2
from a mobile browser or desktop. We keep processing tied to the stated purpose, and availability depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP ROUTE

Get Direct Help With A Policy Request

A clear support path helps when your account record or wallet reference needs checking. Start from the account support route and include the phone number linked to your account, the relevant date…

Account request Ask us to correct account details through the support route connected to your login. We may confirm your phone verification before changing a record.

Wallet reference If a DANA, OVO, GoPay or QRIS reference looks wrong, send the receipt code and payment date. We can compare it with the account record.

Policy question For a Privacy Policy question, state the section and action you want clarified. We will keep the request focused on your account data.

DATA CONTROL POINTS

Know What We Keep And Why

We treat privacy as an account process rather than a decorative page. The policy connects sign-in, phone verification, payment references and device events to specific handling purposes.

Account security

We use sign-in events, phone verification status and device signals to help identify unusual account activity. We do not ask for your password in a support request.

Payment records

Payment references help us match cashier activity with your account. DANA, OVO, GoPay, QRIS and bank rails can create different reference fields.

Cookie choices

Cookies and similar browser data can remember session settings and help the account path function. Your browser controls can restrict them, though some steps may change.

Mobile signals

When you open the lobby through a mobile browser, we may record device and browser details for session security and troubleshooting, not for unrelated purposes.

Retention approach

We retain account, verification and payment records only for the stated operational, security or legal purpose. Retention can vary by record type and local requirements.

Change requests

You can ask us to correct, explain or remove eligible data through support. Include your linked phone number and request details so we can confirm the account.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the account steps Indonesian customers ask about most, from phone verification to wallet references and browser data. If your situation is not listed, use the policy support route with the account details we need to locate your record.

It covers account details, phone verification, sign-in events, device and browser data, cookies, payment references and requests to correct or remove eligible personal data.

We use your phone number to create and identify your account, complete phone verification before account access, and connect support requests to the correct account record.

Yes. The Privacy Policy covers payment references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use them to match status with your account.

When you sign in through a mobile browser or desktop, we may handle device type, browser settings and sign-in events for session security, troubleshooting and account protection.

Use the account support route and provide your linked phone number, the record you believe is incorrect and the requested change. We may verify account ownership first.

Retention depends on the record and its purpose. Account, verification and payment records may remain while needed for operations, security or legal requirements, subject to local law.

Yes. Send a focused policy request through account support, naming the section or data type involved. Do not include your password; we will ask only for needed account details.

zippo365 Privacy Policy: Clear Account Data Rules

Get Direct Help With A Policy Request

Know What We Keep And Why

Account security

Payment records

Cookie choices

Mobile signals

Retention approach

Change requests

Privacy Policy Answers For Your Account

01 What does the zippo365 Privacy Policy cover?

02 Why does zippo365 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS data?

04 What device data can the Privacy Policy cover?

05 How can I request a correction to my data?

06 How long does zippo365 keep personal data?

07 Can I ask questions about this Privacy Policy?

Related Pages