Reference

jumbo33 Privacy Policy for Your Account

Our Privacy Policy shows how we handle your account details, phone verification, cookie choices and wallet records when you use jumbo33.

Clear data purposesCookie choicesWallet record controlsAccount request path
jumbo33 jumbo33 Privacy Policy for Your Account
REQUEST SUPPORT

Privacy Help Through Your Account

A clear contact route matters when you want to ask about your Privacy Policy rights or correct an account detail.

Policy questions Open the support path inside your account and ask what data we hold, why…
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction reference…
Access correction For a phone, device or sign-in issue connected to a data request, use the…
DATA PRACTICES

What We Do With Your Account Data

We treat the Privacy Policy as an operating process, not a page kept apart from account activity.

Account details

We use details such as your account identifier and verified phone status to sign you in, protect the account and…

Device and sessions

A mobile browser or desktop session may create technical records such as device type, browser signals and sign-in time.

Cookies

Cookies can keep your session active, remember selected settings and help us understand whether a page works as intended.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier status without storing a wallet…

Retention

We keep each category only for the period connected to its purpose, account security, dispute handling or applicable legal duties.

Your requests

You can ask through account support about access, correction, deletion or a processing concern.

Privacy Policy Questions About jumbo33

These Privacy Policy answers cover the account steps Indonesian customers ask about most often, including phone verification, cookies, wallet references and requests made through support. If your situation is different, use the signed-in contact route so we can check the relevant record without exposing private payment credentials.

It covers account details, phone verification, device and session records, cookies, support messages, security events and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm account control, reduce mistaken access and connect a privacy request to the right record. We use the verification result for account security and handle it under this Privacy Policy.

Our policy covers the payment reference and status we receive for account reconciliation. DANA, OVO, GoPay, QRIS, banks and other wallet providers manage their own records under their separate privacy terms.

Use the support path inside your signed-in account and ask for an access request. We may verify your phone or ask for reasonable proof before responding, and fulfillment depends on local law.

Yes. Send a correction request through account support and identify the field that appears wrong. We review the request against account records, may confirm your identity, and update it where local law permits.

Cookies can support sign-in continuity, saved settings and technical page checks. You can use the cookie settings path to adjust available choices, although some account functions may not work without necessary session cookies.

Sign in and use the support route connected to account help, then describe your privacy question without sending a wallet PIN. Include a receipt reference only when requested so we can locate the correct record.