Privacy Policy

The short version

• No advertising, ever. No third-party tracking, at any tier.
• Sharing is off until a parent turns it on, and it is the parent's switch.
• Raw practice video is deleted within about six months. The measurements taken from it stay.
• A parent can delete the account and every child's data on it, at any time, from inside the app.
• We do not sell personal information, and we never have.

Who we are, and who holds the account

Homefield is operated by the Homefield team. A parent or legal guardian holds the account. Children do not sign up, do not sign in, and do not have their own login — they use the app under an account an adult created and controls.

We treat everyone under 18 as a child. COPPA sets its threshold at 13; we apply one stricter rule to everybody, because one rule is simpler and safer than two, and it stays at 18 until our counsel says otherwise.

What we collect about a child

• First name and age. Not a surname, and not a date of birth — the coaching rubrics only use an age band, so a birth date is never collected and therefore never has to be protected.
• Handedness, because the same movement is scored differently for a left- and a right-handed player.
• Video of practice, recorded by the parent on their own device and sent to us to be measured.
• Body position measured from that video — joint positions, angles, timing, balance — and the scores calculated from it.
• Which drills were completed, and when.
• Game days a parent chooses to log — the opponent, the result and the score.
• A note the parent may add to a session — a few tapped labels, optionally how the child said the session felt, and up to 280 characters the parent may type. All three are optional, most sessions have none, and nothing counts how often they are used. Typing is available only after the app has checked that an adult is holding the phone.

We do not collect a child's email address, phone number, precise location, contacts, or any advertising identifier. We do not ask a child to enter free text that we store — the note above is the parent's, and the app asks who is holding the phone before it opens that field.

What we collect about the parent

• The email address or phone number used to sign in, through Apple, Google or a phone number.
• A record that consent was given: when, by which method, and which version of the notice was shown.
• Subscription status, if there is one. Payment card details are handled by the app store or the payment provider and never reach us.

What we never do

• No advertising. There are no ad SDKs in the app, and there is no paid tier that turns ads on.
• No third-party analytics. Nothing about a child is sent to an analytics vendor.
• No behavioural profiling of children, and nothing about a child is used to target anything at them.
• No public profiles, no leaderboards visible outside a family, and no comparison between siblings anywhere in the product.
• No selling of personal information, and no disclosure of it to third parties for their own purposes.

What we do with it

• Measure how a child moves, and turn that into their Player Card and their practice plan.
• Show the parent what their child did — sessions, repetitions, and what to work on next.
• Improve the coaching rubrics. Practice video is used for this only where a parent has separately agreed to it; it is not part of ordinary use.

Where a score has not been produced by a calibrated coaching engine, the app says so on the screen showing it. We would rather show a caveat than a number a parent would misread.

Who else sees it

Nobody, unless a parent turns sharing on. Sharing is off by default.

With sharing on, a parent can send a Player Card out of the app. That card carries the child's badge and first name, the sports they practise, when their last check was, and how many games they have logged. It carries no age, no photo, no surname and no score. Nothing is ever sent automatically, and the parent is always the sender.

We use cloud infrastructure providers to store and process data on our instructions. They may not use it for their own purposes. Data is stored in the United States (Google Cloud, us-central1).

On-device pose detection (Google ML Kit) reports anonymous app diagnostics — API usage metrics — to Google as part of running on the phone. No video, no name and no other child data leaves the phone through that channel.

How long we keep it

• Raw practice video: deleted within about six months. This is enforced by a storage lifecycle rule on the bucket itself, not by application code, so it happens whether or not anyone remembers to ask.
• The still picture and short preview made from each clip, and the notes a parent adds to a session: kept while the child is enrolled.
• Measurements, session logs, game-day results and Player Cards: kept until a parent deletes them, because they are the child's history and the product is about showing progress over time.
• Consent records: kept after deletion, because the record that consent was given and withdrawn is itself the evidence a regulator may ask us for.

"Within about six months" rather than "exactly 180 days": the deletion is scheduled by the storage provider and may run up to a day after an object becomes eligible. We would rather state that than a number we cannot guarantee to the hour.

What a parent can do, at any time

• Refuse. Decline consent and no child profile is created and nothing about a child is collected.
• See what we hold about their child.
• Correct it.
• Delete the account and every child's data on it, from Parent settings inside the app. No email required, no support ticket, no waiting. If a parent cannot sign in — uninstalled, changed phone — a web form starts the same deletion; a person reads it within three days and completes the deletion within thirty.
• Withdraw consent. We stop collecting anything new about the child immediately, and the parent can then delete what already exists.
• Turn sharing off again, at any point.

How we verify that a parent is a parent

Before any child data is captured, we ask for consent from a verified parent. Signing in is not consent — it is a separate, explicit act.

The in-app check that keeps a child from tapping through by accident is a gate, not verification. Verifiable parental consent uses a separate mechanism, and the app records which one was used and when.

If we make a significant change to what we collect or how we use it, we ask for consent again rather than relying on an earlier agreement.

Getting in touch

Questions about a child's data, or a request to see, correct or delete it, go to privacy@homefieldcoach.com. We answer within the period the applicable law requires, and sooner where we can.

Changes to this policy

When this policy changes, the version and date at the top change with it. Where a change is significant, we ask consenting parents to review and agree again rather than treating silence as agreement.