> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/students/compliance.md).

# Compliance: NIL, Code of Conduct & Disclosure

This page explains how the student tools help you stay on the right side of your school's rules, and where your own responsibilities begin. It is guidance, not legal advice.

> The Student and NIL terms are currently a **draft, pending review by counsel**. Nothing here overrides them. The binding version is always the current [Terms of Service](/thecontentforge-docs/legal/terms-of-service.md) - read it before you rely on the tools, and check it again from time to time as it is finalised.

### You must be 18+ and a current student

Access is limited to people who are 18 or older and currently enrolled. You confirm this when you join the waitlist and again when you activate your account, and it is checked at every entry point. If either is not true, the student tools are not for you.

### What you are responsible for

The tools draft content and add safety guardrails, but they cannot know your specific school, team, conference, or club rules. These stay your responsibility at all times.

| You are responsible for          | What that means                                                                                                                                                                     |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Your school's NIL policy**     | Athletes: your university, athletic department, conference, and state may all have rules about name, image, and likeness deals. Check them before you announce or promote anything. |
| **Your code of conduct**         | Every draft must fit the standards your school, team, or organisation holds you to. When in doubt, ask your compliance office or advisor first.                                     |
| **Disclosing paid partnerships** | If a post is paid, gifted, or sponsored, you must disclose it - to your audience and, where required, to your school. The tool helps, but the obligation is yours.                  |
| **Reviewing every AI draft**     | Nothing posts automatically. Read every draft, edit it to match the facts, and only publish what is accurate and true to you.                                                       |

### Mandatory FTC disclosure on sponsored and NIL posts

When you use a sponsored or NIL mode - the athlete Sponsor-Safe Post and NIL Announcement modes - every post comes back with a clear, embedded disclosure (such as `#ad`) already in the copy, and a top-level disclosure note to guide you. This is a legal requirement in the US for any paid, gifted, or partnership content, and it is not optional. Keep the disclosure on every post, replace the placeholder brand name with the real sponsor, and disclose the deal to your school where your policy requires it. See [Athlete / NIL](/thecontentforge-docs/students/verticals/athlete.md) for how these modes work.

### The automatic safety backstop

Every student output passes through an automatic safety check before it reaches you. Where it finds risky content it either softens the wording, removes it, or blocks it outright, then shows you an honest notice explaining what it changed, so you can review it.

The check is tuned for student and campus life. Content that could put an athlete's NCAA eligibility at risk, such as sports-wagering promotion, is never shipped, and drafts steer clear of anything that would land badly with a school, a team, or a compliance office. Club recruitment copy stays welcoming and voluntary. Your copy speaks for you as an individual: it never claims that your university, college, team, or the NCAA endorses or sponsors you, and generated imagery stays generic rather than using real university, college, or team logos, crests, mascots, uniforms, jerseys, or helmets.

If a section can't be made safe, the tool holds it back and clearly flags that you need to edit it before posting.

### A backstop, not a certification

The guardrail is a safety net, not a stamp of approval. It cannot read your school's specific NIL policy or code of conduct, it does not certify that a post is compliant, and it will not catch everything. The tool helps you disclose properly and steers you away from obvious trouble - but the final call, and the responsibility, is always yours.

Read every draft, disclose your deals, follow your school's rules, and when something is unclear, ask your compliance office or advisor before you post. For plans and how credits work, see [Plans & Credits](/thecontentforge-docs/students/plans-and-credits.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/students/compliance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
