Trust & Safety
How Wagglepost and Shuttlebee handle your families' information, what we send them, and how we keep rides safe.
How your data is protected
Hosted on Google Cloud
The portal runs on Google Cloud through Firebase. Google encrypts the data in transit and at rest.
Everyone signs in as themselves
Families, drivers and staff each have their own account. What you see depends on your role: families see their own children, drivers see their routes, and staff see their organization.
Invites expire
Invite links work for 14 days. After that, the person asks for a fresh one, sent to the same email address.
Bus location only while it's running
Families see the vehicle on the map during the route's run window. Before and after the run, the location is hidden.
Payments through Stripe
Checkout is handled by Stripe. Card numbers go to Stripe, never to us.
What we collect
Only what's needed to message families and run the ride. We don't sell data and we don't show ads.
Families
- Names, email addresses and mobile numbers
- Each child's name, grade, route and stop
- Anything you add to the care card: other caregivers, addresses, emergency contacts, seating needs, drop-off instructions and notes such as allergies
- Messages you send and absences you report
Drivers
- Name, contact details, and the profile photo and bio you add
- Check-ins, pre-trip and post-trip inspections, including inspection photos
Vehicles
- Location from your Samsara or DriverTech account, if you connect one, to show where a route is
Who helps us run the service
| Provider | What for |
|---|---|
| Google Cloud (Firebase) | Hosting, sign-in and the database |
| Twilio | Sending and receiving texts |
| Resend | Sending email |
| Stripe | Payments |
| Samsara or DriverTech | Vehicle location, only if you connect your account |
| Vercel | Hosting this website and its visitor analytics |
Student information
- Children don't have accounts. Parents, caregivers, drivers and staff sign in. Students never do.
- Your school decides who's added. Families join when your staff invite them, not with a public sign-up code.
- Your records stay yours. Staff can export rosters and message history from the portal at any time. To have your organization's data deleted, email us.
- Data-privacy agreements. If your school or district uses a student data-privacy agreement, send it to us and we'll review it.
Texts and emails to families
- Your name comes first. Every text and email starts with your school's name, so families know who is writing.
- Families choose how they hear from you. They can turn email or text alerts off in their portal, and reply STOP to any text to stop texts.
- Service emails are the one exception. Formal notices, such as closures, still reach families by email if they've turned email alerts off, and each time that happens it's logged. They never override a family's choice to stop texts.
- A record of everything. Every broadcast and conversation is kept in the portal, and a copy of each broadcast is emailed to your office.
Full details are in our SMS terms.
Ride safety
For organizations that run vehicles with Shuttlebee:
Before the run
The driver submits a pre-trip inspection and checks in. Dispatch confirms before the route goes live.
At every stop
The driver checks each child on and off. Families of absent children don't get “bus coming” texts.
Absences
When a family reports an absence, dispatch and the driver are told right away.
After the last stop
A post-trip inspection with an interior photo confirms nobody was left on board.
Accessibility
Families don't need an app: everything works by email, text, or a web portal that runs in any browser. We design to the WCAG 2.1 AA guidelines. If anything is hard to use, please tell us and we'll fix it.
Questions about privacy or security?
Email privacy@getshuttlebee.com. Read our full privacy policy.