Privacy Policy
Volley Pool ("Volley Pool", "we", "us") is an app that helps parents on a youth sports team coordinate carpools. Volley Pool is operated by Dave Stoll, an individual in the State of Nevada. This policy explains what we collect, why, where it is stored, who can see it, how we protect it, how long we keep it, and the choices you have. We collect only what the app needs to do its job (data minimization), and we do not sell personal information or show advertising.
- We collect your name, email, phone and home address, your child's name, and the ride information you create. If you turn notifications on, we also keep a device token so we can send them. We also keep a few limited technical and safety items, all listed in Section 1: problem reports you send, daily usage counts used to prevent abuse, a photo-consent preference for each player, and server logs that can include IP addresses.
- We do not collect your device's location, contacts, photos, or advertising identifiers, and the app has no analytics or advertising software.
- Only approved members of your own team can see your name, phone and address. Your saved Notes for Drivers, such as a gate code, are visible only to your household. A note you attach to a ride request goes only to the family you're riding with, and the app shows it to them once the ride is confirmed. A note on a ride offer can be seen by team members who open it, so never put a gate code there.
- Your data is stored with Google Cloud (Firebase) in the United States, encrypted in transit and at rest.
- You can delete your account yourself, in the app, at any time: Profile → Delete My Account.
- What we collect
- Why we collect it
- Who can see what
- Who we share it with
- Where and how it's stored
- How we protect it
- How long we keep it
- Your choices and rights
- Children's information
- If something goes wrong
- Changes to this policy
- Contact us
- Appendix: ISO/IEC 27001 alignment
1. What we collect
| Information | Details | Who provides it |
|---|---|---|
| Account | Email address; password (we never see it — Google's authentication service stores only a salted hash); whether your email is verified; sign-in times. | You |
| Profile | First name, last name, phone number, your role (parent or team admin), and when you accepted these terms. | You (an admin may pre-fill your phone when reserving a spot for your child) |
| Household | Home address (street, unit, city, state, ZIP, and map coordinates from the address lookup). | You, or a team admin on your behalf |
| Notes for Drivers | Optional “access notes” (a gate code, which door) and “other notes” you choose to share (for example, where to meet), up to 300 characters each. Please don't put a child's phone number or other contact details in notes; use a parent's contact details instead. Readable only by your household. | You |
| Notification settings | Only if you turn notifications on: which categories you chose (ride activity; ride requests — off, within 48 hours, or all), and a device token for each phone you turned them on for. Removed when you turn notifications off, sign out, or delete your account. | You |
| Reports | If you use Report a Problem: your message, a copy of any text you flagged, which ride it concerned, your name and the date. | You |
| Usage counts | How many ride requests and claims you made today, used only to prevent abuse. | Generated automatically |
| Players | Your child's first and last name, which household they belong to, and a photo-consent preference (yes or no), which you can change at any time. The app stores no photos and currently has no photo feature; the preference records your wishes in case the app or your team ever uses photos, and nothing would be shown without it. | You or a team admin |
| Team | Team and league name, activation code, time zone, and who the administrators are. | Team administrators |
| Events | Practices, games and trainings: title, venue name and address, times, drop-off notes. | Team administrators |
| Rides | Ride offers (seats, notes), ride requests (which players, pickup or drop-off address, notes), and claims between two households (players, meeting spot, notes, estimated time, status and timestamps). | Parents |
| Invitations | Household invite codes you generate; an email address (and optional phone) an administrator enters to reserve a spot for you. | You / administrators |
| Technical | Request logs kept by Google Cloud (which can include IP address and timestamps), error logs from our server functions, and an installation identifier Firebase assigns to the app on your phone (used to route notifications you turned on). | Generated automatically |
What we do not collect
- Your device's location (GPS). Addresses you type are looked up as text; the app never reads your location.
- Your contacts, photos, microphone, camera, health data, or advertising identifiers.
- Analytics, tracking, or advertising data. The app contains no third-party analytics or advertising software.
- Payment information. Volley Pool is currently free.
2. Why we collect it
- To run the service: create and secure your account, keep teams closed to invited families, and let parents offer, request, confirm and cancel rides.
- To let families contact each other: names and phone numbers are shared inside a team so a parent can talk to a driver before trusting them with their child.
- To show where to meet: addresses are used to display pickup and drop-off locations and to open them in a maps app you choose.
- To keep the service safe and working: verify email addresses, prevent misuse, fix errors, and keep an audit trail of who changed what.
- To meet legal obligations and resolve disputes.
We do not use your information for advertising, profiling, or automated decisions about you, and we do not sell it.
3. Who can see what
Access is limited by role and enforced on our servers, not just in the app.
| Information | Visible to |
|---|---|
| Your name, phone number and home address; players' names | Approved members of your own team and its administrators. Never other teams. |
| Ride requests (without their notes) | Approved members of your own team. |
| Ride offers, including the note on the offer | Approved members of your own team who open that ride, so they can decide whether to accept it. Don't put a gate code in an offer note. |
| A ride claim (the arrangement between a rider's household and a driver's), including the meeting spot and notes | Only the two households involved. |
| Notes on a ride request (for example a gate code) | Only the household that wrote them, until a driver responds; then the two households in that ride. The app shows them to the other family once the ride is confirmed. |
| Notes for Drivers (your saved gate code and other notes) | Your household only — not drivers, not team administrators, not other families. A driver sees only what you choose to put in a specific ride's note, and the app shows it to them once that ride is confirmed. |
| Reports you send with Report a Problem | Your team's administrators and league administrators, with your name. |
| Your password | No one, including us. |
Team administrators can approve families, manage the roster and events, move a person between households, and delete accounts or players. A league-level administrator can do the same across the teams in their league. Administrators cannot read ride claims they are not part of. Administrators can read reports sent by members of their team.
4. Who we share it with
We share personal information only with the service providers needed to run Volley Pool, under their data-processing terms, and when the law requires.
- Google Cloud / Firebase — hosts the database, sign-in, server functions, and this website. Google acts as our processor. Google Cloud maintains ISO/IEC 27001, 27017 and 27018 certifications and SOC 2 reports.
- Apple — on iPhone, address search uses Apple Maps (MapKit): the text you type into an address field is sent to Apple to suggest and validate addresses. Apple also provides the App Store and TestFlight; any diagnostics you opt into sharing with Apple are governed by Apple's policies, not ours.
- Google Play and address lookup on Android — Google Play distributes the Android app; any diagnostics you opt into sharing with Google are governed by Google's policies, not ours. On Android, the Look Up button for a custom pickup spot sends the text you type to Google's address lookup, through Android, to suggest matches.
- Apple and Google notification services — if you turn notifications on, Apple Push Notification service and Google Firebase Cloud Messaging deliver them. The text is generic (for example “A ride needs your confirmation”) and never contains names or addresses.
- Maps apps you choose — when you tap an address and choose Apple Maps or Google Maps, that address is passed to that app at your request.
- Other teams, advertisers, data brokers — never.
- Legal and safety — we may disclose information if required by law or valid legal process, or to protect someone's safety, after reviewing the request.
5. Where and how it's stored
- Data is stored in Google Cloud Firestore in the United States (Iowa,
us-central1); sign-in is handled by Firebase Authentication; server logic runs on Cloud Functions in the same region. - Separate environments are kept for testing and production; production data is not used for testing.
- Because the data is processed in the United States, people using Volley Pool from elsewhere are transferring their information there. The service is intended for teams in the United States.
6. How we protect it
Our security practices are designed around the control framework of ISO/IEC 27001 and 27002 (see the appendix).
- Encryption: all traffic between the app, this site and our servers uses TLS; stored data is encrypted at rest by Google.
- Authentication: accounts require a verified email address. Deleting an account requires you to re-enter your password, which also confirms a recent sign-in.
- Closed teams: joining requires a team activation code or an administrator's invitation, and a family's household must be approved by a team administrator before it can see the team.
- Least privilege: the app can read only what your role allows. Anything sensitive — creating teams and households, confirming rides, deleting accounts, changing roles — can be done only by our server functions, which re-check who is asking. A person cannot grant themselves access.
- Separation of sensitive data: your Notes for Drivers and ride notes live in separately protected records readable only by the people they are for.
- Input validation: every request to our servers is validated for type, size and format before it touches the database.
- Testing: we maintain automated tests that attempt unauthorized access, privilege escalation and malformed or oversized input against our access rules and server functions.
- Backups and recovery: the production database has point-in-time recovery (seven days) and daily backups kept for 14 days.
- Abuse and cost controls: server functions have capped capacity, each person has daily limits on ride requests and claims, and errors are logged and reviewed.
- Vulnerability reports: please email security@volleypool.com (see also our security.txt). We will acknowledge good-faith reports promptly and will not pursue researchers who follow responsible disclosure.
No system is perfectly secure. You can help: use a strong, unique password, keep your phone's software up to date, and share team and invite codes only with people who should have them.
7. How long we keep it
| Information | Kept |
|---|---|
| Account and profile | Until you delete your account (Profile → Delete My Account) or an administrator removes it. We do not delete accounts for inactivity. |
| Household and players | While on the team roster. Deleting your account does not remove your child from the roster; a team administrator manages the roster. Removing a player deletes their record, and, if it was the household's last player, the household's guardian accounts as well (administrators are kept). |
| Rides (events, legs, offers, requests, claims) | Automatically deleted 12 months after the event or ride, a period we keep for safety and to resolve disputes. When an account is deleted, its rides are removed (if it was its household's last guardian) or continue under the remaining guardian. |
| Reports | Automatically deleted 12 months after they were sent. |
| Notes for Drivers | Until you change or clear them, or your household is removed. |
| Notification settings and device tokens | Until you turn notifications off, sign out, or delete your account; a token is also removed when Apple or Google report that the device no longer accepts notifications. |
| Usage counts | About three days. |
| Invite codes | Expire after 14 days; expired codes are deleted about 30 days later. |
| Spots an administrator reserved for a family | Until claimed, or deleted after 12 months. |
| Server logs | About 30 days, then deleted by Google Cloud's default log retention. |
| Backups | Deleted data can remain in encrypted backups for up to 14 days before it is permanently removed. |
8. Your choices and rights
- See and correct: edit your name, phone, address and players in Profile. Ask us (below) for a copy of everything we hold about you. A team administrator may enter your email address, and optionally your phone number and home address, when reserving a spot for your child before you join. We don't contact you ourselves; the administrator sends you the invitation. When you create your account you can see and correct everything entered for you in Profile, and you can ask us to remove it.
- Notifications: they are off until you turn them on. Change or turn them off any time in Profile → Push Notifications (or in your device's Settings).
- Delete: use Profile → Delete My Account, which explains exactly what will happen, or ask us. Deleting your account does not remove your child from the team roster, which a team administrator manages; ask a team administrator or us to remove your child's record. If an administrator removes a household's last player, that household's guardian accounts are deleted as well (administrators are kept). Affected parents are not notified automatically, so a parent who wants to know should ask their team administrator first.
- Object or restrict: tell us if you'd like us to stop using certain information; some information is needed for the service to work.
- Portability: we'll provide your information in a common format on request.
- Complaints: contact us first; you may also contact your local data-protection or consumer-protection authority.
Your rights. We offer these rights to everyone who uses Volley Pool: to access the personal information we hold about you, to correct it, to delete it, to receive a portable copy, and to ask us to limit how we use it. We do not sell personal information or share it for advertising, so there is nothing to opt out of.
How to ask. Email dave@volleypool.com from the address on your account, or use the in-app options above. We confirm it's you by checking that the request comes from the email on the account (and, for anything sensitive, asking you to confirm in the app). A parent may ask on behalf of their household. We respond within 30 days.
If we say no. If we deny or only partly carry out a request, we'll tell you why in writing. You may appeal by replying to that email with the word “appeal” within 60 days. We will review it, with a different person where one is available, and answer within 45 days, and we'll tell you how to contact your state attorney general if you're still not satisfied.
9. Children's information
Volley Pool is for parents and guardians (18 and over) and team administrators. Children do not have accounts and the app is not directed at children. A child's first and last name appears only because a parent or team administrator adds them to the roster so rides can be arranged. We do not collect anything else about children, do not collect it from children, and do not use it for anything except coordinating rides for their team. A parent can have their child's record corrected or removed by contacting a team administrator or us.
10. If something goes wrong
If we learn of a security incident affecting personal information, we will contain it, investigate it, and notify affected people and the relevant authorities without undue delay and as the law requires, describing what happened, what information was involved, and what you can do.
11. Changes to this policy
When we make a material change to this policy, we will tell you in the app before it takes effect and update the version and effective date above. If a change requires your agreement, you will be asked to accept it before you continue. Earlier versions are available on request at dave@volleypool.com.
12. Contact us
Operator and general contact: Dave Stoll, dave@volleypool.com
Privacy requests and questions: privacy@volleypool.com
Security reports: security@volleypool.com
General support: support@volleypool.com
Appendix: ISO/IEC 27001 alignment
Volley Pool's information-security practices are designed to align with the control themes of ISO/IEC 27001:2022 (Annex A) and ISO/IEC 27002. This is a description of our approach, not a certification; our hosting provider, Google Cloud, is independently certified for the infrastructure it operates.
| Control theme | How we address it |
|---|---|
| Policies and roles (A.5.1–5.4) | This policy and the Terms of Use; defined roles (parent, team administrator, league administrator) with separation of duties enforced by the system. |
| Inventory and classification (A.5.9–5.13) | The data inventory in section 1 and the visibility tiers in section 3 classify information by sensitivity (roster-visible, household-private, party-only). |
| Access control and identity (A.5.15–5.18, A.8.2–8.5) | Verified-email authentication; role- and household-based access enforced server-side; privileged actions only through server functions that re-check authorization; invite codes expire; password re-entry (a recent sign-in) required for account deletion. |
| Supplier relationships (A.5.19–5.23) | Google Cloud (hosting, database, authentication, push delivery through Firebase Cloud Messaging and, on Android, address lookup and Google Play distribution) and Apple (address search on iPhone, push delivery through Apple Push Notification service, and App Store and TestFlight distribution) are the only suppliers that handle personal data, under their standard data-processing terms. When you tap an address and choose a maps app such as Apple Maps or Google Maps, that address is passed to the app at your request. That is a handoff you direct, not a supplier relationship, and the maps app's own privacy policy applies. |
| Incident management (A.5.24–5.28) | Section 10; a published security contact; error logging. |
| Legal and privacy compliance (A.5.31, A.5.34) | Data minimization, purpose limitation, retention limits, and individual rights as described in this policy. |
| People (A.6) | Access to production systems is limited to the people who operate the service. |
| Physical (A.7) | Inherited from Google Cloud's certified data centers; no on-premises storage of personal data. |
| Cryptography (A.8.24) | TLS in transit; encryption at rest by Google; passwords stored only as salted hashes by Firebase Authentication. |
| Backup and continuity (A.5.30, A.8.13) | Point-in-time recovery and daily backups of the production database. |
| Logging and monitoring (A.8.15–8.16) | Request and error logs retained by Google Cloud; function errors monitored. |
| Secure development (A.8.25–8.29, A.8.31) | Input validation on every server entry point; automated security tests (access control, escalation, malformed input); separate test and production environments; version-controlled, tagged releases. |
| Data deletion and retention (A.8.10) | In-app account deletion, administrator removal with cascading cleanup, and automatic deletion of ride records after 12 months. |