This page describes how Playmetric processes data. It is not legal advice and it does not claim that Playmetric, a club, or anyone else is “GDPR compliant”.
Last updated 15 September 2026. For a plain-English product page about how we keep children’s data private, see Privacy.
Playmetric is a grassroots and youth football tracker. Safeguarding, security, and data minimisation come before convenience. This policy describes what the product stores and how that data is used, so clubs, parents, and 16+ players can see it.
Playmetric is provided by DX2 Productions Ltd, trading as Playmetric. Card receipts may show the Stripe business name Play Metric. The service runs at playmetric.co.uk.
Questions: contact form or play@playmetric.co.uk.
A club decides what to enter about its squad; Playmetric hosts the software. Adult parents and players aged 16 or over also create their own logins.
We aim to collect only what match tracking needs.
We do not collect address, school, child phones, under-16 emails, extra parent contact emails on the child record, GPS tracks, social handles, medical history, medication, biometrics, or a full date of birth. Parent and 16+ logins use that person’s own email.
There are no under-16 logins. A parent, guardian, or coach adds those players. Players aged 16 or over may create their own login and see only themselves, after a product privacy review accepted on 14 September 2026. Sixteen- and 17-year-olds remain children under the ICO Age Appropriate Design Code.
There are no public youth profiles and no public youth leaderboards. Player pages and photos are login-gated. Server-side deny is the control — hiding a link is not enough.
Parent-only and 16+ views show that person’s own child or own record, not teammate names. Match assistants get minimum match data. Fairness copy stays factual (for example a minutes share compared with the squad), not an ability label.
Photos are optional and off by default. Permission is UNKNOWN, GRANTED, DENIED, or WITHDRAWN. A photo is served only through an authorised GET /api/players/{uuid}/photo after sign-in, the right capability, and GRANTED permission. Files are not published as public image URLs.
Uploads are rewritten so embedded location data is stripped. If permission is denied or withdrawn, the file is deleted and match statistics are kept. Parents can grant or withdraw permission for a linked child; a 16+ player can do the same for themselves. Club Admins can also record permission in Privacy & data after sign-in.
An adult parent or guardian can follow only children linked to their account. They register themselves. Linking to a club still needs a coach to approve the child onto a team.
A 16+ player account is own-record only. Birth year is used as a coarse age gate — we do not ask for a full date of birth to refine it. One player record is one yearly subscription. Linking a parent later does not create a second charge for the same player.
Coaching invites stay adult-only. Do not enter real children’s data into the demo club.
We process data to run the service you asked for: sign-in, squad and match recording, own-child / own-record views, billing, security, and abuse prevention. Optional photos are processed only when permission is granted. This describes how Playmetric processes data. It does not claim that Playmetric or a club is “GDPR compliant”.
We do not sell player lists. Data stays in the signed-in club unless a feature below applies.
Those are the processors the app actually uses. We do not add advertising networks, analytics pixels, or session-replay vendors on youth screens. If that changes, this page should be updated before the new party is used.
Paid club plans are billed per team. Each player record is £5 per year. Checkout uses Stripe’s hosted page — there is no Stripe payment form on match or youth screens.
Playmetric stays the seller on the customer’s receipt (merchant of record). If someone joins through a club’s share link, 10% of attributed team and player subscriptions can be sent to that club’s Stripe Connect account after payouts are set up. That is a club fund, not an affiliate scheme: sharing the link does not pay the person who shared it. Stripe may see the club name and the adult email of the person who sets up payouts — not the squad.
We use a first-party session cookie so you stay signed in (HttpOnly, SameSite=Lax, Secure on HTTPS). Idle and absolute timeouts apply. We do not use advertising cookies.
If you open a club join link, a first-party pm_club_fund cookie (about 90 days, HttpOnly) remembers which club’s fund should receive the 10% share. It is not a third-party tracker.
Match Mode can keep a short offline copy in the browser (IndexedDB): player uuids, display name, shirt, position, fixture, and events. It does not store date of birth, contacts, or medical notes. After a successful sync, queued rows are deleted after a short period. Signed-in Privacy & data includes “Clear offline data” and “Log out & clear device”.
We store first-party usage_events on our servers — for example sign-ins, new clubs, matches started, reports issued, adult registers, and which marketing pages were viewed. Those counts do not include player names, shirts, photos, or child emails. Super Admins can see totals after sign-in. There is no Google Analytics, advertising pixel, or session replay on youth screens.
Passwords use a modern one-way hash (Argon2id where available). State-changing requests use CSRF tokens. Database access uses prepared statements. Content Security Policy and other browser security headers are on. Login, reset, MFA, invitations, and exports are rate-limited. Password reset does not reveal whether an email exists. Audit logging avoids passwords, tokens, and full player dumps.
No website can promise it will never be breached. Club Admins can record incidents in Privacy & data. The app must not auto-decide whether to notify the ICO — that is a human decision.
Club Admins set retention days in Privacy & data. Zero means the app will not auto-delete that class of record. Export files expire after a club-chosen number of days (the software default is 7 days). Those numbers are operational settings, not legal advice.
Host backups can outlive an in-app anonymisation. If a Club Admin anonymises a player, the live record becomes “Deleted Player” and the photo is removed; backups may still hold an older copy until the host’s backup cycle ends. Say so in any club notice you publish.
UK data protection law gives people rights over their personal data, including access, correction, erasure, restriction, objection, and portability. How those rights apply to a child record at a club is for the club and a lawyer to apply in context.
What the software supports today:
To use those rights, contact your club, email play@playmetric.co.uk, or use the contact form. You can also complain to the Information Commissioner’s Office (ICO). We cannot complete a rights request that would show one parent another family’s child.
Production hosting and SMTP are with Hostinger. This repository does not certify a country or a transfer mechanism. Clubs should record the actual hosting location in their own paperwork. Payment data is processed by Stripe according to Stripe’s terms with the payer.
If the product starts collecting more data, adding a new processor, or changing who can see children, this page will be updated. The date at the top is when this policy was last updated.