Cookie & Local Storage Policy
How FileToolz utilizes HTTP cookies, client-side localStorage, and Progressive Web App (PWA) cache storage.
Last updated: October 27, 2026
2. Essential Browser Storage (First-Party)
FileToolz does not require user accounts, passwords, or logins. Consequently, we do not issue first-party authentication session cookies. We use client storage solely for functional operation:
Files you select for conversion, compression, or calculation exist in ephemeral browser heap memory (Blob objects and Object URLs). When you close the browser tab or refresh the page, this data is permanently discarded.
May be used to store lightweight interface preferences (such as dismissing an update banner or recording PWA installation prompt dismissals) so you are not repeatedly interrupted. No personal files are ever saved in localStorage.
3. PWA Service Worker & Cache Storage (Separate from Cookies)
FileToolz features Progressive Web App (PWA) capabilities enabled by a Service Worker (sw.js).
- What is Cached: Only static application code files—including hashed JavaScript bundles, CSS stylesheets, iconography, and the offline fallback page (offline.html)—are cached locally in your browser's CacheStorage container.
- What is NEVER Cached: User-uploaded documents, confidential PDFs, processed output images, and temporary file blobs are explicitly excluded from the Service Worker cache.
- Purpose: To allow FileToolz to load instantly upon repeat visits and remain partially functional even when your internet connection is intermittent.
7. Questions & Contact Information
If you have questions regarding our use of cookies, client-side storage, or data protection practices, please contact us via our dedicated Contact & Feedback Page or review our complete Privacy Policy.