Acceptable use policy.

This policy governs what you may and may not do with TrackForge. It is part of the Terms of Service, and breaking it can cost you access.

TrackForge is used by minors in school and club settings. That shapes the rules below and how strictly they are enforced.

1. Your account

• Be accurate. Provide accurate information, including an accurate date of birth. The age gate exists to comply with children’s privacy law; defeating it puts a child outside the protections built for them.
• Keep your credentials secret. You are responsible for activity under your account.
• Do not share an account. Do not let someone else use yours. Coaches: this matters most for you. A shared staff login destroys the audit trail on everything from injury records to coach notes.
• Do not create accounts for others. Nobody can. Every TrackForge account is created by the person who owns it. A coach invites an athlete and the athlete accepts with their own sign-in; a guardian is linked to an athlete who already has an account. There is no flow that opens an account on someone else’s behalf, and that is deliberate.
• Tell us about compromises. Promptly, if you believe an account has been accessed by someone else.

2. Respecting other people's data

TrackForge holds training, health-adjacent, and minor-athlete data. Access is scoped by role for a reason. You may not:

• Reach past your scope. Access, or try to access, data belonging to an athlete, team, or organization you are not authorized to see.
• Use a role for something other than coaching. Do not use a coach or administrator role to look at athlete data for any purpose other than coaching that athlete.
• Keep data after you leave. Do not export, copy, or retain athlete data after your role in an organization ends.
• Share another athlete's data. Including screenshots of it, outside the people entitled to see it.
• Profile or recruit a minor. Do not use TrackForge to contact or build a profile of a minor for recruitment, marketing, or any purpose the athlete’s organization and guardian have not approved.

Coaches and organization administrators are custodians of other people’s data, some of it about children. Treat it that way.

3. Content

You are responsible for what you enter. Do not post content that is unlawful, defamatory, harassing, abusive, threatening, or hateful; sexually explicit, or sexualizing a minor in any way; an infringement of someone else’s copyright, trademark, or other rights; someone else’s personal information posted without their permission; or malware, or a link intended to compromise another user.

Coach notes, injury notes, and absence reasons are free-text fields about real people, often children. Write them as if the athlete and their guardian will read them, because they may be entitled to.

If you believe content on TrackForge infringes your copyright, the notice-and-takedown procedure is in the Copyright complaints section of the Terms.

4. The AI features

The AI coaching assistant and planning copilot may not be used to:

• Generate prohibited content. Anything that would violate section 3.
• Seek medical advice. Do not use it to seek medical diagnosis or treatment advice, or as a substitute for a physician. See the Disclaimer.
• Attack the model. Do not extract the underlying model’s instructions, or manipulate the assistant into ignoring its safety constraints.
• Burn a shared resource. Do not generate content unrelated to athletic training at volume, which is an abuse of a cost-bearing shared resource.
• Process outsiders' data. Do not use it to process data belonging to people who are not TrackForge users.

Usage limits apply and are enforced per organization.

5. Technical conduct

You may not:

• Probe or circumvent. Probe, scan, or test the vulnerability of TrackForge, or breach or circumvent authentication, authorization, or rate limiting.
• Automate access. Access the service by any automated means (scraping, crawlers, bots) except through an interface we provide for that purpose.
• Degrade the service. Interfere with service to other users, including by generating unreasonable load.
• Reverse engineer. Decompile or attempt to derive source code, except to the extent the law expressly permits despite this restriction.
• Resell. Resell, sublicense, or provide TrackForge as a service to third parties without a written agreement with us.
• Strip notices. Remove or obscure proprietary notices.

Security researchers: we would rather hear from you than not. Report suspected vulnerabilities to security@trackforge.fit. Good-faith testing that avoids other users’ data, avoids service degradation, and gives us reasonable time to fix will not be met with a complaint from us. Do not access another user’s data to prove a bug exists; a description is sufficient.

6. Enforcement

Depending on severity we may warn, restrict features, suspend, or terminate an account or an entire organization, and where the law requires it, report to authorities. Anything involving the safety of a minor is handled at the top of that range immediately.

Where an organization administers accounts, we will generally work through that organization, except where doing so would put an athlete at risk.

We are not obligated to monitor content, and we do not pre-screen it. Choosing not to act in one case does not waive the right to act in another.

7. Reporting a problem

To report a violation or a safety concern, email hello@trackforge.fit, or write to TrackForge LLC, 550 Congressional Blvd, Suite 390 #1059, Carmel, IN 46032, United States. Suspected vulnerabilities go to security@trackforge.fit.

Concerns about the immediate safety of a child should go to local authorities first and to us second.