Add disclaimer

[buraizu]

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/bryce/add-disclaimer/bits_ai/mcp_server/setup/

[janine-c]

Suggested change

<li><i>Datadog collects certain information about your usage of the Remote Datadog MCP Server, including how you interact with it, whether errors occurred while using it, what caused those errors, and user identifiers in accordance with the <a href="https://www.datadoghq.com/legal/privacy/" target="_blank">Datadog Privacy Policy</a> and Datadog's <a href="https://www.datadoghq.com/legal/eula/" target="_blank">EULA</a>. This data is used to help improve the server's performance and features, including transitions to and from the server and the applicable Datadog login page for accessing the Services, and context (e.g., user prompts) leading to the use of MCP tools. The data is stored for 120 days.</i></li>

<li>Datadog collects certain information about your usage of the Remote Datadog MCP Server, including how you interact with it, whether errors occurred while using it, what caused those errors, and user identifiers in accordance with the <a href="https://www.datadoghq.com/legal/privacy/" target="_blank">Datadog Privacy Policy</a> and Datadog's <a href="https://www.datadoghq.com/legal/eula/" target="_blank">EULA</a>. This data is used to help improve the server's performance and features, including transitions to and from the server and the applicable Datadog login page for accessing the Services, and context (for example, user prompts) leading to the use of MCP tools. The data is stored for 120 days.</li>

[janine-c]

Please feel free to ignore any of these edits if legal requires us to put in an exact snippet.

I'm a little wary of putting the exact retention period into the docs, because those details are subject to changing over time. Everything else seems broad enough to include, but I'm wondering if we could maybe refer users to the included links and/or support if they're concerned about finding the specific time frame? Again, if we're required to post one, it's not a dealbreaker; I just want to make sure we're not introducing liabilities in case this changes but it never makes it to the docs team.

[buraizu]

Thanks @janine-c. I'll merge for now so that this information gets in front of users quickly, but I've followed up with the requestor to confirm if these edits are acceptable from a legal standpoint.

[janine-c]

Yes, totally agree that it's more important to get it merged now and to figure out the details later! Thank you 🙂

[ddtill]

Thanks, both. Tagging @noah-lerman-Datadog to clarify if the specific range is needed