Skip to content

Retention and destruction policy

Last updated: October 8, 2026

Draft — to be reviewed by a lawyer specialized in privacy law before launch. Periods marked "to be confirmed" depend on legal obligations (tax law in particular) still to be verified.

Principles

  • We keep information only as long as needed for the purpose it was collected for; afterwards it is destroyed or anonymized (no possible link to a person).
  • Destruction is automatic: every day the database computes what has expired (scheduled job) and a server process deletes the files, then records it in the audit log.
  • The shortest periods apply by default; only a paid option chosen by the organization extends retention of original videos.

Periods

InformationRetention periodEnd of retention
Original uploaded video, with all its copies (preview, thumbnails, extracted images, work files, annotation images and clips)30 days after analysis, for every plan (proposal to be confirmed; previously 7 days Discovery and Player premium, 14 days Tournament pass); never-analyzed upload: same period from upload (at least 30 days while analysis is running). Annotation images and clips of a team that agreed to model training: see "Exceptions"files and their older versions at the provider deleted; date recorded (original_deleted_at)
"Keep originals" optionuntil the date paid by the organizationback to the rule above
Viewing copy (HLS)30 days (Discovery), 1 year (Tournament pass, Team), 2 years (Pro, Club), per contract (Institution), from match creationfolder deleted; date recorded (playback_deleted_at)
Viewing copy of an account without an active subscriptionthe later of: 90 days after the subscription ends, or the last plan's periodfolder deleted
Statistics, events, trajectories, rosteras long as the organization's account existsdestroyed with the organization
Player entry removed on requestimmediatelyentry and individual statistics deleted; team statistics remain
Closed organization (account deletion by its only owner)none: immediate destructionall match files, then all of the organization's rows
Deleted user account7-day cancellation window after the request (30 days at most)account, memberships and authentication factors deleted
Database backups7 days at Supabase (longer if point-in-time recovery is enabled); daily encrypted copy outside Supabase: 14 daysautomatic expiry
File backups (server disk snapshots, while videos are stored there)14 days; a destroyed video may therefore remain at most 14 days in a backup, never accessed except to restore after an incidentautomatic expiry
Interrupted uploads (parts sent without completion)7 daysautomatic deletion by the provider
Audit log (video access, exports, settings, destructions)12 monthsautomatic monthly purge
Web server logs (truncated IP address)14 days; system journal: 30 days at mostautomatic rotation
Rights requests (register)as long as needed to demonstrate how they were handled (proposal: 3 years, to be confirmed)deletion
Confidentiality incident registerat least 5 years after the incident became known (to be verified)deletion
Billing records (Stripe, accounting)as required by tax law (to be confirmed, often 6 years)deletion
Transient computing data (frames sent to the GPU, appearance embeddings)duration of a match's processingerased when the job ends

Exceptions

  • Litigation or investigation: information covered by a proceeding may be kept until it ends; the decision is recorded by the privacy officer.
  • Model training (only with the team's agreement): retained images are deleted when the team withdraws its agreement; non-identifying derived data may be kept.

Destruction methods

  • Object or disk storage: objects and their older versions deleted (providers then wipe media under their own procedures).
  • Video metadata: GPS location, device make, model and software are removed from every original video on receipt (lossless copy of picture and sound); only the recording date is kept.
  • Database: rows deleted; backups expire per the table.
  • Founder's computers and devices: no copy of client videos outside the planned environments; secure wiping on disposal.

Technical implementation

Database: retention_sweep() (pg_cron, 04:23 UTC daily), process_due_privacy_requests() (04:41), retention_queue table. Server: python -m ufs.retention, daily timer ufstats-retention.timer (05:00 UTC; --dry-run simulation mode until destruction is enabled). Database backup outside Supabase: python -m ufs.backup_db. See docs/PRIVACY.md and docs/STORAGE-ACTIVATION.md.