SagaCookies and storage
Last updated: 2026-10-26.
Saga does not use advertising cookies, tracking cookies, or sell personal data.
The current design choice is intentionally simple: as long as Saga only uses necessary cookies and functional browser storage, we do not show a cookie banner. Instead, we explain on this page which storage Saga uses and why.
1. Summary
Saga currently uses:
- a necessary session cookie to stay logged in;
- local storage for preferences such as language, theme, timezone, and filters;
- session storage for temporary screen status, for example, returning to an appointment or chat context;
- IndexedDB for local cache, such as app data and photo/thumbnail cache, and for offline use;
- native app storage for similar functional app settings on Android.
This storage is necessary for Saga to function properly, securely, and pleasantly.
2. Necessary cookie
| Name | Type | Purpose | Retention period | Consent |
|---|---|---|---|---|
saga_session |
HttpOnly, Secure, SameSite=Lax cookie | Recognizing a logged-in session and securing API requests | When setting, maximum 180 days; deleted earlier upon logout | Not required, necessary for login |
This cookie contains a random session ID. The cookie is not accessible to JavaScript in the browser.
3. Functional browser storage
Saga uses local storage, session storage, and IndexedDB for functional purposes, such as:
- language preference;
- light/dark theme;
- default timezone and recently used timezones;
- excluded vaults in filters;
- onboarding status;
- chat settings, such as whether a language/speech notification has already been shown;
- temporary navigation status, such as returning to a previously opened screen;
- local cache to load screens faster;
- photo and thumbnail cache.
This storage is not used for advertising or tracking across other websites.
Offline use and retention periods
For offline use, Saga stores local copies of available vault data, such as contacts, appointments, tasks, and notes, and associated available files. Changes that have not yet been synchronized are stored locally until synchronization is possible. This data can therefore also be present on the device without an internet connection.
| Storage | Term and cleanup |
|---|---|
| Preferences in local storage and Android settings | No fixed expiration period; remain until they are changed or deleted via browser or device settings. |
| Temporary screen status in session storage | Normally during the browser session; tab restoration may retain this data. |
| App data cache in IndexedDB | After seven days without refresh, a cache item is no longer used as current cache. This does not automatically remove the item from the device. Explicitly logging out clears the app data cache. |
| Photo and thumbnail cache | No fixed expiration period. Explicitly logging out clears this cache. |
| Offline data and not yet synchronized changes | No fixed expiration period. Explicitly logging out deletes this data on the respective device. Upon an account switch, the local offline data of the previous account is cleaned up. |
| Technical browser cache for app files and map images | The browser manages this according to cache settings and available storage space; this cache can be cleared via browser or device settings. |
An expired login session does not automatically delete offline data. As a result, offline reading remains possible; for sending changes, a new valid login session is required.
4. Analytics
Saga currently does not use any advertisement analytics or cross-website tracking. Technical logging and error analysis may occur, but are intended solely for security, stability, and support purposes, not for marketing tracking.
If Saga were to use non-essential analytics or tracking in the future, we would request explicit consent beforehand. You may refuse this consent.
5. Third parties
Saga uses external services for, among other things, payments, email, SMS, maps, AI, voice, and hosting. A connection with a supplier does not automatically mean that they place cookies on your device. Processing and storage of personal data by suppliers are described separately in our privacy statement and the supplier overview.
Examples:
- For Stripe Checkout and the customer portal, you leave Saga and open a payment page from Stripe. There, Stripe may use its own cookies or similar techniques, for example for security and payment processing. See the Stripe Privacy Center.
- When viewing a map, your browser or app retrieves map images directly from OpenStreetMap. In doing so, this service receives, among other things, your IP address and technical request data; the browser may cache map images. See the OpenStreetMap privacy policy. A map request in itself is not proof that a tracking cookie is placed.
- Android WebView and browsers may use their own technical storage.
Saga does not load advertising or marketing cookies on behalf of these suppliers for these functions. Cookies on a separate website of a supplier fall under their own explanation and settings.
6. Manage cookies
Users can delete cookies and local storage via their browser or device settings. This may require users to log in to Saga again, lose preferences, or rebuild the local cache.
If you want to delete the offline data, app data cache, and photo cache on a device, explicitly log out of Saga on that device. To also delete preferences and other technical storage, you can clear website data in your browser, or clear app storage via Android settings. First check if changes have been synchronized: unsynchronized changes are lost when clearing.
Account deletion and clearing device storage are different actions. The account deletion procedure processes the data on our servers according to the privacy statement. This procedure currently does not guarantee that local copies on all your devices are deleted. Therefore, also clear the local storage on each device where you used Saga, especially when a device has remained offline.
Within Saga, we only want to offer settings for choices that have substantive value. No cookie choice is needed for essential login storage, as Saga cannot function properly without this storage.
7. Changes
This Cookie Statement will be updated when Saga introduces new cookies, analytics, or external services.