18JL Privacy Policy
This page explains how information may be handled when users access or interact with 18JL on mobile or desktop. It is written for players and visitors in the Philippines who want a direct view of what may be collected, why it may be used, and what choices may be available.
Some features may collect only basic technical data. Others may involve account details, support messages, or transaction-related records where a service needs them. If a feature is not used, related data may not be collected.
About This Privacy Policy
This page is provided to explain privacy practices in a clear and accessible format. It is not legal advice. Users should review the current policy information applicable to their use of the website.
Information
The website may handle information that helps it run, support users, and keep records tied to site activity where applicable.
Use
Data may be used for service delivery, account management, support, security, technical maintenance, and related operational needs.
Control
Users can review the policy, manage browser preferences where supported, and raise privacy questions through the Contact page.
Updates
Privacy practices may change when services, tools, or requirements change. Policy updates may be reflected on this page.
Information We May Collect
The categories below describe information that may be collected depending on the feature used, the page visited, or the way a user contacts the website.
| Information Type | What it may include | Why it may matter |
|---|---|---|
| Account Information | Details needed to create or manage access to an account, where registration or login features are used. | Lets the website maintain account access and support account-related services. |
| Contact Information | Information shared through a message, inquiry, or support request. | Helps the website respond to questions and keep a record of the request. |
| Technical Information | Browser type, device type, operating system, IP address, language settings, and technical logs where applicable. | Supports site performance, compatibility, and basic security monitoring. |
| Usage Information | Pages viewed, time spent, clicks, and similar interaction signals. | Helps the website understand how features are used and where improvements may be needed. |
| Cookie Information | Browser-based data used for sessions, preferences, or technical functions where cookies are enabled. | Can help keep a session working and remember basic preferences. |
| Transaction Information | Where payment or withdrawal features are available, records related to the requested transaction may be processed. | Helps complete the request, track status, and keep operational records. |
| Security-Related Information | Signals connected to fraud checks, abuse prevention, or suspicious activity review. | May help protect the website, user accounts, and service stability. |
Account details
If account registration is available, the website may need certain details to create access, keep records, and provide account support. The exact fields depend on the service flow shown on the site at the time.
Users should keep account details accurate. That helps avoid delays when the website needs to verify access, troubleshoot a problem, or review a request.
Transaction records
Where payment-related features are available, transaction information may be handled to process the request, check status, confirm completion, or support a review. The website should not be treated as a place to share unnecessary payment details.
If a user sees a payment request that feels unusual, it is better to stop and confirm it through the official Contact page before taking action.
For PH users, the safest rule is simple: do not send passwords, OTPs, PINs, or full payment credentials through informal channels. If a request looks rushed or unusual, use the site’s official contact path and verify it first.
How Information May Be Used
The website may use information for practical tasks tied to operation, support, and account handling. The purpose depends on the service or feature being used.
Account Management
To create access, maintain account records, and handle requests linked to a user account where such a feature is enabled.
Service Delivery
To provide the page, feature, or function that the user selected, including related processing that keeps the service working.
Support
To read a message, review the issue raised, and reply through the channel used for the inquiry.
Technical Improvement
To understand how pages perform on mobile and desktop and where loading, display, or navigation issues may appear.
Security
To watch for suspicious activity, misuse, or conditions that could affect the site, user accounts, or service availability.
Compliance and Records
To keep records where needed for operational handling, issue review, internal control, or applicable requirements.
Communication
To send replies or updates connected to a request, account matter, or policy question when a response is appropriate.
Feature Support
To support cookies, sessions, and other technical elements that keep a page or feature usable during a visit.
Privacy perspective
Useful data should stay useful. That means the website may process only what it needs for the task at hand, instead of asking for extra details that do not help the service.
User control note
If a user does not want a browser to remember certain preferences, cookie controls may be adjusted in the browser or device settings where supported.
Cookies & Technical Information
Cookies are small browser files that may support sessions, preferences, or basic site functions. They are not always required for every feature, but they often help a page work more smoothly.
Why cookies may be used
Cookies may help remember a session, keep a page state active, or reduce repeated steps during a visit. They may also help the website understand whether a page is loading as expected.
Where applicable, they can support navigation, language handling, and other basic functions that make browsing less repetitive.
Technical signals
Browser and device details may be read to keep the website compatible with common mobile screens and desktop setups. That can include system type, browser type, and simple log data.
These signals are usually about function, not personal profiling. They help the site know how it is being opened.
What cookies are not
Cookies are not a promise of complete tracking and they are not a guarantee that every visit will look the same. Their use depends on the website configuration and the browser settings on the user’s device.
What users can do
Browser settings may allow cookies to be cleared, restricted, or blocked. If a setting is changed, some features may not work the same way.
Information Sharing
Information may be disclosed only when necessary for the operation of applicable services, to support a request, where required by law, or where otherwise permitted under the site’s current handling practices.
Service support
Data may be shared with relevant technical or operational support that helps the website function, respond, or maintain a requested service.
Request handling
If a user contacts the website, the details of that message may be seen by the people or systems that handle the inquiry.
Legal needs
Some information may be disclosed when a request has to be handled under applicable requirements or a valid process.
Business operation
Operational records may be reviewed internally for quality, security, system maintenance, or related administration tasks.
If a third party is needed to keep a service running, the website may rely on that third party for the relevant task. That does not mean every detail is shared with everyone. The handling should stay tied to the purpose.
Data Security
Reasonable measures may be used to help protect information from unauthorized access, misuse, or loss. The exact setup can vary by service, device, and technical configuration.
What this means in practice
The website may use basic administrative, technical, and operational safeguards that fit the feature being used. That can include limited access, standard logging, and common site controls where applicable.
No online system is perfect. Users should still keep their own credentials private and avoid sending sensitive account data through unofficial channels.
Good user habits
- Use strong passwords for any account you open.
- Keep OTPs and PINs private.
- Check that a request comes from the official site flow.
- Review account activity if something looks unfamiliar.
Security awareness
From a privacy point of view, many problems start with rushed sharing. Slow down if a message asks for sensitive details that do not seem necessary for the task.
Data Retention
Information may be retained for as long as reasonably necessary for the relevant purpose, subject to applicable requirements and operational needs.
Active use
Data may stay available while an account, request, or feature is still being used.
Support records
Messages and case details may be kept long enough to review the issue and close the request.
Operational records
Logs or technical records may be retained for system checks, abuse review, and service maintenance.
Required handling
Some records may need to stay longer if a requirement, dispute, or security review is still open.
Retention depends on purpose and context. If a specific timeframe is required for a feature or record type, the current policy or service notice should say so.
User Privacy Choices
Privacy choices are often practical. They are not always formal requests. Many can be handled through browser settings, careful sharing, or the Contact page.
Review your details
If an account is used, users should keep their details accurate and update them where the site allows it.
Manage cookies
Browser controls may let a user clear or restrict cookies. Some features may change if cookies are blocked.
Ask a question
If a user wants to know what data is involved, the Contact page is the cleanest place to ask.
Check the current policy
Users should review the live policy page from time to time, especially after service changes or feature updates.
What users should avoid sharing
Passwords, OTPs, PINs, one-time security codes, and full payment credentials should stay private. Those details are sensitive and usually not needed for a normal support conversation.
Where to raise privacy questions
Use the Contact page for questions about information handling, account records, cookies, or a request to clarify a policy point.
Policy Updates
This policy may be updated when services, tools, or handling practices change. The page should always be checked in its current form.
Why updates happen
A privacy page may need a refresh when a feature is added, a support process changes, browser behavior changes, or a different data flow is introduced.
How to stay current
Users should review this page before sending information that matters to them. If something looks unclear, the Contact page can be used to ask for a plain answer.
Privacy FAQ
Short answers for common privacy questions. If the details you need are not listed here, use the Contact page and ask directly.
1. What information may 18JL collect?
It depends on how the site is used. The website may handle technical information, cookie data, support messages, account-related details where an account feature is used, and transaction-related records where applicable.
If a feature is not used, related data may not be collected. The policy is meant to track the real service flow, not list every possible item as a certainty.
2. Why may account information be needed?
Account information may be needed to create access, keep records, maintain a user profile, and support account-related services. It can also help the website manage requests tied to the account.
The exact details depend on the current registration or account flow. If the site does not ask for a field, it should not be assumed to exist.
3. Does the website use cookies?
It may use cookies where the configuration supports them. Cookies can help with sessions, preferences, navigation, and simple technical functions that make a visit smoother.
Users can often adjust browser settings if they want to clear or restrict cookies. Some functions may behave differently after that.
4. What technical information may be collected?
Technical information may include browser type, device type, operating system, IP address, language settings, and basic logs. The exact mix depends on how the page is opened and what the site needs to run properly.
This kind of data is usually used for compatibility, troubleshooting, performance, and security review rather than for a full personal profile.
5. How may transaction information be handled?
Where payment or withdrawal features are available, transaction-related information may be processed to complete the request, track its status, or support recordkeeping.
Users should not send extra financial details unless the official service flow asks for them. If a request seems unusual, confirm it through the Contact page first.
6. Can users ask about their personal information?
Yes. A user can ask what information may be involved, why it may be used, or how a specific request is handled. The Contact page is the right place for privacy questions.
If a request involves account access or a record check, the website may need enough detail to understand what the user is asking about.
7. How is information protected?
Reasonable measures may be used to help protect information from unauthorized access, misuse, or loss. The exact controls may depend on the service, the device, and the technical setup.
Users still have a role to play. Keep passwords private, avoid sharing OTPs or PINs, and review requests before sending sensitive details.
8. How long may information be retained?
Information may be kept for as long as reasonably necessary for the relevant purpose, subject to operational needs and applicable requirements. No fixed period is stated on this page.
Some records may need to stay longer if a support case, security review, or operational matter is still open.
9. Can the Privacy Policy change?
Yes. The policy may be updated when services, features, or handling practices change. Users should check this page from time to time and read the current version before sharing information.
If the site changes a data flow, the policy should reflect that change in plain language.
10. Where can privacy questions be directed?
Use the Contact page for privacy-related questions, clarification requests, or concerns about how information may be handled. That is the safest and most direct route.
If the question is about service terms as well, the Terms page may also help as a companion reference.
Have a Privacy Question?
If something in this page needs a clearer explanation, use the Contact page. Keep the message short. Mention the feature, page, or account issue you want checked.
Best next step
Review the section that matches your question first. Then open the Contact page if you still need clarification about information handling, cookies, or account-related records.
Useful reminder
Do not send passwords, OTPs, PINs, or full payment credentials in a casual message. Use the official site path and keep sensitive details limited to what is needed.