1. Necessary storage
- Supabase authentication cookies maintain a secure signed-in session and recovery flow.
- Local storage may remember guest saved places, anonymous session continuity, offline/PWA state and interface choices on that device.
- Security and load-balancing storage may be used where necessary to protect and deliver the service.
2. Essential analytics
GoJB records minimized events needed to understand route health, feature use, redemption integrity and demand gaps. Event properties must not include raw free-text searches, email addresses, phone numbers, precise coordinates, secrets or other direct contact details.
Anonymous identifiers are hashed or device-local where feasible, cohorts are thresholded, and merchant reporting uses aggregate directional counts.
GoJB does not use email-open tracking. Delivery, bounce, complaint, unsubscribe and privacy-safe first-party link/action attribution may be recorded using campaign, message and entity identifiers without placing email addresses or message bodies in analytics.
3. Optional technology
Non-essential analytics, advertising pixels, cross-site profiling and marketing cookies are not enabled in the current MVP. If introduced, they will require a clear prior choice, remain off when refused and be described here before use.
4. Your controls
You can sign out, clear site data through browser controls and use GoJB as a guest for public discovery. Clearing local storage removes device-only guest saves and may require signing in again. Necessary storage cannot be disabled while using the authenticated service.