Cookie
Policy.

This Policy applies when a person visits or uses the Fortune9 website, Wallet, PWA or embedded Live Chat.

It explains the current use of cookies and similar browser technologies for:

• Website delivery, security and traffic management;
• Login, session continuity and saved preferences;
• Advertising measurement and attribution;
• PWA installation, updates and cached website files;
• Web Push subscription and notification delivery; and
• Embedded customer-support conversations.

External websites, payment applications, banks, messaging platforms and game-provider pages may use their own technologies under their own policies.

A cookie is a small text record that a website or related service places in a browser. A cookie may last only for the current session or remain until its expiry date or manual removal.

Fortune9 also uses or may rely on technologies that are not technically cookies, including:

• Meta Pixel;
• Local Storage;
• IndexedDB;
• Browser cache;
• Service workers;
• Push subscription IDs;
• Notification permissions; and
• Embedded-service session records.

In this Policy, “browser technologies” refers collectively to cookies and these similar tools.

Some browser technologies are needed to deliver the website, protect requests, maintain an active session or provide a feature specifically requested by the visitor.

These technologies may be used to:

• Route traffic and load the requested page;
• Protect the website against bots, abuse or malicious traffic;
• Maintain login or Wallet-session continuity;
• Apply security and fraud-prevention controls;
• Remember an immediate website or support-session state; and
• Deliver the PWA files and updates needed for the service to work.

A browser may still allow a visitor to block these technologies, but parts of Fortune9 may then fail to load or operate correctly.

Fortune9 uses Cloudflare to deliver the live website and manage traffic. Depending on the Cloudflare features active at the time of a visit, Cloudflare may place strictly necessary cookies or process technical request information to:

• Identify and reduce automated or malicious traffic;
• Apply security challenges or rate limits;
• Route and optimise website requests; and
• Maintain the integrity and availability of the service.

Cloudflare determines the names and default durations of its own cookies according to the service features in use.

The Fortune9 website or Wallet may use session or preference storage to keep a requested feature working and remember an immediate choice.

Depending on the feature, this may include:

• Login or account-session status;
• Navigation or menu state;
• Language, display or device preferences;
• Notification-prompt status;
• PWA installation or update state; and
• Live Chat session continuity.

Deleting browser data may reset these choices and require the visitor to log in, select a preference, reload files or reconnect to a support session.

Depending on the events configured on the live website, Meta Pixel may receive or infer technical and activity information such as:

• Page or URL visited;
• Date and time of the visit;
• Referring page or advertising source;
• Selected clicks or button events;
• Browser and device information;
• IP or network information;
• Cookie or browser identifiers; and
• Configured conversion or campaign events.

The exact information depends on the Pixel configuration, the visitor’s browser, Meta settings and any tracking protection in use.

Fortune9 does not intend for an account Password, OTP, banking Password, private-wallet key or recovery phrase to be included in a Meta Pixel event.

Fortune9 may use information available through Meta Pixel to:

• Measure visits generated by a Meta advertisement;
• Understand whether a campaign leads to selected website actions;
• Compare campaign, placement or audience performance;
• Reduce ineffective Promotion advertising; and
• Improve future advertising and website journeys.

Meta determines how information processed within its products may be used, combined and retained under Meta’s own privacy and cookie policies.

Fortune9 does not currently use Google Analytics. Meta Pixel is the only confirmed advertising or analytics tracking tool in the current implementation.

Fortune9 uses OneSignal to provide optional Web Push notifications.

According to OneSignal’s current Web SDK information, OneSignal does not use its own cookies for this function. It uses browser technologies including Local Storage and IndexedDB to store client and subscription information.

A Web Push subscription may also involve a service worker, a browser-issued push token or subscription ID, device and browser information, notification permission, and the push services operated by the browser or device platform.

The Fortune9 PWA may use a service worker and browser cache to install the website on a supported home screen, load interface files, check for updates and support Web Push features.

Cached website files may remain on the device until the browser removes them, a new version replaces them or the visitor clears site data.

Fortune9 account services and games still require an internet connection. A cached page or interface file does not make account, payment or game functions available offline.

Clearing site data may remove cached files, reset the installed PWA’s website state or create a new Web Push subscription when the visitor later subscribes again.

Fortune9 Live Chat is embedded directly in the website rather than opening only as a separate external page.

The embedded chat may use a cookie, session identifier, Local Storage or similar technology to:

• Open and maintain a support conversation;
• Associate messages within the same session;
• Remember the chat window’s immediate state;
• Reduce spam or abusive requests; and
• Support delivery and troubleshooting.

Blocking all browser storage may cause Live Chat to restart, lose its current state or fail to open. Members must never send an account Password, OTP, banking Password, private-wallet key or recovery phrase in Live Chat.

Fortune9 does not apply one fixed expiry time to every cookie or similar technology.

• Session technologies may expire when the browser or session closes;
• Persistent technologies may remain until their default expiry, replacement or manual removal;
• Meta Pixel and Meta cookies follow the applicable Meta defaults and settings;
• Cloudflare cookies follow the defaults for the Cloudflare feature that placed them;
• OneSignal browser data follows the OneSignal SDK, browser-storage and subscription lifecycle; and
• Live Chat storage follows the active chat implementation and session requirements.

Provider defaults may change. The external policy links on this page provide the latest provider-controlled details.

Most browsers allow a visitor to view, delete or block cookies and site data. A visitor may also:

• Enable available tracking-prevention or advertising-tracker blocking;
• Clear cookies, Local Storage, IndexedDB and cached site data;
• Reset or block Fortune9 notification permission;
• Remove the Fortune9 PWA from the home screen; and
• Review Meta’s own advertising and Cookie controls.

Blocking Meta Pixel should not normally prevent access to core Fortune9 account, payment or game functions. Blocking all cookies or site storage may affect login continuity, preferences, PWA updates, Web Push or embedded Live Chat.

Settings differ between Chrome, Safari, Edge, Firefox and mobile operating systems. Members should follow the current instructions provided by their browser or device.

Fortune9 may update this Policy when it changes a Cookie, Meta Pixel event, advertising tool, Cloudflare feature, OneSignal configuration, PWA function, Live Chat implementation or user-control method.

The latest version will be published on this page with its updated date. If Fortune9 later introduces an on-site Cookie banner or preference centre, the available choices and operation of that tool will be added to this Policy.

Visitors should review the current version when a new privacy notice appears or a significant website feature changes.