Swim tracking guide
Swimming data privacy for families
Tracking a swimmer means holding personal information, sometimes a child's. That is fine and normal, but it is worth being thoughtful about what you store, where, and who can see it.
Direct answer
Swimming data for families can include names, ages, club, race results and sometimes dates of birth. The safest approach is data minimisation: store only what you need, prefer age group over full date of birth where possible, keep it private, and never send child data to marketing tools.
What data is involved
A swim record can include the swimmer's name, club, age or age group, event results and PBs. Some contexts also involve a date of birth or a membership identifier.
Not all of it is equally sensitive. A PB in an event is fairly ordinary, while a child's full date of birth is something to handle with more care.
Why data minimisation matters
The simplest privacy principle is to hold only what you actually need. If age group is enough to make sense of a result, there is rarely a reason to display a full date of birth.
Minimising data also reduces what could ever be exposed. The less sensitive detail a record carries, the lower the stakes if anything goes wrong.
Questions worth asking of any tool
Ask who can see the data, whether anything is public, and whether the tool creates public profiles or leaderboards. For children, public listing is the thing to avoid.
Ask whether swimmer data is shared with marketing or advertising tools. Child data, names, dates of birth and results should not be sent to those services.
How PB Pathway handles it
PB Pathway is private by default, with no public swimmer profiles and no public leaderboards. It prefers age group over full dates of birth in the interface where age group is enough, and it does not send swimmer data to marketing tools.
This is about sensible, practical handling of swimmer and child data rather than any claim of certification. You can read more in the privacy pages, and see how the private dashboard works in the demo.
FAQ
What swimming data do families usually hold?
Names, club, age or age group, race results and PBs, and sometimes a date of birth or membership identifier.
What is data minimisation?
Holding only the data you actually need. For example, using age group rather than a full date of birth where age group is enough.
What should I ask before using a tracking tool?
Who can see the data, whether anything is public, whether it creates public profiles or leaderboards, and whether swimmer data is shared with marketing tools.
Should child swimming data go to marketing tools?
No. Child data, names, dates of birth and results should not be sent to marketing or advertising services.
How does PB Pathway protect swimmer data?
It is private by default, avoids public profiles and leaderboards, prefers age group over full dates of birth where possible, and does not send swimmer data to marketing tools.
Related resources
Why private swimmer profiles matter
Why private swimmer profiles matter for children and developing swimmers, covering pressure, safeguarding-minded design and keeping progress personal.
Private swimming progress tracking
What private swimming progress tracking means, why it suits developing swimmers and families, and how it differs from public profiles and leaderboards.
What does age at 31 December mean in swimming?
A clear explanation of age at 31 December, why it appears in swimming entries and how it affects standards and rankings.
Public rankings vs private swimming progress tracking
How public swimming rankings and private progress tracking differ, what each is good for, and why private tracking often suits developing and younger swimmers.
See how this looks in a private swimmer dashboard.
PB Pathway helps swimmers, swim families and support teams track PBs, race results, standards context and private reports without public swimmer profiles or public leaderboards.