Junior Football Privacy: What Happens When a U9s Post Goes Up Without Consent

Clubpost owns the consent toggle. MatchDesk owns youth-safe names. Nobody has built the incident playbook. Here's what happens when a U9s post goes up without consent — and the next 48 hours.

The Two Entrants Who Own Privacy

In 14 cycles of competitor sweeping, only two entrants have addressed children's privacy in grassroots football:

Clubpost (clubpostapp.com)

Phone-first graphics app. Per-match, in-app. "Posted before the final whistle has stopped ringing." 1,000+ template/style combos. 3 sponsor slots. Portrait/square/story output.

The wedge: children's privacy by design. Consent toggles per player. Initials-only mode. Scores never leave the phone. No server upload.

It's aimed at the junior coach. It's a compliance story disguised as a features list. And it's the first entrant in 13 cycles to claim this lane.

MatchDesk (matchdesk.app)

Written match reports. £20/month. Per-match, on demand. "Before you leave the ground." AI match report, manager reaction, four social posts.

The wedge: youth-safe display names from U12s upwards. First name and initial only. Publishing safeguards built into the report generator.

It's the first sub-£50 entrant in the written lane. It undercuts our £199 retainer by 90%. But it writes the report — nothing between fixtures, no graphics, no sponsor proof.

Two entrants. Two privacy features. Zero incident playbooks.

What Happens When a U9s Post Goes Up Without Consent

It happens more often than anyone admits. A well-meaning volunteer takes a team photo. Posts it to the club's Facebook page. Tags the kids by first name. Doesn't check consent.

The post gets 50 likes. Parents share it. The club's page grows.

Then a parent messages: "I didn't consent to my child's photo being posted. Please remove it."

Now what?

The Next 48 Hours: The Incident Playbook

There is no playbook. No competitor has built one. Here's what should happen:

Hour 0-1: Take It Down

• Remove the post from every platform. Facebook, Instagram, X, website. Everywhere it was shared.
• Don't edit it. Don't crop it. Don't blur faces. Take it down.
• Screenshot the post before removing it. For your own records. In case you need to explain what happened.

Hour 1-4: Contact the Parent

• Call the parent or guardian. Not email. Not DM. Call.
• Acknowledge what happened. Don't make excuses. "I posted a photo of the team without checking consent. I've taken it down. I'm sorry."
• Ask if they want anything else — a written apology, a note to the committee, a change to club policy.
• Document the conversation. Date, time, what was said, what was agreed.

Hour 4-24: Document and Review

• Write a short incident report. What was posted. When. By whom. What consent was or wasn't in place. What you did about it.
• Send the report to the club committee. Not as a scandal. As a process review.
• Review your consent process. Do you have a consent form? Does the volunteer who posts know about it? Is it checked before every post?

Hour 24-48: Fix the System

• Implement a consent toggle. Clubpost has one. Build one. Even a simple spreadsheet: player name, parent name, consent given (Y/N), date.
• Switch to initials-only mode for U12s and below. First name and initial. No surnames. No full identification.
• Add a pre-post checklist. Before any post goes live: "Have all featured players' parents consented?" Yes/No. If No, don't post.
• Train the volunteer. Show them the checklist. Make it part of the Saturday SOP.

Why Nobody Has Built This

Clubpost owns the toggle. MatchDesk owns youth-safe names. But neither has built the incident playbook because the incident playbook isn't a feature — it's a process.

Features are easy to sell. "Consent toggle included!" "Youth-safe names automatic!"

Processes are hard to sell. "Here's what to do when it goes wrong." That's not a selling point. That's a liability admission.

But every club needs it. Because it will go wrong. Not because volunteers are careless. Because the system doesn't exist to prevent it.

The Consent Checklist Every Club Needs

Before any post goes live, the volunteer checks:

1. Who is in the photo? List every child visible.
2. Do we have consent for each child? Check the consent register.
3. Are we using full names or initials? U12s and below: initials only.
4. Does the post include match data that could identify a child? Score, position, minutes played — all potentially identifying.
5. Has the parent been notified? Not just consented. Notified. They should know the post is going live.

Five questions. Thirty seconds. Prevents the 48-hour crisis.

The Privacy Wedge Nobody Is Building

Clubpost opened the children's privacy wedge. MatchDesk added youth-safe names. But nobody has built:

• The consent register template
• The pre-post checklist
• The incident playbook
• The parent notification workflow
• The committee reporting template
• The training module for volunteers

The privacy lane is open. The tools exist. The process doesn't. The club that builds the process owns the lane.