Privacy policy and personal-data guidance
Understand a data request before responding
This page explains the privacy scope of the JL99 information hub and the questions to check before using an account service. The supplied material does not establish the current operator’s data controller, retention periods, recipients or privacy contact. This page therefore cannot replace its complete privacy notice. Read the notice at the verified destination before submitting personal information, identity documents or payment details. The gambling-related content here is for adults aged 21+.
Keep control of sensitive information
Use a unique password and keep OTPs, recovery codes and wallet PINs private. Submit an identity document only through a verified secure process with a clear explanation of the request.
On a shared device, sign out explicitly and check saved credentials, form data and screenshots before leaving.
Scope of this notice
Information reading and operator account use are different
This hub provides account guidance, game explanations and sports-reading pages. It is not an account-verification or payment-submission channel. The pages describe privacy questions that can arise when you follow an account action to another service, but they do not confirm how that service actually collects, stores or shares data. Verify the operator, the exact destination and its current notice before deciding to disclose information.
A complete operator notice should identify who is responsible for the data, what information is requested, why it is needed, who may receive it and how long it is kept. It should also explain available privacy choices and how to raise a request or concern. Those details cannot be inferred from an HTTPS address, a platform framework or a general statement about encryption in older collected material.
The content review date for this guidance is 28 October 2026. That date records the review of this page, not the effective date of an operator’s privacy policy. If a current notice differs from an earlier description, read the applicable version and obtain clarification before sharing more data. Do not assume that a general information page establishes consent to an unrelated processing activity.
Data categories to examine
What a privacy notice should make understandable
The categories below are questions to check, not a declaration that every listed item is collected by this hub or by JL99. Review the actual request and current notice rather than treating a broad list as permission to submit unnecessary information.
Account and identity details
If a service requests a name, mobile number, identity document or selfie, confirm the purpose, accepted format and secure submission route. Use your own accurate information only.
Device and browser information
Check whether the current notice covers technical information such as a browser, device or connection record. Its purpose, recipients and retention should be explained rather than assumed.
Usage and cookies
Read any applicable cookie or analytics explanation and available controls. This page does not confirm a particular tracking service, consent tool or cookie-retention period.
Security and verification records
An account service may describe records used for access checks or a dispute. Confirm what is recorded and why; never provide a password or OTP to a person in chat as a substitute for verification.
Preferences and communications
Check any language, notification or marketing choices before accepting. Look for a documented way to change a preference, and distinguish service messages from promotional communications.
Adult-use information
The gambling-related audience is 21+. Protect account and payment access from under-21s, and verify any request involving age information through the current authenticated process.
Purpose and disclosure
Ask why the information is needed and who receives it
Match a requested data item to a clear purpose in the current notice. Identity checks, payment review, account access and marketing are different activities and should not be treated as interchangeable explanations. If an upload request appears outside the normal process, pause and verify it through a route you already trust. This page does not authenticate a verification vendor or state that a particular transfer of data occurs.
Before sharing, check the destination, recipient and applicable retention or deletion explanation. Keep a record of the notice you relied on if it is relevant to a later question, without storing unnecessary sensitive files on a shared device. The supplied material does not support promises that information is never shared, is kept for a fixed period or is protected by a particular certified control.
| Notice topic | Question to ask |
|---|---|
| Purpose | What specific activity needs this item of information, and is the request proportionate? |
| Recipient | Who is responsible for receiving it, and does the notice identify any relevant third party? |
| Account process | Is this the verified secure route for the action I initiated? |
| Retention and choices | How long is the information kept, and what documented options exist to manage it? |
If a privacy question cannot be answered from the applicable notice, stop before disclosing more information and seek clarification through the verified operator. An incomplete answer is not a reason to send extra documents in the hope that the request will be resolved.
Practical account protection
Protect the device as well as the password
Use a long, unique password and a personal device with current software and a screen lock. Do not reuse a wallet or email password, and avoid saving credentials on a shared computer. Sign out explicitly when finished; closing the page alone may leave a session active. Check whether browser autofill, downloads or screenshots contain private account or identity information.
Be cautious with messages claiming to be JL99 support, verification staff or a payment provider. Verify the contact independently before responding, and never send an OTP, wallet PIN or recovery code to a person. If a device is lost or an account seems exposed, secure the connected phone and email through their verified procedures and ask the operator about the account controls it actually offers.
Privacy choices and questions
Use the documented route for a data request
A request about access, correction, deletion, communications or account closure should go to the contact identified in the current applicable privacy notice. Confirm that the route belongs to the operator and ask what verification is needed before sending documents. This hub does not authenticate a data-protection email address, response deadline or particular request outcome.
Account closure, gambling exclusion and deletion of data can involve different processes; do not assume that one automatically completes the others. Ask the operator to explain its applicable procedure and any retention conditions. Keep the request reference and response securely. This page provides reading guidance rather than a statement of legal entitlements or an operator’s binding processing practice.
Adult participation and privacy
The 21+ audience and safer information habits
Gambling-related participation is for eligible adults aged 21+ in the Philippines. Keep accounts, payment access and personal documents away from under-21s. A privacy decision should be made calmly and with the request understood. Do not submit more data because a promotion, message or game timer makes the action feel urgent.
Protecting privacy is one part of a more controlled experience; it does not remove gambling risk. Set a PHP spending limit and a stop time, and leave if participation causes pressure. If you need a break or exclusion, use the current operator’s verified procedure and ask separately how related personal data is handled. No specific account-control feature is confirmed here.
- Only eligible adults aged 21+ should use gambling-related account services.
- Verify the purpose and destination before sharing a number, document or payment detail.
- Sign out and check saved information when using a shared device.
- Keep spending and time limits in place, and stop when participation becomes harmful.
Reviewing the applicable notice
Check the version before a new data request
Revisit the current privacy notice when a service asks for new information or changes its terms. Record the effective date and clarify anything you do not understand through its verified contact. This hub’s review date is 28 October 2026 and does not certify the operator’s present processing practices. Return to JL99 home for related guidance, or leave an account action unfinished until the privacy questions are answered.
