Your data in OOO.
Transparency notes for the current OOO prototype. This is a product explanation, not a final legal privacy notice.
Information stored on OOO's server
Trip title, destination, dates, budget, organiser name and optional organiser email; traveller names, starting locations/postcodes and travel availability; destination suggestions, votes, date polls and shared Belt itinerary items. Data is stored using Cloudflare D1. Organiser and guest edit tokens are stored in your browser, with token hashes stored server-side.
There is currently no full account system, self-service export or deletion workflow.
Information stored on your device
Recent trip links, organiser/guest access tokens, personal packing checklist, local budget estimates and local shared-expense draft. These use browser local storage and may disappear if you clear browser data or change devices. Expense and budget drafts are not synchronised between travellers.
Third-party services
Nearby airport lookup uses Postcodes.io, which receives the postcode requested from your browser. Experimental road routing uses the public OSRM demonstration endpoint and receives approximate postcode coordinates and airport coordinates only when you enable the feature. Flight research links open Google Flights; destination research may open Google Search. Those services have their own privacy practices.
What we still need before launch
Authenticated trip access, permissions for itinerary changes, stronger one-person-one-vote verification, a proper retention/deletion process, rate limiting, a production routing provider, live flight provider integration, and a legally reviewed privacy notice and terms.