Built for the work of football.

Data processing & security

Protect the record without promising the impossible.

Security is shared across the service, its providers, club owners, and every authorized staff member.

Reviewed August 27, 2026

Product controls

  • Authentication and active workspace membership are separate checks.
  • Protected reads and changes are limited by role and scope.
  • Sensitive responses are intended for private delivery rather than public caching.
  • Changes, exports, reports, and destructive actions preserve accountable events.
  • Historical evaluations and reports use revisions instead of silent rewriting.

Customer responsibilities

  • Use individual accounts and never share credentials.
  • Review roles regularly and remove access promptly.
  • Protect downloaded reports after they leave the application.
  • Sign out from shared devices.
  • Report suspected access without including player details in an unsecured message.

Minimization and providers

Collect only what the workflow needs, limit access, and delete information when the need ends. Providers must be verified for purpose, contract, confidentiality, deletion, and incident terms before publication.

Incidents

A written response plan should cover containment, investigation, restoration, documentation, customer coordination, and legally required notification. This page does not promise an unapproved response or notification period.

No absolute guarantee

Reasonable safeguards reduce risk, but no service is completely secure. Encryption, certification, penetration-test, recovery, or availability claims must not be published without evidence.