BakeSafe Cookie Policy
Contact: bakesafehelp@gmail.com ยท Version v1.0
This policy explains how BakeSafe uses cookies and similar browser or app storage. BakeSafe does not use advertising or analytics tracking cookies.
Essential app cookies and storage
BakeSafe uses essential cookies, local storage, session storage, IndexedDB, cache storage and service worker storage so the app can sign you in, keep your account secure, sync records, call backend services, remember necessary app state and load as an installed PWA. These are necessary for BakeSafe to work, so they do not require optional cookie consent.
Optional support chat cookies
BakeSafe uses Crisp for in-app support chat. Crisp is optional support functionality. BakeSafe asks for chat cookie consent before loading Crisp chat. If you do not allow chat cookies, BakeSafe still works, but Crisp chat will not open on that browser or device.
Cookies and storage we use
| Cookie or storage | Provider | Purpose | Essential? | How long it lasts |
|---|---|---|---|---|
| Firebase Authentication cookies/storage, including browser storage used for auth persistence | Google Firebase | Signs you in, keeps your session secure, and lets BakeSafe load your account on the same browser/device. | Yes | Usually until sign-out, token expiry/refresh, account deletion, or clearing browser/app storage. |
| Firestore, Cloud Functions, App Check and app security storage | Google Firebase / Google Cloud | Protects backend requests, stores/syncs records, and helps prevent abuse of BakeSafe services. | Yes | Varies by token/session; generally short-lived security tokens plus local app state until refreshed, expired, signed out, or storage is cleared. |
| LocalStorage, sessionStorage, IndexedDB, cache storage and service worker cache | BakeSafe / browser | Keeps necessary app state, preferences, offline/PWA assets, update recovery and signed-in app reliability. | Yes | Until the app updates/replaces cached files, you clear storage, sign out where relevant, or the browser/device removes it. |
| Firebase Cloud Messaging token storage, if notifications are enabled | Google Firebase | Lets BakeSafe send reminders and alerts you enable. | Only when you enable notifications | While notifications are enabled or usable, until disabled, refreshed, deleted, or storage is cleared. |
| crisp-client-session-* and crisp-client-* | Crisp | Runs support chat, restores a chat session, keeps messages connected across pages/visits and manages chat connection state. | No, optional support chat | Session cookies and up to 6 months by default, renewed when Crisp chat loads, according to Crisp documentation. |
| bakesafe-cookie-consent-v1 | BakeSafe | Remembers whether you allowed optional Crisp chat cookies so BakeSafe does not ask again on the same browser/device. | Yes, for consent preference | Until the consent version changes or you clear browser/app storage. |
Third parties
Google Firebase and Google Cloud provide essential app hosting, authentication, database, backend and security services. Crisp provides optional support chat after chat cookie consent. Stripe may use cookies or similar technologies on its own checkout and billing pages when you subscribe; those pages are provided by Stripe and are covered by Stripe's own notices.
Changing your choice
You can block or clear cookies and app storage in your browser or device settings. If you clear BakeSafe storage, you may need to sign in again and may be asked again about optional chat cookies. If you refuse optional chat cookies, BakeSafe still works but Crisp chat will not load on that browser/device.
For more information, see the Privacy Policy and Terms of Service.