Privacy policy

This policy covers the en route iPhone and Android apps, the en route web app at app.getenroute.app, the share link a host can send to people at home, and this website, getenroute.app.

Who we are. en route by hosted/trips is run by SRALL, LLC, 10245 North Allwood Terrace, Citrus Springs, FL 34434, United States ("we", "us"). Questions or requests: hello@getenroute.app.

Signing in. Hosts sign in with a hosted/trips account (accounts.hostedtrips.com), the same account that works on hostedtrips.com, or with a one-time code we email. What that sign-in collects (for example a passkey, or your name and email address from Apple or Google) is explained in the hosted/trips privacy policy. Guests don't need an account: they open the trip with their own invite link or invite code.

Information from hosts

• Account: name, email address, and phone number if you add one.
• Trip details: trip name, dates, places, time zone, itinerary, trip information such as local emergency numbers, announcements, polls, and links you add.
• Places to stay: for each place the group stays, its name, town, address, Wi-Fi details, house rules, notes for guests (for example parking or a door code), and check-in and check-out dates and times.
• Travel in the schedule: for a journey you add, how people travel (for example a bus, then a train), service numbers such as "Bus 36", the towns it goes from and to, where and when to meet, what's on board (toilet, a comfort stop, luggage space, food), and whether tickets are included, to buy, or not needed.
• Images: trip cover image, trip logo, your own photo for "Meet your team", and photos you add to the trip album. If you crop your photo, we also keep the uncropped picture so you can adjust it later; only hosts see it.
• Your team: names, titles, short bios and photos of co-hosts and team members you list, and a team member's email address and phone number if you add them. A team member with an email address gets their own sign-in, and guests' messages and your forwards can reach them. Please list people, and add their email addresses, only with their permission.
• Invites: the email addresses you send guest and co-host invites to, when each invite was sent, and the invite codes (stored only in scrambled form).
• SOS contacts: names and phone numbers of the people who receive a trip's SOS alerts.
• Tickets and documents: photos and PDFs you upload for your guests (for example an entry ticket, which may show a guest's name or booking details), their titles, which guests each one is for, and when each guest was told about it and opened it.
• Scout (optional, for hosts): if you use Scout (scout.getenroute.app) to scout places for a trip, we keep the verdicts, scores, notes, photos and voice recordings you add to each stop, which stops still need booking, and any booking confirmation numbers and booking contacts you save. Only you and co-hosts who can edit the trip see them. Guests, staff and share-link viewers never do. They are deleted with the trip, or when you delete your account.
• Hold to talk (optional): if you use Hold to talk to write an announcement, your phone or browser listens only while you hold the button and turns your words into text in the announcement box. Where your iPhone can do this on the phone itself, it does; otherwise your words are processed by your device's own speech service (Apple on iPhone, Google on Android and in Chrome) under their privacy terms. We never receive or keep a recording of your voice: we only receive the text, and only if you send the announcement. Guests never see this button.
• AI imports (optional): When a host chooses to bring in a schedule, guest list or other details by uploading a file or pasting text, we send that file or text, plus the trip's title, dates and time zone, to Anthropic (Claude), our processor, to draft entries for the host to review before anything is saved. The file or text may include guests' names, contact details and trip details the host chose to include. We don't send any other information we hold about guests. We keep Claude's response for 7 days, then delete it. Under Anthropic's commercial terms, Anthropic may not train its models on this content.
• Guest list: the names, and any email address, phone number, room and pre-trip form details you enter for your guests.
• Messages: messages you send in the group chat and in private threads with guests, and private messages you forward to your team by email.
• Payments (web only, when card payments are switched on): amount, date, status and Stripe's reference for each payment. Card details are entered on Stripe's page. We never see or store your card number.

Information from guests

• Contact details: your name, and the email address, phone number and room your host enters or you provide.
• Host notes: notes your hosts may keep about you to plan the trip, for example whether you're a morning person or what you enjoy doing. Only the trip's hosts see them.
• Pre-trip form: dietary needs and allergies, an emergency contact (name and phone number), your arrival and departure flight details, and whether you want text messages. Dietary needs and allergies may be health information. Please tell your emergency contact that you have shared their details.
• Your profile for "Who's coming" (optional): a profile photo and links to your social media accounts, if you choose to add them.
• Messages and photos: messages you send in the group chat or privately to your hosts or a member of the trip team, and photos you add to the shared album.
• Tickets and documents: when you open a ticket or document your host gave you. A copy is saved on your phone so it opens without signal; it is removed when you leave the trip.
• Trip activity: when you tap "Got it" on an announcement, your answers to the host's polls, and SOS alerts you send (the time and any note).
• After the trip (optional): your rating and feedback, a quote if you tick the box allowing it, and your contact details if you join the host's waitlist for future trips.

Information from everyone who uses en route

• Safety and moderation records: when you agreed to the Terms, reports you send about messages, photos or profiles, and guests you have hidden.
• Push notification token: if you allow notifications, a token from Apple or Google, delivered through Expo, so we can send trip notifications to your device.
• Sign-in and offline storage: the app keeps your sign-in token and a copy of your trip on your device so it works offline. Deleting the app (or clearing the web app's site data in your browser) removes them.
• Technical data: like any website or app, our hosting provider processes technical information such as IP addresses to deliver and protect the service.
• Notification records: a record of the notifications, emails and texts we send (the recipient and the message), so we can confirm delivery and investigate problems. Sign-in codes are hidden in these records.
• Roadmap suggestions: if you send an idea from our roadmap page, we keep your idea, who it's for if you say, and your email address if you leave one. You don't need an account. We use your idea only to consider it. We use your email address to reply to you and, only if you tick the box "Send me en route news", to send you occasional en route news through Brevo. You can unsubscribe at any time from any of those emails. Each idea is also emailed to the en route team at hello@getenroute.app. To stop spam, we count how many ideas come from each network using a scrambled form of the network address. We don't store the address itself.

What en route does not collect: your location, your contacts, or any advertising identifier. en route has no ads and no advertising or tracking tools. We count visits to getenroute.app and the web app with Cloudflare Web Analytics, which uses no cookies, does not identify you and does not follow you across sites. People who open a share link do not need an account, and we collect no personal information from them beyond the technical data above.

How en route uses information

• To run the trip: the schedule, trip information, announcements, polls, messages, photos, "Who's coming" and the share link.
• To email hosts a sign-in code, and to email guest and co-host invites.
• To send push notifications about the trip, and SOS alerts to the trip's hosts.
• To email a team member the private messages sent to them, and the messages a host forwards to them.
• To send text messages to people who opted in, as described under Text messages.
• To show hosts live flight status, if that feature is switched on. Only the flight number and date are sent to the flight-data provider, never your name.
• To keep the community safe: reviewing reports, removing content and removing people who break the rules.
• To take payments on the web, provide support, and meet legal obligations.

We do not use en route information for advertising, and we do not sell it.

Who can see what

• The trip's hosts and co-hosts see their guests' names, contact details, rooms, pre-trip form answers (including dietary needs, allergies, emergency contacts and flights), the notes hosts keep about each guest, "Got it" taps, who answered each poll and how, SOS alerts, feedback, and waitlist entries. Every host on a trip sees every private message on that trip. Hosts can download their waitlist. Hosts are responsible for how they use guest information outside en route.
• Co-hosts and staff. The trip's lead host decides what each co-host and staff member (for example a chef or a guide) can do and see. Staff who are given their own sign-in can, if the lead host allows it, see guests' and the team's names, dietary needs and allergies, emergency contacts, rooms and flights, so they can do their job (for example a chef planning meals). Host notes are shown only to people the lead host allows. Staff don't see guests' private messages to the hosts; they receive by email only the private messages a guest sends to them and the messages a host forwards to them. Team members listed without an email address have no sign-in and receive nothing. Guests never see a team member's email address.
• The trip team's own details. Hosts, co-hosts and staff have the same details as guests: phone number, room, dietary needs, emergency contact, flights, and the notes hosts keep. They can add their own, or a host can add them (for example for a chef who doesn't sign in). Other members of the trip's team can see them, as above. Guests never do, except the phone numbers described below. They are deleted when that person leaves the trip or deletes their account.
• Other guests on the same trip see your name, your "Who's coming" photo and social links if you added them, your group-chat messages and your album photos. For polls, they see the totals only, never who picked what. They do not see your contact details, your pre-trip form or your hosts' notes about you. Private messages are seen only by you and the trip's hosts (and the team member you wrote to, if you chose one).
• Guests see the lead host's phone number, so they can reach the host directly, and the phone numbers on the trip's SOS call list. They see a co-host's or staff member's phone number only if the lead host switches on "Show this phone number to guests" for that person. Guests also see the "Meet your team" names, titles, photos and bios. Guests never see other guests' phone numbers.
• Share-link viewers see the trip name, host names, the towns where the group stays and on which nights, cover image, logo, itinerary and the host's links. For travel in the schedule, they see how people travel, service numbers, the towns and the times, but not where to meet, what's on board or ticket details. The share link never shows rooms, addresses, Wi-Fi details, house rules or notes for a place to stay, phone numbers, guests' names or photos, messages, polls or album photos. A host can replace the link at any time, and the old link stops working.
• The en route team at SRALL, LLC can access trip information when needed to provide support, review reports, keep the service secure, or meet legal obligations.
• When the law requires it, or to protect people's safety or our rights. If our business changes hands, the new owner would take on this policy.

Service providers

en route uses these service providers to run the app. They process information only on our behalf, to provide their service to us.

• Cloudflare — hosting for the app's server, the web app and this website, the database (D1), and photo and image storage (R2).
• Brevo — sending sign-in code emails, invite emails, messages to team members, and moderation report and roadmap suggestion emails to the en route team; and occasional en route news to people who ticked "Send me en route news" on the roadmap form.
• Anthropic (Claude) — drafting schedule, guest list or other entries from a file or text a host chooses to bring in (see AI imports). Anthropic may not train its models on this content.
• hosted/trips (also run by SRALL, LLC) — the shared sign-in at accounts.hostedtrips.com.
• Expo, Apple Push Notification service and Firebase Cloud Messaging (Google) — delivering push notifications.
• Twilio — placing SOS phone calls to hosts who turned them on, and sending text messages to people who opted in.
• Stripe — card payments on the web, when that feature is switched on.
• AeroDataBox (via RapidAPI) — live flight status, if that feature is switched on. Receives the flight number and date only.
• Apple and Google speech recognition — turning a host's spoken words into text when they use Hold to talk. When the phone can't do this on its own, they receive the audio while the button is held; we never do.
• Apple App Store and Google Play — distributing the app.

We require our service providers to protect personal information with safeguards at least as protective as those described in this policy. We do not sell, rent or share en route information with third parties for their marketing or advertising.

Text messages (SMS)

en route by hosted/trips sends text messages only to people who ask for them. Guests opt in by ticking "Yes, text me urgent trip updates" on their pre-trip form. The box is never pre-ticked. Hosts opt in to SOS text alerts by ticking an unticked box for their own phone number while signed in. Nobody can sign up someone else's number for texts. See how people opt in.

Texts are about the trip only: schedule changes, meeting points, reminders from the host, and SOS alerts. We do not send marketing texts. Message frequency varies by trip, and is usually a few texts per trip. Message and data rates may apply.

Reply STOP to any text to stop receiving them, or HELP for help. You can also contact us at hello@getenroute.app.

Full text-message terms: Text messages in our Terms (the same terms are at srall.biz/terms).

We do not sell, rent or share mobile phone numbers or text-message opt-in consent with third parties or affiliates for their marketing or promotional purposes. Phone numbers are shared only with our text-message provider (Twilio) to deliver messages you asked for.

Cookies

Every visitor to getenroute.app sees a choice, with Accept and Decline as equal buttons. You can change it any time from Cookie settings at the bottom of every page.

• Always: one cookie that remembers your choice, for one year.
• Only after Accept: tools that measure visits to this website and show which links bring people here. getenroute.app uses no such tools today, so choosing Accept changes nothing yet. If we add one, we'll name it here first, and it will only ever run after Accept.
• Decline, or a Global Privacy Control signal from your browser, means none of the "only after Accept" tools are used.
• This website's fonts are served from our own site, so no font service sees your visit.

Checking your choice on this browser…

The en route app (including the web app at app.getenroute.app) uses no cookies for measurement, analytics or advertising. The only measurement is Cloudflare Web Analytics, which counts page visits without cookies and without identifying you. It stores only what it needs to work, on your device: your sign-in, your settings and a copy of your trip for when you're offline. The shared sign-in at accounts.hostedtrips.com uses its own cookies to keep you signed in, as explained in the hosted/trips privacy policy.

How long we keep it

• We keep trip information while the trip and the host's account exist, so hosts can look back at past trips. It is deleted when the host deletes the trip or their account, or when a guest leaves the trip and deletes their info (see Deleting your information).
• When a host removes a guest, the guest loses access at once, and their contact details, form answers, flights, profile photo and social links, feedback and waitlist entry are deleted. Messages and photos they already shared stay on the trip unless a host removes them.
• When a message or photo is removed, it is deleted for everyone, including the stored photo file. Any report about it keeps only who reported it, when and why.
• Messages already emailed to a team member stay in that person's email inbox, which we don't control.
• Payment records are kept as long as tax law requires. If the host deletes their account, the name and email address are removed from those records.
• Roadmap suggestions are kept until we've finished with them. They are not deleted automatically. Email us and we'll delete yours.
• Deleted information may remain in our hosting provider's routine backups for a short period before it is overwritten.

Deleting your information

• Hosts: in the app, go to Settings → Delete my account. The app shows what will be deleted before anything happens. Trips you own with a co-host pass to that co-host. Trips you own alone are deleted with everything in them, including photos and files. Your hosted/trips sign-in account is separate; you can delete it from your account page on hostedtrips.com.
• Guests: in the app, go to Info → Leave this trip and delete my info. This deletes your profile, profile photo and social links, pre-trip form answers, flights, the notes your hosts kept about you, poll answers, messages, photos, feedback, waitlist entry, notification tokens and SOS records. Your hosts are told that you left.
• On the web: app.getenroute.app/delete-account explains the same steps and lets hosts delete their account from a browser.
• By email: write to hello@getenroute.app from the email address on your account, or with your name and trip. We complete email requests within 30 days.

You can also turn off push notifications in your device settings at any time, and reply STOP to stop text messages.

Your rights

Wherever you live, you can ask us to show you the information we hold about you, correct it, or delete it. Email hello@getenroute.app from the address you use with us. We may ask you to confirm it's you, and we answer within 30 days.

California residents

You have the right to know what personal information we collect, use and disclose; to delete it; to correct it; and to opt out of its sale or sharing. en route doesn't sell or share personal information, and doesn't use it for advertising. We won't treat you differently for using these rights, and you can use an authorized agent. We answer California requests within 45 days.

Visitors in the EU, UK and Switzerland

We use your information to provide what you and your host ask for (contract), to run and protect the service and keep the community safe (legitimate interests), and, for anything optional such as text messages or website measurement cookies, only with your consent, which you can withdraw any time. You can also ask us to limit or object to how we use your information, or for a copy to take elsewhere, and you can complain to your data protection authority.

International users

SRALL, LLC is based in the United States, and en route guests travel all over the world. en route information is processed and stored in the United States and in other countries where our service providers operate, including on Cloudflare's global network. Where the law requires it, we rely on appropriate safeguards for these transfers.

Children

Children are welcome on trips, but en route isn't meant for children under 13 to use themselves. A parent or guardian uses the app for them, and hosts shouldn't send invites to children under 13. We don't knowingly collect information from children under 13; if you think a child has given us information, email us and we'll delete it.

Keeping it safe

We use encrypted connections, store sign-in codes and invite codes only in scrambled form, and limit who can see personal information. No method of sending or storing information is 100% secure; if something goes wrong, we'll tell you as the law requires.

Changes

If we change this policy, we'll post the new version here and update the date at the top of this page.

Contact us

See also our Terms of use. SRALL, LLC's policy for all its services is at srall.biz/privacy; for en route, this page gives the detail.