1. Controller and contact
Verified controller and privacy-contact details must be published before paid public launch. The current launch gate remains visible in the Legal Center.
2. Data WarriorIQ processes
Depending on how the service is used, WarriorIQ processes account email and password hash; athlete profile text and optional media; fight video and visible people; boxes selected for Fighter A/B; pose, tracking, event candidates, reports and scorecards; optional accuracy-lab labels; plan, usage and payment-event metadata; coach assignments and private share tokens; consent/acceptance records; browser session or guest identifiers; and limited security/diagnostic information.
WarriorIQ does not need a fighter's real-world identity to analyse a video. Full card details are not stored by WarriorIQ when Stripe-hosted checkout is used.
3. Purposes and legal bases
- Provide the requested service: upload, analyse, replay, save, share and delete footage and reports; generally necessary to perform the user agreement.
- Secure and operate the service: authentication, access control, abuse prevention, fault diagnosis and allowance enforcement; generally legitimate interests and, where applicable, legal obligations.
- Billing: create checkout and record successful subscription events; contract and legal obligations.
- Optional model improvement: export pose-feature sequences from deliberate corrections only after the signed-in user enables the separate profile setting; consent, which can be withdrawn for future exports.
- Optional external identity recovery: send selected frames to OpenAI only after the upload-time opt-in and only when configured; consent for that optional processing.
The uploader is responsible for having an appropriate legal basis for identifiable people in the footage. Consent is not always the only possible basis, and an upload checkbox does not cure unlawful recording or disclosure.
4. AI, recipients and transfers
Local computer-vision models analyse the footage. OpenAI may receive selected frames only when external recovery is explicitly enabled. Stripe receives checkout and billing data only when payments are configured. A public hosting, storage, email, monitoring or content-delivery provider is not configured in this local build; any future provider must be added to the provider list and covered by appropriate contracts and transfer safeguards.
WarriorIQ does not sell fight footage or use it for targeted advertising. Private seven-day report links exclude the original video and can be revoked, but anyone holding a live link can read that summary.
5. Retention and deletion
Guest video and analysis files are temporary and automatically removed after 2 hours. Original videos saved to an account are scheduled for automatic deletion after 30 days; generated reports may remain until the user deletes an analysis or account. Users can delete a video earlier without deleting its report. Share links expire after seven days or earlier revocation. Production backups and any narrow legally required records need a reviewed schedule before launch.
6. Your privacy choices and rights
Signed-in users can download an account-data copy, remove individual fights, revoke report links, turn future model-training exports off, and delete the full local account. Depending on location, users may also have rights to access, correct, erase, restrict or object to processing, receive portable data, withdraw consent, and complain to a supervisory authority. Identity may need to be verified before a request is completed.
WarriorIQ does not make solely automated decisions that produce legal or similarly significant effects. Scorecards are automatic training estimates, not official decisions.
7. Children and fight footage
Standard accounts are limited to people aged 18 or older for the initial public launch. Junior athlete accounts are not enabled. An adult uploader may process junior fight footage only with all required rights and appropriate parent or guardian permission. A future junior-account programme requires reviewed age assurance, verifiable guardian approval, data minimisation and safeguarding procedures; the database is prepared for that later status.
8. Changes
Material changes receive a new policy version and, where appropriate, a renewed acceptance request. The effective version is shown at the top of this page and in saved acceptance records.