WarriorIQ legal · draft for counsel review

Service Providers and Subprocessors

This list describes integrations present in the current WarriorIQ code. The final operator must update it to match the actual hosting region, vendor contracts and production configuration.

Policy version 2026-08-24
Draft policy architecture—not legal approval. Final wording, jurisdiction, operator details and effective dates must be reviewed by qualified counsel before public launch. View the launch gate.

1. OpenAI

Optional identity-recovery provider. Selected fight frames are sent only when the user enables the feature and an API key is configured. Purpose: resolving Fighter A/B continuity when local tracking is uncertain. The operator must document the contracted entity, processing location, retention controls and transfer mechanism before production use.

2. Stripe

Optional payment provider. When paid plans are enabled, Stripe receives checkout, account email and billing information and returns signed payment events. WarriorIQ does not store full card details. The contracted Stripe entity and region depend on the operator's account.

3. Hosting and storage

This build processes and stores files on the computer running it. No WarriorIQ cloud host is configured in the code. A public host, CDN, database, email or monitoring vendor must be added to this notice before it receives personal data.

4. Change notice

Material provider changes should be published before they take effect where required, with an updated policy date and a way for affected customers to raise data-protection concerns.

5. Contact and operator

Verified operator, jurisdiction, and monitored support details will be published here before paid public launch.