Privacy
Last updated Oct 13, 2026. This is a working draft for Kineo coaching — have a lawyer review it with your waiver and coaching agreement before you take paying athletes.
What we collect
Account email and name; coaching intake answers; health-screen answers and injury notes; training plans and workout logs; payment records you enter (Venmo references, amounts, periods); and technical sign-in data from our auth provider (Supabase).
How we use it
To invite athletes, build and deliver training plans, let athletes log workouts, track who has paid, and keep an audit trail of sensitive coach actions. We do not sell athlete data.
Sensitive health data
Health-screen answers, injury notes, date of birth and emergency contacts are stored separately from general intake where possible. They are not copied into notification emails, analytics, error messages or AI prompts. Access is limited by role-based database rules (Row Level Security).
Who can see what
Athletes see their own published plan, logs and payment history. The coach who invited them can see their coaching data. An admin flag (set only in the database) can access support tools; admin actions are logged. Passwords are never readable by Kineo staff — they are handled by Supabase Auth.
Retention and deletion
Deleting an athlete removes rows tied to them through cascading deletes (intake, health screen, plans, logs, payments). Athletes can request deletion by contacting their coach.
Processors
Hosting and auth: Supabase and Vercel. Email delivery may use a transactional provider (for example Resend) configured in Supabase. Payments happen outside the app (Venmo); Kineo only stores the records you enter.