Is Your Child's AI Coaching Actually Safe? A Parent's Privacy Guide

Your child's coach says their first touch needs work. You've found an AI tool that analyses a video clip and gives you feedback - sounds useful. But then you get to the upload screen, and you stop. That's your kid. On video. Going to... somewhere. Some server, some AI, some company you've never heard of.

If you're hesitating, you're exactly the parent this article is for. Privacy is the number one concern parents have about AI sports tools - not the quality of the feedback, not the price, but whether it's safe to upload a video of their child. I understand that hesitation completely, because I had it too. The whole reason this tool exists is that I wanted coaching feedback for my own kids and couldn't find anything I trusted enough to upload their video to.

So here's what actually happens to your child's video, what questions you should ask before uploading to any AI sports tool (not just ours), and what the safeguards look like when they're done properly.

What actually happens when you upload a video

Let's walk through it plainly. When you upload a video clip to an AI football analysis tool, three things happen:

1. The video is stored on a secure server. In our case, that's Google Cloud infrastructure - the same infrastructure that banks and hospitals use. The video sits in an encrypted storage bucket. It's not public. Nobody can search for it. It's accessible only through your authenticated account.

2. The video is sent to an AI model for analysis. The AI processes the video, identifies technique patterns (plant foot position, body shape, strike point), and generates structured feedback. For our tool, that model is Google Gemini, accessed via Google's Enterprise API.

3. The video is retained or deleted based on your choice. You control this. If you want to keep the video so you can compare future clips, you can. If you want it gone immediately after the analysis, you delete it with one click. No email to support, no 30-day waiting period. One button.

Here's the critical part that most parents don't know to ask about: not all AI APIs handle your data the same way.

The question that matters: does the AI train on your child's video?

This is the question nobody tells you to ask, and it's the most important one. When you upload a video to an AI tool, the AI model processes it - but what happens to the video after that processing?

There are two models, and they're very different:

Consumer AI APIs (the risky one): On consumer-tier AI APIs, your data may be retained and used to improve the model. That means your child's video could theoretically be used as training data - fed back into the AI to help it learn. You might not know this is happening. The consent might be buried in a terms-of-service document nobody reads. Once the video is in the training set, removing it is effectively impossible - it's baked into the model's parameters.

Enterprise AI APIs (the safe one): Enterprise-tier APIs - the tier that businesses pay for - operate under strict Service Level Agreements that explicitly prohibit using your data for model training. The video is processed, the analysis is generated, and the video is not retained by the AI provider for training purposes. It comes in, the model does its job, and the video goes back to your account's storage. The AI doesn't learn from it. It can't.

Our tool uses Google Gemini via the Enterprise API. The SLA with Google is clear: videos processed through the enterprise tier are not retained by Google and are not used to train their models. This was a non-negotiable decision from the start, because the founder is a parent first and a builder second. No child's video should end up in an AI training set.

If you're evaluating any AI sports tool, ask this question directly: "Is the AI processing done via a consumer API or an enterprise API?" If they can't answer, or if the answer is "consumer," that's a red flag.

"Anyone" vs. your child: what data is actually collected

A common concern: "Does the AI need my child's name, age, and face to work?" The answer should be no. Here's what actually matters for football technique analysis:

• The video of the body movement. The AI analyses how your child moves - foot placement, body angle, balance, timing. That's the whole point. The video needs to show the relevant body parts in motion.
• That's it.

The tool should not require your child's full name. It should not require their date of birth. It should not require a profile photo that links a face to an identity. Our tool lets you create a "player profile" with just a first name or nickname - enough for you to keep track of whose clip is whose. That's all that's needed.

When you film a clip for analysis, the ideal footage shows your child from behind or from the side - not a face-on close-up. This isn't just a privacy measure; it's actually better for technique analysis, because the AI can see foot position and body shape more clearly from behind. (I wrote about this in how to film your child's football technique - the filming angle matters for both privacy and analysis quality.)

What to ask before uploading to any AI sports tool

If you're evaluating any AI coaching or analysis tool for your child, here are the questions to ask, in order of importance:

1. Is the AI processing done via an enterprise API? This is the question that separates tools that take child privacy seriously from those that don't. Enterprise API means the AI provider has a contractual obligation not to retain or train on your data. Consumer API means your child's video might be training data.

2. Can I delete the video immediately? Look for a one-click delete. Not "email us within 30 days." Not "we'll process your deletion request." A button, on your dashboard, that removes the video now. If the tool makes deletion hard, they're retaining the video for their purposes, not yours.

3. What data is collected beyond the video? The tool should need the video and a nickname. If it's asking for a date of birth, a home address, a school name - ask why. Football technique analysis doesn't need any of that.

4. Is the video accessible to anyone other than me? The answer should be: no. Not the company's staff. Not other users. Not third parties. The video is yours, stored securely, accessible only through your authenticated login. (Note: this is different from the AI processing the video - the AI provider processes it under enterprise SLA, but the AI provider's human staff do not watch your kid's video. The model does the analysis automatically.)

5. Is the data sold or shared? The answer should be a clear no. No selling video data to third parties. No sharing with advertisers. No "anonymised" datasets that could realistically be de-anonymised.

The one-click delete: why it matters

A lot of companies talk about privacy in their terms of service. Very few make it easy to actually exercise your privacy rights. The gap between "we respect your privacy" and "you can delete your data right now, yourself, with one button" is where most tools fail.

Our tool was built with deletion as a first-class feature, not an afterthought. From your dashboard, you can delete any video clip with a single click. The clip is removed from storage immediately. It's not archived, it's not soft-deleted for 30 days, it's not held in a backup that might be restored. Deleted means deleted.

This matters because privacy isn't a promise - it's a capability. A privacy policy is a document. A one-click delete button is a feature. The document says "we respect your data." The button proves it.

Why we built it this way: the parent-first decision

Here's the honest context. The founder (that's me writing this, or rather, the person whose voice this is) built this tool because he wanted coaching feedback for his own kids. He's a dad at a community football club in Brisbane. His kids play. He wanted to help them improve. He couldn't find a tool he trusted enough to upload his own children's video to.

So when the architecture decisions were being made, they were made through the lens of "would I upload my own kid's video to this?" The answer needed to be yes on every count: enterprise API (no training on the video), minimal data collection (nickname only), one-click delete (no friction, no waiting), encrypted storage (Google Cloud), and no sharing or selling of data.

Every one of those decisions costs something - enterprise API access is more expensive than consumer, the deletion infrastructure is engineering work, and the minimal-data approach limits future marketing options. They're worth it. The trust barrier is the thing that stops parents using AI coaching tools at all. Solving it properly isn't just the right thing to do; it's the only way the product works.

If privacy is your concern, here's how to start

If the privacy question has been the thing stopping you from trying AI coaching feedback, here's what I'd suggest: try a free analysis first. Upload one clip. See the feedback. If it's not useful, delete the clip with one click and you're done - no commitment, no data left behind.

The analysis takes a couple of minutes. It breaks down what's happening across your child's technique - plant foot, body shape, ankle lock, strike point - with plain-English explanations and a drill to run together. You keep the clip and the feedback, or you delete the clip. Either way, you're in control.

For more on how the filming works (and why the filming angle itself is a privacy choice), how to film your child's football technique walks through exactly what to shoot and how. And if you want to see what the feedback actually looks like before uploading, inside the AI analysis dashboard shows you the whole thing - the strengths, the improvements, the drills, and the metrics.

Privacy isn't a feature you bolt on after the product works. It's the foundation that makes the product work at all - because the parent who won't upload the video gets no feedback, and the child gets no help. Get the privacy right, and the rest follows.