Effective Date: 19 March 2026 — Last Updated: 19 March 2026
This policy explains how Trefnus CMMS uses browser storage technologies on your device. Unlike many web applications, Trefnus CMMS does not use traditional cookies for tracking or advertising. Instead, we use browser-native storage APIs (localStorage, sessionStorage, and IndexedDB) essential to the Application's functionality.
The Application uses the following browser storage technologies:
Persistent key-value storage that remains until explicitly cleared. Used for essential application functionality.
Temporary key-value storage that is cleared when the browser tab is closed. Used for session-level authentication.
A larger-capacity structured database in the browser. Used for storing application data and file attachments.
A browser cache managed by a service worker for offline functionality. Stores application files (HTML, CSS, JavaScript, icons) to enable the Application to work without an internet connection.
| Key | Purpose | Category |
|---|---|---|
licence_activated |
Records whether the licence has been activated on this device | Essential |
licence_user_id |
Stores the authenticated user ID for licence association | Essential |
licence_activated_at |
Timestamp of licence activation | Essential |
licence_last_verified |
Timestamp of last successful licence verification | Essential |
licence_device_hash |
Unique device identifier (randomly generated UUID) | Essential |
cmmsAuth |
Stores hashed local password and setup completion status | Essential |
pwaInstallBannerDismissed |
Records if the user dismissed the PWA install banner (sessionStorage) | Functional |
Additionally, the Supabase authentication library may store authentication tokens and session data in localStorage under keys prefixed with sb-.
| Key | Purpose | Category |
|---|---|---|
cmms_session_authenticated |
Records whether the user has entered the correct local password for this browser session | Essential |
pwaInstallBannerDismissed |
Prevents the PWA install banner from reappearing within the same session after dismissal | Functional |
| Database | Store | Purpose | Category |
|---|---|---|---|
CMMS_FileStorage |
files |
Stores uploaded file attachments (images, documents) associated with assets and work orders | Essential |
CMMS_FileStorage |
appData |
Stores all application data including assets, work orders, contracts, to-do items, settings, and maintenance history | Essential |
The service worker caches the Application's static files (HTML, CSS, JavaScript, icons, fonts) to enable offline access. This cache:
You can manage or delete stored data through your browser settings:
Warning: Clearing browser storage will permanently delete all your maintenance data (assets, work orders, contracts, etc.) and may require you to re-activate your licence. This action cannot be undone. Always export or backup your data before clearing browser storage.
We rely on the following legal bases for using browser storage:
Because we only use essential and functional storage (no tracking or advertising), separate cookie consent is not required under most privacy regulations. However, this policy serves as transparent disclosure of our storage practices.
We may update this policy to reflect changes in the Application's storage practices. Updates will be posted on this page with an updated date.
For questions about this Cookie & Local Storage Policy, contact:
Trefnus
Email: privacy@trefnus.com