Reference

Open jablay123 Privacy Policy

Your account details, wallet records and device signals are covered in the jablay123 Privacy Policy, so you can see what we collect and why.

Account dataWallet recordsCookie choicesAccess requests
jablay123 Open jablay123 Privacy Policy
CONTACT ROUTES

Contact us about your data

A clear contact path matters when an account record or wallet reference looks wrong. Use the support route shown after login, or reach us through the account help link near the cashier status area. Include your registered phone number, request type and any relevant transaction reference; never send your password or a complete wallet credential. We use those details to locate the right record without asking for unrelated personal content.

Team online

Account support

Use the signed-in support route for Privacy Policy questions, phone verification corrections and requests concerning the account attached to your registered number.

Wallet status

For DANA, OVO, GoPay or QRIS records, share the transaction reference and displayed status so our support team can check the matching account event.

Privacy requests

Ask for access, correction or deletion through the support contact in your account. We may verify ownership before changing or releasing personal records.

CONTROL SETTINGS

Check your account data controls

We keep this policy practical by connecting each privacy choice to an account action. You can ask what we hold, correct an inaccurate phone detail, question a wallet reference or request removal…

Data we receive

We receive registration details, phone verification results, login events, device signals and support messages. Payment references from DANA or QRIS help us match account activity without storing unrelated wallet content.

Cookie choices

Cookies can remember sign-in preferences and help us understand security events. You can clear or restrict them in your browser, though some account functions may then need another sign-in.

Account security

Phone verification before account access helps connect a session to the correct account. We also examine unusual sign-in signals and may ask for additional ownership checks.

Retention periods

We retain records only for the period needed for account service, security checks, payment matching, dispute handling or legal duties. A deletion request does not erase required records immediately.

Correction requests

If your phone detail, name or transaction reference is inaccurate, contact support from the account route. Tell us what is wrong and provide the corrected value for checking.

Who handles requests

Our support team receives privacy questions through the signed-in contact path. We verify the requestor, explain the available action and confirm when a change or response is recorded.

Find Privacy Policy answers

These Privacy Policy answers cover the account and payment questions we hear most often. If your situation is not listed, send the details through the signed-in support route so we can check the relevant record without exposing it to another person.

It covers registration details, phone verification, login and device signals, support messages, cookie use, game activity records and payment references connected with DANA, OVO, GoPay, QRIS or bank rails.

We record transaction references and displayed statuses to match a wallet event to your account, investigate a missing or unclear cashier result and respond to a payment-related request.

Use the signed-in support contact and ask for an access request. Include your registered phone number and describe the records you need; we verify account ownership before sharing them.

Yes. Contact support with the inaccurate field, such as a phone detail or transaction reference, and provide the corrected value. We check the request before updating the account record.

Retention depends on the purpose. Security, payment matching, dispute handling and legal duties can require records to remain after a normal account-service need has ended.

Cookies may remember sign-in preferences and support security checks. You can restrict or clear them through your browser settings, but doing so may require repeated sign-in steps.

Yes, access and eligibility depend on local law. We apply this Privacy Policy where local law permits, and support can explain the account route available for your location.