Privacy at IDP Engine

IDP Engine collects the information needed to create a youth soccer Individual Development Plan: player name, age group, position, coach-provided context, player interview answers, coach review notes, and the generated IDP document.

If a coach sends an interview link by email, IDP Engine also stores the email destination needed to deliver that invitation.

The information is used to support a coach-reviewed development plan: setting up the player context, running the player reflection, helping the coach review the evidence, drafting the IDP, sending invite emails, supporting approved family-facing sharing, maintaining account security, handling support, and improving the workflow.

IDP Engine is not a medical, psychological, disciplinary, scouting, tryout, or selection system. It should not be used for injury guidance, diagnosis, discipline, roster decisions, talent prediction, or other high-stakes decisions outside normal player-development planning.

Generated IDPs are drafts until a coach reviews and approves them. Coaches and clubs are responsible for the final plan they choose to share with a player or family.

IDP Engine is built for youth soccer contexts, but it is not a child-self-serve app. Use is led by a coach or club, with parent or guardian involvement where required.

The player-facing screen is written as player assent: it helps the player understand what they are about to answer. It should not be treated as a complete parent or guardian consent workflow by itself.

For U13-and-under players, IDP Engine requires an explicit parent/guardian action path before the player interview starts, because U13 teams can include 12-year-old players. Coaches and clubs should not send a player interview link until that parent/guardian path has been handled.

IDP Engine uses service providers and subprocessors to operate the product. These can include hosting and database providers, authentication providers, email delivery providers, billing providers, analytics or logging tools, and approved AI model providers.

Approved AI model providers may process submitted coach and player information to help draft an IDP. New or experimental model-provider tests should use redacted fixtures unless Kyle explicitly approves a real-data path.

IDP Engine keeps information only as long as it is reasonably needed to provide the service, support coaches and clubs, protect the product, meet legal or billing obligations, and handle access, correction, or deletion requests.

Parents, guardians, coaches, clubs, and players can ask IDP Engine to access, correct, or delete information by emailing hello@idpengine.com. For youth-player requests, IDP Engine may route the request through a parent, guardian, coach, or club contact before disclosing or deleting player data.

IDP Engine may ask for enough context to confirm the player, coach, club, requester identity, and requester relationship before taking action. Deletion may not remove minimal request records, billing records, security logs, backups, or information IDP Engine is required to keep.