1. Storage we use
Bodhi may use identity-provider session storage, workspace context, legal-bundle preflight, theme/language/accessibility preferences, PWA update state and user-initiated offline draft storage. Exact cookie names may be controlled by the configured identity provider.
2. Necessary authentication
Authentication storage allows verified sign-in, token refresh and logout. Blocking it may prevent the Service from working. Bodhi does not intentionally store provider API keys or client document content in browser cookies.
3. Preferences
Theme, contrast, language and reduced-motion preferences may be stored locally and in the account. These are not used for advertising.
4. PWA CacheStorage
The service worker caches public application shell files only. Routes beginning /api/ or /auth/, authentication callbacks and tenant responses are network-only. Logout requests cache clearing.
5. Offline drafts
Only explicitly supported drafts are stored in a tenant/user-keyed IndexedDB database and labelled LOCAL_DRAFT_NOT_SYNCED. A local draft is not submitted, posted or backed up. Logout removes the draft database. Anyone with access to an unlocked device/browser may be able to access local data; use trusted devices.
6. Analytics and changes
No advertising or cross-site behavioural analytics cookies are part of the current Service. If optional analytics are introduced, the provider, purpose, duration and consent control will be disclosed before activation.
7. Controls
You can clear browser storage or use logout. Clearing storage may sign you out and delete unsynced drafts. Browser privacy modes can limit PWA/offline functionality.