Cookie Policy

Last updated: September 21, 2026

This Cookie Policy explains how TipsyBuddy ("we", "us") uses cookies and similar technologies when you visit the TipsyBuddy tracker page (tipsybuddy.app and any page that loads index.html). It also explains your choices and how to change them.

1. We don't set first-party tracking cookies

TipsyBuddy does not set any first-party analytics or advertising cookies of its own. We do not profile you, track your browsing across sites, or sell your data. The only thing we remember is the cookie consent choice you make below, and that preference is stored in your browser's localStorage — not in a cookie.

2. How your consent is stored

When you accept or reject non-essential cookies, we save your choice in localStorage under the key tipsybuddy_cookie_consent_v1. The stored value looks like:

{ "necessary": true, "optional": true|false, "ts": "2026-09-21T12:00:00.000Z" }

(necessary is always true — the page can't work without the hosting and map tiles needed to display it. optional reflects whether you accepted the optional third-party resources such as fonts.) Because this is stored in localStorage rather than a cookie, dismissing or accepting the banner does not place a tracking cookie on your device.

3. Third-party cookies we rely on

The tracker page loads content and functionality from the following third-party providers. These providers may set their own cookies (both during and after your visit) according to their own policies:

• Firebase (Hosting & Firestore) · Google — serves the tracker page and streams live location/venue/ride updates to friends via Firestore. Firebase may set cookies such as firebase / __hsinit and related performance/analytics identifiers.
• OpenStreetMap (OSM) tiles — provides the map tiles shown on the live map. The tile server (tile.openstreetmap.org / tile.khomonia.com style hosts) may set session cookies to balance load and prevent abuse.
• Leaflet (CDN) · unpkg — the unpkg.com/leaflet@1.9.4 CDN delivers the Leaflet CSS and JavaScript used to render the map. unpkg may set first-party cookies for analytics/caching and set the SameSite/__Host- cookies to serve your requests.
• Google Fonts — provides the Outfit and Plus Jakarta Sans fonts used across the site. Google Fonts may set cookies (for example __Secure-ENID-style identifiers) to serve font files; these are only loaded when you accept optional cookies, since fonts are an optional resource.

You should review each provider's cookie policy for details about the cookies they set:

• Firebase / Google Analytics terms
• OpenStreetMap copyright & licensing
• unpkg — npm content delivery
• Google Fonts technical considerations

4. What happens if you reject

If you click Reject, we record optional: false in localStorage and we do not load the optional third-party resources (Leaflet and Google Fonts are not fetched). The page still works, but the live map shows a paused notice and custom fonts fall back to system fonts until you accept. Note that the third-party services strictly required to serve the page (Firebase hosting) are "necessary" and cannot be disabled if you want to use the tracker.

5. How to manage or change your choice

You can update your cookie preferences at any time:

• Cookie banner — on your first visit (when no choice is saved) the banner asks you to Accept or Reject. Choosing again updates the stored preference.
• Cookie Settings — every page footer has a Cookie Settings button. Clicking it clears the saved choice from localStorage and shows the banner again so you can pick differently.
• Programmatically — developers/embedders can call the reset API exposed by cookie-consent.js:

window.TipsyCookieConsent.reset();

This clears tipsybuddy_cookie_consent_v1 from localStorage, updates the footer status text, and scrolls the banner back into view.

6. Do Not Track

TipsyBuddy does not respond to Do Not Track signals in any particular way, because we do not run any first-party tracking. If you do not want third-party cookies, please use the Reject option or your browser's built-in controls to block or delete cookies.

7. Changes to this policy

If we update this Cookie Policy, we'll post the new version here with a new "Last updated" date. Your consent choice is stored per-browser, so a policy update does not override your existing preference.

8. Contact us

Questions about cookies? Open an issue on our GitHub repository: github.com/chartmann1590/TipsyBuddy.

Related: Privacy Policy • Terms of Use