Privacy at AthleteXP

Last updated September 30, 2026

AthleteXP is designed for youth hockey development with family-controlled access. This page explains the product’s current privacy practices in plain language.

What we collect

Account information may include a Parent or Coach name and email, or a Player username created by a Parent. Player profiles may include name, birth date, assessments, skill ratings, training activity, XP, goals, rewards, badges, reflections, calendar history, and team participation.

How Player data is used

Player development data is used to provide the journal, calculate progress, display training history, support Parent confirmation, and provide the role-limited Coach features available in the product. AthleteXP does not make Player development data public.

Family and Coach access

Parents and Guardians manage family access. Player sibling visibility is off by default. Coaches receive operational team information needed for team features; private Player development details remain outside Coach views unless the product explicitly shows otherwise.

Billing

Payments are handled by Stripe. AthleteXP stores provider references and subscription state needed to operate billing, but does not store full payment-card credentials.

Data exports

Parents can download a JSON copy of family and AthleteXP data from Family settings. Exports intentionally exclude passwords, active session secrets, payment credentials, provider secrets, and internal security records.

Account and Player removal

Removing a Player from the active family archives the Player so history is preserved and can be restored. Signed-in users can request account deletion from the account screen; the request signs out active sessions and can be cancelled after signing back in while it remains pending. Permanent processing may retain records required for security, billing, fraud prevention, or legal obligations.

Security

AthleteXP uses authenticated role checks, private storage, encrypted network connections, rate limits, short-lived access sessions, and production health monitoring. No system can guarantee absolute security.

Changes

Privacy practices may change as the product evolves. Material changes should be reflected on this page before they take effect for public launch.