Volley Pool

Privacy Policy

Version 3 · Effective October 28, 2026

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.

The short version.
  1. What we collect
  2. Why we collect it
  3. Who can see what
  4. Who we share it with
  5. Where and how it's stored
  6. How we protect it
  7. How long we keep it
  8. Your choices and rights
  9. Children's information
  10. If something goes wrong
  11. Changes to this policy
  12. Contact us
  13. Appendix: ISO/IEC 27001 alignment

1. What we collect

InformationDetailsWho provides it
AccountEmail address; password (we never see it — Google's authentication service stores only a salted hash); whether your email is verified; sign-in times.You
ProfileFirst 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)
HouseholdHome address (street, unit, city, state, ZIP, and map coordinates from the address lookup).You, or a team admin on your behalf
Notes for DriversOptional “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 settingsOnly 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
ReportsIf 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 countsHow many ride requests and claims you made today, used only to prevent abuse.Generated automatically
PlayersYour 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
TeamTeam and league name, activation code, time zone, and who the administrators are.Team administrators
EventsPractices, games and trainings: title, venue name and address, times, drop-off notes.Team administrators
RidesRide 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
InvitationsHousehold invite codes you generate; an email address (and optional phone) an administrator enters to reserve a spot for you.You / administrators
TechnicalRequest 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

2. Why we collect it

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.

InformationVisible to
Your name, phone number and home address; players' namesApproved 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 offerApproved 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 notesOnly 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 ProblemYour team's administrators and league administrators, with your name.
Your passwordNo 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.

5. Where and how it's stored

6. How we protect it

Our security practices are designed around the control framework of ISO/IEC 27001 and 27002 (see the appendix).

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

InformationKept
Account and profileUntil you delete your account (Profile → Delete My Account) or an administrator removes it. We do not delete accounts for inactivity.
Household and playersWhile 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.
ReportsAutomatically deleted 12 months after they were sent.
Notes for DriversUntil you change or clear them, or your household is removed.
Notification settings and device tokensUntil 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 countsAbout three days.
Invite codesExpire after 14 days; expired codes are deleted about 30 days later.
Spots an administrator reserved for a familyUntil claimed, or deleted after 12 months.
Server logsAbout 30 days, then deleted by Google Cloud's default log retention.
BackupsDeleted data can remain in encrypted backups for up to 14 days before it is permanently removed.

8. Your choices and rights

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 themeHow 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.