OKFUN Privacy Policy
This page explains how information may be handled when you access OKFUN or use related website features. It covers account details, device data, cookies, communication records, and other privacy points that matter to users browsing from the Philippines. If you are checking how the site treats personal information before you continue, this is the right place to start.
About This Privacy Policy
OKFUN uses this policy to explain privacy handling in plain language. The goal is simple: show what may be collected, why it may be used, how cookies may work, and where users can raise questions.
If you browse from a mobile phone, tablet, or desktop, the same basic privacy approach may apply. Some information is gathered only when a feature is used. Other information may be processed automatically for technical or security reasons.
This page is provided to explain the website’s privacy practices in a clear and accessible format. Users should review the current policy information applicable to their use of the website.
Privacy Note
A useful privacy habit is to check what you share before creating an account, sending a message, or using a payment-related feature. If a detail is not needed, it is usually better not to submit it.
The site may update this page when features, settings, or operational requirements change.
Policy Summary
What may be collected
Depending on the service used, OKFUN may process account, contact, technical, cookie, communication, or transaction-related information.
Why it may be used
Information may help with account access, service delivery, support, security checks, and site improvement where applicable.
How it may be handled
Reasonable measures may be used to help protect information from unauthorized access, misuse, or loss.
What users can do
Users may review browser settings, check account details, and use the Contact page for privacy-related questions.
Information We May Collect
The categories below describe the types of information that may be processed depending on the pages visited, the features used, and the settings available on the website. Not every category will apply in every case.
| Information Type | Possible Purpose | Practical Note |
|---|---|---|
| Account Information | Account access, maintenance, and service support | May be used where a user creates or manages an account. |
| Contact Information | Communication and support follow-up | May include details shared through a contact or inquiry channel. |
| Technical Information | Site operation, device compatibility, and troubleshooting | May include browser, device, language, or log-related data. |
| Cookie Information | Session handling, preferences, and basic website functionality | Cookie use may depend on the website configuration. |
| Communication Information | Support records and message handling | May include the content of messages and related response notes. |
| Transaction Information | Processing requests related to payments or account activity | Only relevant where payment functionality is available. |
Account Information
Where account features are available, information may be used to create access, maintain records, and support service-related requests.
Device & Technical Data
Technical details may help the website load properly on Android, iOS, and desktop browsers, and may assist with performance checks.
Communication Records
If you send a message, the website may keep the content of that message and related details needed to respond appropriately.
Security-Related Information
Certain logs or activity patterns may be reviewed where needed to help detect misuse, protect accounts, or maintain service integrity.
How Information May Be Used
Information may be used for practical reasons tied to the website’s operation. That usually means helping the site work properly, keeping user access stable, and handling requests without unnecessary delay.
In a typical browsing session, the same data may serve more than one purpose. For example, technical information can support both troubleshooting and security review. Account details may help with access, record keeping, and support communication.
Data Handling Note
Users should keep account details accurate where account functions are used. If a message or record is incomplete, support teams may have difficulty understanding the request or confirming the right context.
Account management
Information may be used to create access, maintain records, and support the features that a user chooses to use.
Communication
Messages and contact details may be used to answer questions, clarify requests, or follow up on service issues.
Risk monitoring
Technical or activity data may be reviewed where needed to help identify unusual behavior or protect the website from misuse.
Site performance
Usage patterns may help the website understand which pages load well, which features need adjustment, and where browsing can be smoother.
Privacy practices may vary depending on the feature being used. A guest visitor, a registered user, and a user who sends a support request may each trigger different handling steps.
Cookies & Technical Data
Cookies are small files or similar tools that may help a website remember a session, keep preferences in place, or understand how pages are being used. They can make browsing easier, especially when a user moves between pages or returns later.
OKFUN may use cookies or related technical methods where applicable for basic operation, navigation support, and usage analysis. Exact cookie behavior can depend on the website setup and the feature being used.
Technical information may also include browser type, device type, operating system, language settings, IP address, or log data. These details are often used in a general way to keep the site stable and to help diagnose problems.
Cookie Information Box
If a browser blocks cookies, certain functions may not work as expected. A session may end sooner, a preference may not save, or a page may not remember the last selected setting.
Users can review browser controls if they want to limit or clear stored cookies on their device.
Account & Transaction Information
Where account features are available, the website may process information needed to create access, maintain records, and support the services that a user requests. That can include information entered during registration, details used to verify access, or records tied to account activity.
Where payment functionality is available, transaction-related information may be processed as necessary to support the requested transaction. This may include records needed for confirmation, reconciliation, support, or security review. The exact details depend on the feature in use and the available service configuration.
Why accuracy matters
Accurate account details help reduce confusion, especially when a user needs help with access or a service-related issue.
Transaction records
If a transaction feature is available, related records may be retained for support, audit, or operational purposes where appropriate.
Payment handling
The website does not need to expose payment details publicly. Sensitive information should be shared only through the proper service flow.
Careful sharing
Users should avoid sending passwords, OTPs, PINs, or similar credentials through informal channels.
Information Sharing
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. That can include technical support, hosting, communications, or related operational assistance.
If a third-party service is used for a feature, the website may need to pass limited information so the feature can work correctly. The amount of information shared should stay tied to the purpose of the feature.
Third-Party Information
A practical rule is simple: if a service is necessary for the requested function, only the information needed for that function may be shared. Users should still review the current policy details on this page.
Data Security
Reasonable measures may be used to help protect information from unauthorized access, misuse, loss, or improper handling. Security practices can include access controls, operational checks, and careful handling of records within the website environment.
No online system is free from risk. For that reason, users should also take basic precautions on their own devices and accounts. A strong password, careful device use, and attention to unofficial messages can make a real difference.
Security Awareness
If someone asks for your password, OTP, or PIN outside the normal website flow, treat it carefully. A legitimate privacy or support request should not require you to hand over sensitive credentials casually.
Protect access
Keep login details private and avoid reusing weak passwords across different websites.
Watch for unofficial requests
Be cautious if a message asks for sensitive details through a channel that does not look official.
Use trusted devices
Public or shared devices may store browsing traces, so sign out when the session is finished.
Report concerns
If something looks unusual, use the Contact page and describe the issue clearly.
User Privacy Choices
Users may have practical choices around their privacy, even when a website does not offer a formal request form. The most useful first step is to review what information was provided, what was stored in the browser, and what part of the service was actually used.
Review information
Check the details you entered in your account or message before asking for help with any privacy concern.
Manage browser cookies
Browser settings may let you clear cookies, block some storage, or control how preferences are remembered.
Ask for clarification
If you are unsure why a detail is needed, use the Contact page and ask a direct question.
Limit what you share
Only send the information that is needed for the task. Extra details rarely help and may create confusion.
For privacy-related questions, users may refer to the website’s Contact page. If a request concerns account access, include enough context to help identify the relevant issue without sharing sensitive credentials.
Data Retention
Information may be retained for as long as reasonably necessary for the relevant purpose, subject to applicable requirements and operational needs. That can depend on whether the information supports account access, communication, security review, troubleshooting, or a transaction-related record.
Some records may need to stay available for a period after a request is completed. Other details may be removed sooner if they are no longer needed. Retention practices may also change if the service setup changes or if a record is needed for operational continuity.
Retention Note
The site does not state a fixed deletion period here because that would depend on the information type and the purpose for which it was collected. Users should review the current policy information available on the website.
Privacy Perspective for Players
Keep credentials private
Passwords, OTPs, and PINs should stay private, even if a message sounds urgent or official.
Use the right channel
Privacy questions are best handled through the Contact page or the website’s own support flow.
Check before sharing
Before sending an ID, payment detail, or screenshot, make sure it is actually needed for the request.
Review updates
If the website changes its features or handling practices, this page may be updated to reflect the current approach.
Privacy FAQ
1. What information may OKFUN collect?
OKFUN may collect information that is needed to operate the website and support the features a user chooses to use. That can include account-related details, contact details, technical information, cookie data, communication records, and transaction-related information where applicable.
The exact mix depends on how the site is used. A visitor who only browses may leave a lighter technical trail than a registered user who sends a message or uses a feature that requires account access.
2. Why might account information be needed?
Account information may be needed to create access, maintain records, and support service-related requests. It can also help the website keep a user’s settings or activity tied to the correct account.
If account details are incomplete or inaccurate, it may be harder to confirm the request or provide the right assistance.
3. Does the website use cookies?
Cookie use may apply where the website is configured to remember sessions, store preferences, or understand how pages are being used. Cookies can make browsing smoother and reduce repeated steps.
If cookies are limited or blocked in the browser, some functions may not behave as expected. Users can check browser settings if they want more control.
4. What technical information may be collected?
Technical information may include browser type, device type, operating system, language settings, IP address, and log-related data. This kind of information is usually used for operation, troubleshooting, and general site maintenance.
Not every technical detail is always collected in the same way. The exact setup depends on how the website is configured.
5. How may transaction information be handled?
Where payment functionality is available, transaction-related information may be processed as needed to support the requested transaction. That may include records for confirmation, support, or operational review.
The policy does not state a fixed handling method for every transaction because the details depend on the feature being used.
6. Can users ask about their personal information?
Yes. Users may raise privacy-related questions through the Contact page. A clear message helps, especially if the issue involves account access, a message record, or a feature-specific concern.
It is better not to include passwords, OTPs, or other sensitive credentials when asking a question. Share only what is needed to identify the issue.
7. How is information protected?
Reasonable measures may be used to help protect information from unauthorized access, misuse, or loss. That usually means operational controls and careful handling rather than absolute guarantees.
Users should also protect their own devices and keep sensitive account details private. Good privacy often depends on both the website and the user.
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 retention period can differ by data type and by why the information was collected.
This page does not set a fixed retention period unless one is specifically confirmed elsewhere on the website.
9. Can the Privacy Policy change?
Yes. The Privacy Policy may be updated if services, settings, or handling practices change. Users should review the page from time to time to see the current version.
Any change should be read together with the latest policy information shown on the website.
10. Where can privacy questions be directed?
Privacy questions can be directed to the website through the Contact page. If the question involves a specific feature, it helps to mention the page or action involved so the request can be understood quickly.
If you are unsure what to share, keep the message short and focus on the privacy issue itself.
Policy Updates
Privacy practices may change when the website adds features, changes technical settings, or adjusts how a service is run. When that happens, this page may be revised so the information stays aligned with the current setup.
Users should check the page occasionally, especially before sharing account details or using a feature that involves communication or transaction-related data.
Have a Privacy Question?
Review the policy information above and use the Contact page if you need to raise a privacy-related question. If your message concerns account access or a specific feature, include enough detail to help identify the issue without sending sensitive credentials.