Skip to content

Add disclaimer #32033

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 7, 2025
Merged

Add disclaimer #32033

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d63295c
Add disclaimer
buraizu Oct 7, 2025
a108f28
Fix smart quote
buraizu Oct 7, 2025
ff31bc8
Fix smart quote
buraizu Oct 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions content/en/bits_ai/mcp_server/setup/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@
<li>The Datadog MCP Server is not supported for production use during the Preview.</li>
<li>Only Datadog organizations that have been specifically allowlisted can use the Datadog MCP Server. It is not available to the general public.</li>
<li>The Datadog MCP Server is not available for organizations that require HIPAA compliance.</li>
<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>

Check warning on line 33 in content/en/bits_ai/mcp_server/setup/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.abbreviations_latin 

Use 'for example' instead of abbreviations like 'e.g.,'.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

</ul>
</div>

Expand Down
Loading