Your account and home base.
Your sign-in service handles your account email, authentication and recovery. Somewhere stores your name, home city, departure airport, flight budget, direct-flight preference and accommodation country when you provide them. These details make your profile and travel preferences work.
Your name, city and airport appear to the people in your crews. Your sign-in email is used for your account and any email alerts you choose.
Crews, posts and plans.
The app stores crew membership, admin roles, invitations, the posts and plans you create, links, uploaded pictures, comments, reactions, poll votes and interest in plans. Crew membership and each post’s selected audience determine access. Exclusions restrict access to the selected plan or post.
People you share with can copy or forward content. An invitation link can be used to join its crew. Avoid including private information about other people without their permission.
Travel searches and alerts.
A flight or accommodation search sends the route or destination, dates and search preferences to the enabled travel provider. This can include currency, direct-flight preference, guest count and country of residence. Search results, cached quotes and price observations help compare trips and prepare alerts.
The current travel integrations can use Google Flights and Google Hotels results through SerpApi, and Skyscanner or Booking.com when their app-wide connection is enabled. A comparison link opens the provider’s own website; its privacy policy applies there.
Plan and price notifications can be eligible when someone posts in your crew, even if you have not tapped Interested. Your alert switch, email preferences, crew mutes and plan snoozes control the updates you receive.
Optional analytics.
Analytics is off until you accept it in this browser. If you accept, PostHog receives basic page visits, a limited set of feature actions, browser/device information and filtered technical error events. Event data is filtered to exclude account email, names, crew and plan content, private links and invitation tokens. The app does not identify your Somewhere account to PostHog.
Analytics uses page memory for its visitor identifier. Your privacy choice and the SDK’s consent marker can be stored in your browser. The configured analytics endpoint is PostHog’s EU service. Session recording is disabled in this beta.
Change your privacy choice any time. Your browser’s Do Not Track or Global Privacy Control signal keeps analytics off. Declining analytics does not prevent you from using the app.
Services that help run Somewhere.
Somewhere uses Supabase for its current account sign-in, Google when you choose Google login, OpenAI Sites and Cloudflare for app hosting and storage, enabled travel providers for search results, and PostHog for optional analytics. An earlier ChatGPT sign-in can be used to connect an original account. If email alerts are enabled and the sender is configured, a delivery service receives your email address and the alert message.
A complete processor list, the email provider, international-transfer arrangements and retention periods still need to be confirmed for the final notice. An EU analytics endpoint does not establish that every service stores all data only in the EU.
Your controls and app data.
Use Account & Settings to edit your profile and travel preferences, change notifications, withdraw analytics consent and download an app-data snapshot. The snapshot includes your own stored app records and picture file details; it does not contain image binaries, authentication-provider records or infrastructure logs. If a collection exceeds 1,000 records, the export identifies the partial collection.
The complete account deletion and data-request process, including shared crew ownership and provider-held records, is still being finished. Deleting a plan or post uses its existing author controls; turning analytics off stops future collection and does not erase data already received.
You can learn about access, correction, erasure and other data rights in the European Commission’s guidance. You can also contact your data protection authority.
Retention and the final notice.
App records remain stored until removed through available app controls or maintenance. This beta does not yet have a complete automatic account-retention and deletion schedule. Hosting logs, account records, email records and analytics may have separate provider settings.
The final notice needs confirmed operator/contact details, processing purposes and legal bases, provider agreements, exact retention periods, international transfers and a working rights-request channel. This beta explanation will be updated when those details are confirmed.