Reference

Privacy Policy for Your jelas33 Account

The jelas33 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet recordsDevice securityCookie choices
jelas33 Privacy Policy for Your jelas33 Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path matters when you want to ask what data we hold or why an account record appears in a wallet status check.

Data access request Ask us for the personal data connected with your account, including contact details, phone verification records and support correspondence. We use the account email or verified phone path to confirm that the request comes from you before sharing any private account material.
Correction request If your account detail is wrong, tell us which field needs correction and why. A specific request helps us compare the change with the account record, wallet reference or phone verification step without exposing unrelated activity from your account.
Privacy contact For cookie questions, retention concerns or a request about deletion, contact support from the signed-in account path where possible. We may retain a limited record when required to resolve security, payment or legal obligations, and we will explain the applicable reason.
HANDLING DETAILS

How We Apply This Policy

This Privacy Policy is tied to real account actions rather than broad statements. We use account and device signals to keep sign-in connected to the right person, payment references to match wallet…

Data handling

We collect details you submit during account creation and verification, then combine them with limited activity records needed to provide account access and answer support cases. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account are used to match status, not to create unrelated profile details.

Cookies and devices

Cookies and similar device signals help keep your session connected while you move from login to the lobby on mobile or desktop. They can remember technical preferences and help identify unusual sign-in behaviour. Your browser settings can control some cookies, although parts of the account path may then work differently.

Account security

Phone verification is an account protection step before access is completed. We may use sign-in time, device details and security events to investigate an unusual session or a wallet-status dispute. Never send a password or one-time code through a support message, even when asking about this policy.

Retention choices

We keep personal data only for the period needed for the purpose described in this policy, account security, payment reconciliation or a legal requirement. When a retention reason ends, we may remove, anonymise or restrict the record. A deletion request does not automatically erase records that must remain for those purposes.

Your requests

You can ask us to access, correct or delete eligible personal data, or ask us to explain how a record is used. Include your account contact and the request type. We may verify ownership before acting, and we will limit the response to information that belongs to your account.

Policy changes

If our data practices change, we will update this Privacy Policy and show the revised wording on the policy page. Check this page before changing account details or payment settings. Where a change affects your choices, the updated section will identify the relevant data use and contact path.

Privacy Policy Questions About jelas33

These Privacy Policy answers address the account questions you are most likely to have before opening jelas33 or asking support for a data change. They cover collection, payment references, device access, cookies, retention and requests from Indonesia. If your situation is not listed, use the signed-in support path and describe the exact account record you want us to check.

It covers account details, phone verification, sign-in and device records, cookie use, support messages, payment references and retention. It also explains how to ask for access, correction or deletion. Availability and eligibility depend on local law, including whether access is permitted in your location.

We collect the details you submit for the account path, such as contact information and phone verification status. We may also create technical records from sign-in and device activity so we can protect access, connect support cases and investigate an unusual session.

Yes. The policy covers payment references linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a wallet or transfer status with the correct account and to answer a receipt or cashier-status question.

Phone verification helps confirm the account holder before access is completed. We can also examine device and sign-in signals when a session looks unusual. Use your own device where possible, keep account credentials private and contact support from the account path if access behaves unexpectedly.

You can request a correction or deletion through the privacy contact path. Tell us which record is involved and include the account email or verified phone route. We may confirm ownership first, and some records can remain when needed for security, payment reconciliation or legal duties.

We retain each category for the period needed for its stated purpose, account protection, payment reconciliation or a legal requirement. After that period, we may remove, anonymise or restrict it. Ask support about a specific record and we will explain the retention reason that applies.

Use the signed-in support path and identify the request as a Privacy Policy question. Include the account contact, the data category and the action you want, such as access or correction. We may request an account verification step before discussing private records or payment references.