90JILI Privacy Policy Philippines-facing site Clear reading on mobile and desktop

90JILI Privacy Policy

This Privacy Policy explains how information may be handled when users access or interact with 90JILI and related website features. It is written in a direct format so visitors can review privacy details without digging through a long legal wall. For users in the Philippines, questions often come up around registration, login access, device changes, cookie prompts, and contact requests. This page keeps those points practical and easy to scan.

Quick privacy view

Information

Depending on the service used, 90JILI may process personal, technical, account, communication, or transaction-related information.

Use

Information may be used for account handling, support, service delivery, security checks, and website maintenance.

Cookies

Cookies may support login sessions, preferences, navigation, and basic site performance where applicable.

Choices

Users may review the policy, adjust browser settings where supported, and use the Contact page for privacy questions.

About this Privacy Policy

What this page is meant to do

This page is provided to explain privacy practices in a direct format. It is not a sales page. If you are looking for support, account help, or a place to raise a privacy question, this policy points you to the right next step.

For users in the Philippines, privacy concerns often appear when someone creates an account, changes devices, opens the site from mobile data, or receives a cookie notice for the first time. That is why the wording here stays simple and practical. If a feature is not being used, the related information may not be needed.

Users should review the current policy information on the website before sharing details through any support channel. Where a feature, tool, or service is not active, privacy handling may be different from what is described here.

Information we may collect

What may be collected, depending on the feature used

The website may process different categories of information depending on how a visitor interacts with it. Not every category applies to every user. The main idea is simple: the site may need enough information to keep an account working, help with support, understand basic technical activity, and manage normal website operations.

Information Type What it may involve Why it may matter
Account Information Details used to create or manage an account, maintain access, or keep records linked to a user profile, where applicable. Supports sign-in, account management, and service continuity.
Contact Information Information shared when a user sends a message, asks for support, or raises a privacy-related concern. Helps the site respond to questions and follow up on requests.
Technical Information Browser type, device details, operating system, language preferences, IP address, and similar technical signals where relevant. Helps the website function correctly and spot technical issues.
Usage Information Basic information about how the website is used, such as pages viewed, features opened, or navigation behavior where applicable. Supports site improvement and easier navigation.
Transaction Information Where transaction features are available, related details may be processed to support the requested action. Helps complete or record the transaction properly.
Communication Information Message content, support details, and any follow-up information shared through the website’s contact path. Helps the team understand the issue and reply with relevant information.
Cookie Information Small browser data that may support sessions, preferences, and basic site functionality, depending on configuration. Helps remember settings and maintain smoother browsing.
How information may be used

Practical purposes, explained plainly

Information may be used for relevant purposes tied to how the website operates. The exact use depends on the feature, the page, and the action the user chooses. That keeps the policy flexible without pretending that every piece of information is used in the same way.

Account handling

Where an account feature exists, information may be used to create access, maintain account records, and help the user return to the same profile later.

Service delivery

Data may support the normal operation of pages, forms, support paths, and any feature the user chooses to open or request.

Support and communication

If a user sends a question or issue, the website may use the message content and related details to respond more accurately.

Security checks

Technical signals may be reviewed to help spot unusual activity, protect accounts, or keep the site operating normally.

Website maintenance

Usage and technical information may help identify broken links, load problems, or other issues that affect browsing.

Legal or policy needs

Where required, information may be reviewed to support compliance with applicable requirements or internal policy handling.

Security Awareness

A useful privacy habit is to avoid sending passwords, OTPs, PINs, or other sensitive account credentials through unofficial channels. If a request looks unusual, verify it through the website’s normal contact path before sharing anything.

User Control Note

Users should keep their own browser settings, saved devices, and account recovery details under review. Small changes there can affect how sessions, cookie prompts, and logins behave on mobile devices.

Cookies & technical information

How browsing data may help the site work

Cookies are small pieces of browser data that may help the website remember a session, keep preferences in place, or understand basic usage patterns. Technical information may also support navigation and page performance where applicable.

Cookie use may depend on the website configuration and the feature being used. If cookie prompts appear, users should read them carefully and decide what fits their own device or browser settings. Some browsers allow users to clear cookies, block certain cookies, or manage stored site data directly.

Sessions Preferences Navigation Basic performance
Account & transaction information

When account-related data becomes important

If a user creates an account or uses a feature that depends on account access, some information may be needed to set up the profile, keep the account available, and handle support requests later. The exact details depend on the service in use.

