SwingSendLog in

Pilot privacy notice · 12 July 2026

How SwingSend handles pilot data

This notice describes the current self-hosted pilot build. Your coach remains responsible for how they use your coaching information.

What is collected

Coach applications collect contact and workflow information. Player submissions collect name, email, golf profile, goals, notes, consent and uploaded video. Coaches may add feedback, markup, voice notes, messages and payment-status metadata.

Who can access it

The selected coach and authorised members of their workspace can access player cases. The SwingSend pilot operator can access data for hosting, security, support and verified privacy requests. Private upload and lesson URLs are unlisted bearer links: anyone holding a link may be able to open it, so do not forward it unnecessarily.

Storage and retention

This deployment stores application data and lesson metadata in SQLite and uploaded media on local server storage. Real video and voice files are automatically purged after 90 days, configurable by the operator. Coach-authored feedback and case metadata remain until the coach deletes them or a verified access, correction or deletion request is completed. Database backups may retain deleted metadata until the rotating backups expire; raw uploaded media is not included by the built-in database backup routine.

Purpose and sharing

Data is used to assess pilot applications and deliver remote coaching, support and security. SwingSend does not sell pilot data or use it for advertising. SMTP and hosting providers may process data when the operator configures those services; provider details must be supplied by the operator before a production launch.

Who owns a player's swing history

A player's lessons belong to that player: every published lesson stays readable from their own progress link, and they can download a copy of their profile and lesson text at any time from that page — including after they stop working with a coach. A coach owns their own working material: private notes, unsent drafts and unconfirmed assessments are not part of a player's record and are not included. Uploaded video sits under the coach's retention policy and is purged on the schedule above, so a downloaded copy holds the lesson text and links rather than the media. Neither side loses access because the other leaves.

Players you bring are never shown to other coaches

A player who reaches SwingSend through a coach's own upload link, roster import or clip import is recorded as coach-sourced, and is never rendered, counted or linked on a public or discovery surface belonging to any other coach. Only a player who arrived without a coach could ever be offered a choice of coaches, and no path in this product creates one yet. This is not a policy the product merely states: repository.coach_first_guard is the one function every public page passes player records through, this paragraph is generated from that function's own documentation so the two cannot drift apart, and the release gate refuses to pass if a new public page is added that reads player records without it.

Your choices

You can request access, correction or deletion through Support & data requests. Requests are manually verified before disclosure or deletion to protect players and coaches.

Privacy contact: support@swingsend.local