1. Strictly necessary storage
Authentication tokens and security state keep users signed in and protect private routes. These are necessary for the service and cannot be disabled through a consent preference while using a signed-in account.
2. Functional storage
HALISI stores language choice and installation settings on the device. This avoids asking for the same preference on every visit.
3. Offline record storage
When a user saves a field record without connectivity, HALISI stores the description, selected action, identifiers and any chosen evidence photo in the browser's private IndexedDB storage. The queue remains on that device until it syncs or the user clears site data. Shared devices should be locked and signed out after use.
4. Cached application files
On the published app, a service worker may cache application code, styles, fonts and previously loaded pages so the interface can open with poor connectivity. HALISI uses a network-first approach for pages and excludes authentication callbacks from offline caching.
5. Analytics and advertising
HALISI does not currently use advertising cookies or behavioral advertising. We will not place optional analytics cookies before obtaining consent where applicable. If this changes, the preference control and this policy will be updated first.
6. Your controls
You can clear HALISI site data using browser settings. Doing so signs you out and permanently removes any unsynced field records stored only on that device. Browser privacy controls may also restrict storage and offline behavior.
Questions
Contact our privacy and legal team through the contact page. These terms are an international baseline and should be reviewed by qualified local counsel before HALISI launches in a specific country.