Where payment or transaction features are available, related information may be processed as necessary to support the requested action, record the event, or maintain the relevant account history. This policy does not list provider names unless they are confirmed on the website.

A practical privacy rule: check your details before submitting them. If account information is inaccurate, it can slow down support, recovery, or verification steps.

Information sharing

Who may receive information, and when

Information may be disclosed to relevant service providers or other parties where necessary for the operation of applicable services, where required by law, or where otherwise permitted. The exact sharing pattern depends on the feature in use and the technical setup behind it.

Third-party services may support hosting, technical maintenance, communication, or other operational functions. If the website uses such services, the related information may be handled under those arrangements. This page does not name providers unless the source text confirms them.

Data security

Reasonable protection, without overpromising

Reasonable measures may be used to help protect information from unauthorized access, misuse, loss, or similar issues. Security handling can include operational checks, access control practices, and maintenance routines based on how the website is configured.

That said, no online service should pretend to be perfect. Users should keep their own devices secure, avoid unknown links, and use official pages when entering sensitive details. Small habits make a real difference.

Security Awareness

From a privacy perspective, the safest move is to treat requests for passwords, one-time codes, or recovery details with caution. If a message, page, or person asks for sensitive information outside the usual process, verify it first.

Data retention

How long information may be kept

Information may be retained for as long as reasonably necessary for the relevant purpose, subject to applicable requirements and operational needs. That means retention can depend on account status, support history, technical needs, security review, and whether a feature is still active.

This page does not promise a fixed deletion period because one was not confirmed in the source text. Users who need clarity on a specific record can use the Contact page and ask what applies to their case.

User privacy choices

Practical ways to stay in control

  • Review the current policy Check the policy when you use a new feature, switch devices, or notice a change in how the site behaves.
  • Manage browser settings Where supported, browser tools may allow you to clear cookies, limit stored data, or adjust preferences.
  • Use the Contact page Raise privacy questions if you want clarification on handling, access, or the kind of information tied to your use of the site.
  • Check unofficial requests If someone asks for sensitive details in a way that feels unusual, verify the request before replying.
Policy updates

How this page may change

Privacy practices may change when the website changes, features are added, or operational requirements shift. When that happens, the policy information on this page may be updated to match the current setup.

Users should revisit the policy from time to time, especially before sending new information or using a feature for the first time. If a specific update date is available on the website, it should be read together with this page.

Privacy FAQ

Common privacy questions, answered in plain language

1. What information may the website collect?
Depending on the service or feature being used, the website may process account, contact, technical, usage, communication, cookie, or transaction-related information. Not every category applies to every visitor. The point is to collect only what is relevant to the action being taken.
2. Why may account information be used?
Account-related information may be used to create access, manage records, keep sessions working, and support account-related services. If a user does not use an account feature, that type of information may not be relevant.
3. Does the website use cookies?
Cookies may be used where applicable to help with sessions, preferences, navigation, or basic site performance. Cookie use can depend on the website configuration and the feature being used, so users should check the current browser prompt or settings when they appear.
4. What technical information may be collected?
Technical information may include browser type, device details, operating system, language settings, IP address, and similar signals where relevant. This kind of information can help the website operate correctly and identify technical issues.
5. How may transaction information be handled?
Where transaction features are available, related information may be processed as needed to support the requested action and keep a relevant record. The policy does not name payment providers unless the source text confirms them.
6. Can users ask about their personal information?
Yes. If a user wants clarification about the kind of information linked to their use of the website, the Contact page is the right place to start. It is better to ask a specific question than to guess how a feature works.
7. How is information protected?
Reasonable measures may be used to help protect information from unauthorized access, misuse, or loss. Users should still keep their own devices, passwords, and browser sessions secure, because privacy also depends on everyday habits.
8. How long may information be retained?
Information may be retained for as long as reasonably necessary for the relevant purpose, subject to applicable requirements and operational needs. The exact period was not confirmed in the source text, so no fixed retention promise is given here.
9. Can this Privacy Policy change?
Yes. Privacy practices may change when services, technical setup, or requirements change. Users should review this page from time to time so they know how information may be handled at the moment they use the site.
10. Where can privacy questions be directed?
Privacy-related questions can be directed through the Contact page. If your concern involves account access, support, or a record linked to your use of the site, it helps to describe the issue clearly so the reply can focus on the right part of the policy.
Contact

Have a Privacy Question?

Review the policy information above, then use the Contact page if you need to ask about information handling, cookies, account-related data, or a privacy concern tied to your use of 90JILI.

Contact Us