> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-fairbid/privacy/coppa.md).
# COPPA
The Children's Online Privacy Protection Act ([COPPA](https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa)) sets guidelines for collecting and processing personal information from children under the age of 13. It applies to apps and digital services, either directed at children or serving a general audience, where children may be present. You must assess both the nature of the content and the intended audience when configuring COPPA-related settings.
DT FairBid allows you to configure COPPA compliance at the app or placement level. The app level includes placements and users to inherit the same settings. Placement-level configurations allow you to apply different COPPA settings to specific placements. COPPA compliance at any level confirms that the app, or placement context, is not directed at children under the age of 13 or to a general audience that may include them.
To configure COPPA at the app level, select the checkbox when you add an app. This confirms that your app is COPPA-compliant.
{% hint style="info" %}
Your monetization might be negatively impacted if the COPPA Compliance box remains unchecked.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digitalturbine.com/dt-fairbid/privacy/coppa.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
