voyage crew doesn't use tracking cookies, advertising cookies, or third-party analytics. We don't set cookies at all in the traditional sense. We do use your browser's localStorage and sessionStorage to keep voyage crew working — here's exactly what gets stored.
Session storage
voyage:supabase:auth
Your signed-in session token from Supabase. Without it, we'd sign you out every page load. Cleared when you sign out.
Local storage
voyage:currentTrip
A cached copy of the trip you're currently viewing. This lets the trip room render instantly while fresh data loads from the server. Replaced when you switch to another trip.
voyage:itinerary
The generated itinerary for your current trip, so vote and results screens paint immediately without a round-trip to the server.
voyage:votes
Your in-progress votes for activities, dinners, hotels, and nightlife — stored locally while you swipe. Pushed to the server when you submit; cleared if you switch trips.
Third-party resources
When a page loads, your browser may make requests to:
- Supabase — auth token validation + trip data reads
- Google Places (via voyage crew proxy) — venue photos; you never talk to Google directly, we proxy
- Google Fonts — the Fraunces and Inter typefaces
- QR server (api.qrserver.com) — generates the QR code on your invite page
None of these set tracking cookies on our site.
How to clear
Open your browser dev tools → Application → Storage → Clear site data. Or: sign out of voyage crew, which clears the session + the caches listed above.
Questions? Email nejc.marinic09@gmail.com.