Crane privacy policy
Effective September 9, 2026
Crane is a collaborative trip-planning application. This policy describes the information the current application uses to provide private accounts and trip workspaces.
Information Crane uses
When you sign in with Google, Crane receives basic account identity such as your account identifier, email address, name, and profile image when Google provides them. Crane does not require permission to read Gmail, Google Drive, Google Calendar, contacts, or photos for authentication.
Crane stores your profile and the content you choose to add: trip memberships, traveler links, destinations and votes, itineraries, research, transport options, bookings, budgets, expenses, shares, payments, invitations, and collaboration activity. Booking and financial details are included only when users choose to enter them.
How information is used and shared
Information is used to authenticate you, show your authorized trips, support collaboration, and operate the planning features. Trip content is available only through trip membership and role rules. Other signed-in accounts do not receive access merely because they have a Crane account. Members of a trip may see content and member information that is relevant to that shared workspace.
Service providers and external links
Crane currently relies on Google for sign-in, Supabase for authentication and PostgreSQL database hosting, and Vercel for application hosting. Maps use MapLibre with OpenFreeMap map tiles and OpenStreetMap attribution. These providers may process necessary technical information and maintain operational or security logs under their own policies.
Users may save links to airlines, hotels, research sources, or other websites. Opening an external link or loading map tiles connects your browser directly to that provider, whose own privacy terms apply.
Your choices
Enter only information you are comfortable sharing with the members of that trip. Trip owners control invitations and membership roles. Leaving a trip removes active access but may preserve traveler and planning history needed for the shared record. Requests about account or trip data should be directed to the person operating the Crane instance or the relevant trip owner.
Changes
This policy may be updated as Crane’s actual features or providers change. The effective date above identifies the current version.