Effective date: 9 September 2026 (Asia/Kuching) Operator: Feroce Fitness Centre Sdn Bhd (“Féroce”, “we”, “us”)
This policy explains cookies and similar browser storage used when accessing Féroce OS. Féroce OS is an internal administration platform for authorised Féroce personnel.
Cookies are small pieces of information stored by your browser. Similar technologies, including local storage and session storage, can retain information needed by a website.
Depending on the implementation, these technologies can support sign-in, security and saved preferences.
Féroce OS does not use HTTP cookies. The application authenticates with a token held in your browser's local storage, and no cookie is set by the application, the web server, or any third party.
The verified inventory below identifies the technologies actually used by Féroce OS (verified against the application code, 8 September 2026):
| Storage item | Provider | Purpose | Information stored | Expiry / retention | Essential or optional |
|---|---|---|---|---|---|
| --- | --- | --- | --- | --- | --- |
feroce_token (browser local storage) | Féroce OS (first-party) | Keeps you signed in — the token is sent with each API request | A randomly generated session token only. No member profiles, invoices, payment or other records are stored in the browser. Token ↔ identity mapping exists only server-side | Local-storage retention: the token has no expiry inside the browser — it stays until you sign out, until the server rejects it, or until you clear site data. Server-session expiry (separate): the server-side session behind the token expires after 12 hours and is cleared on server restart or sign-out, after which the stored token is refused | Essential (required for sign-in) |
| Server-side session table (server memory, not browser storage) | Féroce OS | Session lookup for authenticated requests | Token → user reference | 12 hours from login; cleared on sign-out or server restart (in-memory only) | Essential |
No other cookies or storage are used. Specifically, Féroce OS uses no third-party analytics, advertising, tracking, social-media or content-delivery services, and loads no external resources. There is currently no optional storage.
Reserved: the disabled member portal (not reachable in the current phase) would use a separate local-storage key (frt). It is listed here only for completeness — it is not in use while the portal is disabled, and this policy will be updated before it is re-enabled.
Dormant integration: an optional Trainerize API connection screen exists but Trainerize sync is disabled by operating instruction. If ever connected, the API credential is stored server-side only — never in your browser — and would not change this inventory.
We will update this policy when the technologies or their purposes materially change.
All storage currently used by Féroce OS is essential: it exists to maintain your authenticated session. Blocking essential storage may prevent sign-in or disrupt the application.
Optional storage is not currently used. If optional technologies are introduced, they will be separately identified and explained in this policy, and consent will be requested before they are enabled where required. Refusing optional storage will not prevent access to essential administration functions.
You can review, block or delete cookies and other site data through your browser settings.
Deleting site data will sign you out. It does not delete member profiles, invoices, payment records or other records held in Féroce OS — those live on the Féroce OS server, not in your browser.
Where optional-storage controls are provided, you can revisit Cookie Settings to change your choices.
Sign out when you finish using Féroce OS, particularly on a shared counter computer. Do not allow another person to use your authenticated session.
Information connected to an identifiable person is also subject to our Privacy Notice. That notice explains how Féroce handles personal information and how to contact us about it. Privacy Notice published 2026-09-08 (bilingual, PDPA) — see /feroce-os/legal/privacy.html.
Cookie controls do not replace your rights or choices concerning other personal-data processing.
For questions, contact admin@ferocegoldhelloyou.com.
The effective date above indicates the latest published version of this policy.
Storage inventory verified 8 September 2026 against the Féroce OS codebase (replica; code parity with production confirmed by the 7 September audit). Operator: Feroce Fitness Centre Sdn Bhd — confirmed 2026-09-08.