7. Cookie and Browser Storage Notice (Preliminary Working Draft)
7.1 Zero Advertising or Analytics Trackers
BiteShark staging sets zero advertising cookies, zero cross-site tracking pixels, and zero analytics or session-recording scripts. We use only strictly necessary HTTP cookies for authentication/security and functional browser storage for user-requested app features.
7.2 HTTP Cookies Used by BiteShark
| Cookie Type | Attributes & Purpose | Lifetime |
|---|---|---|
Strictly Necessary Authentication Session Cookie (__Host- prefix) |
HttpOnly; Secure; SameSite=Lax; Path=/ (host-only; retains an internal legacy session key name for same-origin session continuity). Stores an opaque random session token matched via SHA-256 against PostgreSQL when you sign in. Never set for unauthenticated public discovery requests. |
14-day sliding window (30-day maximum lifetime), or cleared immediately upon Sign Out. |
Strictly Necessary Age-Gate Cooldown Cookie (__Host-bs_age_gate) |
HttpOnly; Secure; SameSite=Lax; Path=/. Stores only the constant literal value 1 (never a birth date, email, or user identifier) after an under-14 registration attempt is declined, preventing immediate birth-date fishing in the same browser. Server-side network throttling separately uses a minimized, pseudonymous truncated SHA-256 IP rate-limit bucket purged after 24 hours (described in our Draft Privacy Notice). |
15 minutes (Max-Age=900). |
Optional User-Requested Starting Preference Cookie (bs_start_pref) |
SameSite=Lax; Path=/; Secure (on HTTPS). Set only when an unauthenticated visitor explicitly checks “Remember my choice on this device” on the first-visit welcome screen. Stores solely the literal token customer or vendor to select the initial screen on return visits — never an account ID, role, email, location, or tracking identifier, and never consulted for authentication or authorization. Independent of analytics/advertising (none used). Can be cleared anytime from the top-right menu (“Forget saved start preference”) without signing out or clearing saved places. |
90 days (Max-Age=7776000), or cleared immediately when forgotten by the user. |
7.3 Functional Browser Storage & Service Worker
localStorage& IndexedDB (device-local functional preferences, caches & tasting notebook): Stores your saved favorite spot IDs for offline/guest viewing, a cached copy of the public Sonoma County food-spot catalog for resilient loading, optional nearby-alert radius preferences, passkey-offer dismissal state, active pickup pager token references on your device, self-reported Food Passport stamps, and any personal notes/photos you save in the local Dish Notebook (IndexedDB). Date of birth, verification codes, and onboarding evidence files are never written tolocalStorage,sessionStorage, or IndexedDB.sessionStorage(tab-scoped preview, invitation handoff & support draft preservation): Used when an authenticatedAdmin: ModorAdmin: Topenters read-only Customer Preview, Vendor Preview, or audited Act-on-Behalf mode; to temporarily hold a pending single-use invitation reference during sign-in on the same tab; or to preserve an unsent Support & Feedback draft (bs_support_draft_v1) across sign-in or transient network errors; cleared when submitted, manually cleared, exited, or when the browser tab closes.- Service Worker (
/sw.js): Caches core static shell assets (icons, stylesheets, and app scripts) for progressive web app reliability and handles incoming order-ready web-push notifications if push delivery is enabled in the future (push delivery is disabled on staging).
7.4 Managing Cookies & Local Data
Signing out clears your authentication session cookie and revokes the server session immediately. You can clear localStorage, sessionStorage, cookies, and service-worker caches at any time through your browser’s site-data settings (note that clearing site data removes device-only Dish Notebook entries and guest favorites).
[UNRESOLVED — CONFIRMATION REQUIRED] Open Storage & Notice Questions
- Strictly-necessary exemption confirmation: Have privacy counsel confirm whether any jurisdiction targeted for public launch requires an explicit cookie banner when only strictly necessary authentication/security cookies and user-initiated functional storage are used.
- Mandatory re-review before adding third-party scripts: If any analytics tool, error-monitoring SDK, embedded third-party widget, or sponsored-content measurement is proposed in the future, this notice and consent controls must be updated and legally approved before deployment.