גרסה בעברית · Request account deletion
Privacy Policy — Rondo
Last updated: November 2026
Rondo is an app for parents to coordinate rides to children's activities. It is intended for adults (18+). Child profiles are created and managed by a parent, except a first-name-only guest entry a group admin can add — see "Children" below.
What we collect
- Account details: name and email at sign-up
- Phone number: optional, so parents in a group can contact each other
- Usage data: practice schedules, driver assignments, swap requests, and ride offers you create
- Location: only with your permission.
- Drivers: when you mark "on my way" for a ride, your location is shared with group members until the ride ends. While that sharing is on, our servers compare the driver's location with the child's location during the ride, or with the family's single home pin, only to decide whether to send a "ride almost here" notification. That comparison is not stored as a new location history.
- Children (Live ETA): when a parent enables Live ETA, the child's device shares location — including in the background, even when the app is closed — only during the ride window, so parents can see an estimated arrival time.
- Place search: if you have already allowed location for the app, a place search may include your approximate area (rounded to roughly 1 km granularity) so nearby places come first. The app never asks for permission just for this, and the area is not stored.
- Contacts: with your permission, contacts access is used only to fill in a group member's or child's details from your address book. The app does not upload or store your address book.
- Calendar: with your permission, the app adds rides assigned to you and reminders to your device's calendar.
- Google Calendar (optional, Premium): if you choose to connect Google Calendar, you sign in with Google and let Rondo create and manage only a dedicated calendar named "Rondo" that Rondo creates for you. Rondo cannot see your other calendars or events. We store an encrypted Google refresh token and the IDs of the events we created, and we send the details of the sessions you chose (title, time, location and reminders) to Google Calendar so it can create those events.
- Push token: to send you notifications about swap requests, schedule changes, and get-ready ride reminders, be-at-the-door reminders, and driver share reminders.
- Verification emails: to confirm your email address at sign-up, or to let you sign in with a one-time code, we send a short code to your email address via a third-party email delivery service (Resend).
- Analytics: anonymous usage events (e.g. "swap requested") via PostHog, stored in the EU. The only identifier is the internal user ID; no names, emails, or content are sent. No PostHog usage analytics are collected from child accounts.
- Ad measurement (Google Analytics for Firebase, Android, at sign-up only): on Android, only on the device where a parent confirms the email address of a newly created account, the app uses Google Analytics for Firebase (Google) to measure whether our ad campaigns lead to sign-ups. Collection is turned on at that moment and records Firebase's automatic app events (such as first open and session start) and one custom event, "sign up". Collection stays on for about a day after that sign-up and is then turned off for good on that device; it is turned off while the app is open, or the next time the app is opened. When the app is next opened after that day, Firebase may still send one automatic app-open event before collection is turned off. Signing in to an existing account never turns it on, and deleting the account ends it. It uses Firebase's app-instance ID and an approximate location (country or region, estimated by Google from the network address); no name, email, phone number or content is sent, and no Advertising ID is collected. The data is shared with Google Ads for ad measurement. It is disabled for confirmed child sessions: when a child's device is paired or a child account signs in, collection is turned off, the app-instance ID is reset and any open sign-up measurement on that device ends for good. There is no in-app switch for this, because collection only happens around sign-up; for questions or requests write to support@rondoride.app, or delete your account (see "Data deletion").
- Approximate country (service logs): when the app contacts our servers, our hosting provider (Google Cloud) may tell us which country the request came from, estimated from the request's network address. We record only that two-letter country code (e.g. "IL") in our service-health logs, to see where the service is used and to spot outages. These log entries do not include your name, email, or user ID, and we do not record your city, precise location, or IP address in them. This is separate from the GPS location described above. It applies to every device that uses the app, including a child's device, and is not used for advertising.
- Troubleshooting diagnostics (child's device, only on a parent's request): a child's device keeps a short technical Live ETA log on the device for about 3 days: when a background start was scheduled or ran, whether a permission or setting blocked it, and whether location updates reached our servers. It never includes locations, names or message content. It leaves the device only when a parent submits a problem report and keeps "Include diagnostics" on. The device then sends that log and a summary of its settings (permission states, battery optimization, notification permission, app version, and device type — Android or iPhone), and we attach it to the parent's report in our private issue tracker. The child's user profile may also store device type and notification permission so a parent report can show them even when the phone does not answer the diagnostics push.
- AI features (Anthropic): some features use Anthropic's AI service (Claude). They run only when you start them, and only the content listed here is sent:
- Reading a schedule from a message: the text you paste, and the content of schedule links in it (league website, Google Drive or a PDF) that the app reads for you.
- Reading a schedule from a file: the PDF or image (a screenshot or a photo of the page) you choose, and the team name you enter.
- Importing members (group admins): the names and phone numbers you paste.
- Swap message draft: your name, the session date, the group name, the reason you typed, and your gender if saved on your profile, so it can draft a WhatsApp message you can edit before sending.
- Fairness report (group admins): the display names of the group's members and how many pickups and drop-offs each did in the period.
- Problem reports: the title and description of a report you submit are checked by Anthropic's AI to filter out spam before the report reaches our issue tracker. Screenshots are not sent to Anthropic.
- Anthropic processes this content as our service provider. Under its commercial terms, content sent through its API is not used to train its models and is deleted automatically within 30 days. Exceptions: content flagged as violating its Usage Policy is kept for up to 2 years (classifier scores for up to 7 years), or longer if the law requires.
- AI results can be wrong, so check them before you save or send them. You can report a swap draft or fairness summary that looks wrong with Report this text.
- Before pasting or uploading, remove personal details that aren't needed, such as phone numbers or other children's names.
How we use this information
- Showing the ride schedule to group members
- Sending notifications about swap requests, schedule changes, and get-ready ride reminders, be-at-the-door reminders, and driver share reminders
- Coordinating rides between parents in a group
- Adding rides to your Google Calendar, if you connect it
- Showing live location and estimated arrival (Live ETA) to group members during an active ride
- Reading schedules and member lists, and drafting swap messages and fairness summaries with AI, when you ask for it
- Screening problem reports for spam
- Improving the app based on anonymous usage data
- Measuring whether our ad campaigns lead to sign-ups (Android, at sign-up only)
- Monitoring that the service works reliably (service logs, including approximate country)
Children
- The app is intended for parents. A child profile is created by a parent inside the app, and a child's device joins only via a pairing code issued by the parent (or, for a guest kid, by a group admin — see below).
- Children cannot sign up on their own; a child's device signs in only with a pairing code, issued by the parent for a parent-created profile or by a group admin for a guest entry.
- Guest kids: when a child's parents don't use the app yet, a group admin may add the child to the group roster by first name (and optionally a last initial) so drivers know whom to pick up. No location is shared and no PostHog usage analytics are collected for the child. An admin may connect the child's phone with a short-lived code so it can see the schedule, get and confirm pickup times, and see drivers on the map; the phone never shares its own location, and the admin gets no access to it. The admin can send the parent a single-use link; a parent who claims it manages the child like any child profile from then on. The phone's push token is stored only to deliver schedule and pickup-time notifications. The phone is signed out when the guest entry is deleted (see Data retention) or a parent takes over, and the parent can pair it again.
- A child's location is shared only when a parent has enabled Live ETA, only during the ride window, and only with the parents in the group. The child's device shows an explanation and asks for permission before location sharing starts.
- No PostHog usage analytics are collected from child accounts.
- Google Analytics for Firebase is disabled for confirmed child sessions. When a child's device is paired or a child account signs in, the app turns collection off, resets the app-instance ID and ends any open sign-up measurement on that device for good.
- AI features: the AI features under "What we collect" are started by parents and group admins. A child's device does not use schedule reading, member import, swap drafts or fairness reports. The child-profile data the app holds (pairing, Live ETA location, diagnostics) is never sent to Anthropic. A schedule, member list or report you paste may contain names, so please leave out children's personal details that aren't needed. A problem report sent from a child's device is screened the same way as any other report.
- A child's device can also send technical troubleshooting diagnostics (no locations or names) when a parent asks for them with a problem report — see "Troubleshooting diagnostics" under "What we collect".
- A parent can at any time remove the child from a group, unpair the device, or permanently delete the child profile from Settings → Manage children.
Data retention
- Account data is kept for as long as the account exists.
- Location shared during a ride is stored on that ride's record and is deleted together with the ride, the group, or the account.
- Screenshots attached to a bug report are automatically deleted after 90 days.
- Raw Cloud Logging service entries, including the approximate country field, are deleted automatically after 30 days. Aggregated monitoring metrics derived from those logs may retain country totals for longer.
- Diagnostics requests are deleted from our servers after 7 days. The on-device Live ETA log keeps about 3 days. Diagnostics already attached to a problem report stay with that report in our issue tracker.
- Pending invites and requests that are never approved expire and are deleted automatically.
- Google Calendar connection: the encrypted token and event IDs are kept until you disconnect Google Calendar in Settings or delete your account. Events already created stay in your Google Calendar unless you choose to delete the Rondo calendar when disconnecting.
- A guest kid entry is kept until a group admin removes it, a parent claims it, or the group is archived or deleted. If the admin who added it leaves the group, it passes to another admin; it is deleted if no admin remains. Unused claim links expire after 7 days. The guest's sign-in record and phone session are deleted with the entry.
- AI features: we keep only the results you choose to save (for example imported sessions or members). For each AI request we also keep a usage record (feature, model, size and cost — never the content you sent) linked to your user ID, for cost and abuse monitoring.
Sharing information
- Personal information is never sold to third parties.
- Android, at sign-up only: data from Google Analytics for Firebase is shared with Google Ads, to measure whether our ad campaigns lead to sign-ups. It contains no name, email, phone number or content.
- Details (name, phone, location during a ride) are shown only to members of your own group.
- Service providers that process data on our behalf:
- Firebase (Google) — authentication, data storage, notification delivery, and service logs
- Google Maps Platform — place search and arrival-time estimates (the relevant location is sent to Google for the calculation)
- PostHog (EU) — anonymous usage analytics
- Anthropic — the AI features you start (reading schedules from messages, links and files, member import, swap message drafts, fairness reports) and spam screening of problem reports
- Expo — delivering push notifications to your device
- Resend — delivering email verification and sign-in codes to your email address
- GitHub — our private issue tracker, where problem reports and attached diagnostics are stored
- Google Calendar API (Google) — only if you connect Google Calendar: creating and updating events in the Rondo calendar
Security
Data is stored on Firebase servers with defined security rules — only members of a group can see that group's data. Sensitive operations (joining, deleting, pairing a child) run server-side with permission checks.
Data deletion
- You can leave a group at any time from Settings.
- Parents: permanently delete your account from Settings → Delete account. This removes your profile from every group and cannot be undone. If you created child profiles, delete those first. Past rides may still show the name that appeared on them.
- Children: a parent deletes a child profile from Manage children; a child who still has an older account they created themselves (before independent kid sign-up was closed) can delete it from Settings.
- Guest kids: a group admin removes the entry from the Admin panel, which also signs out its phone; a parent can also ask us to delete it using the contact below.
- Google Calendar: disconnect at any time from Settings → Calendar. Rondo then revokes its Google access and deletes the stored token, and can also delete the Rondo calendar. Deleting your account does the same (the calendar itself stays in your Google account). You can also remove Rondo's access from your Google Account settings.
- Request deletion outside the app: carpool-f22db.web.app/delete-account.html
Contact
For privacy questions or data-deletion requests: support@rondoride.app