Trust & security

What a club should know before it says yes.

Who we are, whose data it is, where it goes, how it is protected — and how to tell us if you find a problem.

Who we are

Company
4CM, Inc., a Delaware corporation
Registration
Delaware, USA, file number 10715824
Registered office
Northwest Registered Agent Service, Inc., 8 The Green, Ste B, Dover, DE 19901, United StatesFor formal service of documents only — email reaches a person, the postal address does not.
Data Protection Officer
Peter Bull — dpo@4cmcoaching.co.uk

Whose data it is

Your club is the data controller. 4CM is its processor.

Your club decides what is collected about its coaches, players and parents, and why. We hold and process it only on your club’s documented instructions, under the data processing agreement that is part of your club’s agreement with us.

Two small things are ours rather than a club’s: enquiries sent to us from these websites, and the counts of visits to them. For those, 4CM, Inc. is responsible. The privacy notice sets all of this out in section 2.

Where your data goes

The providers that process it, and where.

These are the companies we use to run 4CM. The list is quoted from our privacy notice and checked against it every time the site is built.

Sub-processors, as listed in section 5 of the privacy notice.
ProviderWhat it does for 4CMWhere
SupabaseHosting (database, auth, storage)EU (Frankfurt)
AnthropicAI inference for coaching insightsUS
ElevenLabsSpoken Brain replies — optional, off by defaultUS
OpenAITwo separate things: (a) speech-to-text — transcribing anything you dictate, anywhere in the app, including feedback; (b) spoken Brain replies — optional, off by defaultUS
Voyage AIText embeddings for the knowledge baseUS
SentryCrash reporting (consent-gated)EU/US
ResendTransactional email (account verification, sign-in links, consent notices, data-request delivery, enquiries from our websites)EU (eu-west-1) — underlying AWS SES; SCCs where data reaches the US
CloudflareHosting our websites, running the small piece of code that passes an enquiry to Resend, and counting page views on our websites without cookiesUK + global
Google WorkspaceEmail hosting: messages you send usUS

What each provider receives, and how data that leaves the UK is protected, is in section 5 of the privacy notice.

Security

How it is protected.

  • Data held in the EU

    The platform database — every club’s data — is hosted by Supabase in the EU (Frankfurt).

  • Access enforced in the database

    Row-level security in the database separates data by user, club and team. That rule lives in the database itself, not only in the app’s screens.

  • Locked-down websites

    Our websites are served only over HTTPS, with a strict content security policy and no third-party requests: browsers are told to use HTTPS for a year, and only scripts from our own site may run.

  • Nothing on your device

    Our websites store nothing on your device — no cookies and no browser storage. We count visits on our own server without identifying you.

  • No advertising, ever

    No advertising, no selling of personal data, and no tracking on our websites. That is a rule, not a setting.

The rest of our security controls are listed in section 11 of the privacy notice.

Children’s data shaped the product.

  • No coach-to-child messaging: communication is squad-wide or goes through a parent.
  • Player accounts start at 13+. Younger players are planned for and tracked by their coach, without a login of their own.
  • Player names are replaced with pseudonyms before any request reaches an AI model.
  • A coach sees no player information until the club has recorded their DBS check and FA safeguarding training.

Read how 4CM handles children’s data — the design decisions, the frameworks it is built against, and how to report a concern.

Report a security issue.

If you think you have found a security problem in 4CM or these websites, email security@4cmcoaching.co.uk. Tell us what you found, where, and how to reproduce it.

Please do not access, change or keep anyone else’s data while you look, and give us a reasonable time to fix the problem before you tell anyone else. Our contact details for security researchers are also published in machine-readable form at /.well-known/security.txt.