> ## Documentation Index
> Fetch the complete documentation index at: https://docs.particle.pro/llms.txt
> Use this file to discover all available pages before exploring further.
# Zero data retention
> What Particle keeps from your organization's API and MCP requests, what zero data retention removes, what it does not cover, and how to request it.
export const SupportLink = ({children}) => {
return {children};
};
export const EmailSupportLink = () => {
return api@particle.pro;
};
export const DashboardLink = ({children}) => {
return {children};
};
By default, Particle keeps the contents of your organization's API and MCP requests for 90 days, so you can inspect them in **Request Logs** and Particle can investigate support and security issues. Zero data retention (ZDR) is a per-organization setting: with it on, Particle keeps that each request happened, but not what it contained.
## What is kept
| | Retention on (default) | Zero data retention |
| - | - | - |
| Time, endpoint, HTTP method, and status code | Kept | Kept |
| Duration and request and response sizes | Kept | Kept |
| Organization, project, and the API key or user that made the request | Kept | Kept |
| MCP tool name | Kept | Kept |
| Client IP address and user agent | Kept | Kept |
| Query parameter names | Kept | Kept |
| Query parameter values | Kept for 90 days | Not kept |
| Identifiers in the path, such as a podcast or episode ID | Kept for 90 days | Not kept: the endpoint is recorded as its template, such as `/v1/podcasts/{id}` |
| Request bodies and response bodies | Kept for 90 days | Not kept |
Under zero data retention, Request Logs still lists every request, marked **Omitted under zero data retention** in place of its contents. Particle's operational logs and traces for your requests keep the same metadata and drop the same contents.
## What is covered
Zero data retention covers every request your organization makes to the [REST API](https://api.particle.pro) and the [MCP server](/mcp/overview), whichever credential it uses.
These are not covered:
* **Alerts.** An alert's definition (title, description, keyword, watched entity, filters, and notification addresses) and its results (matches and deliveries) are stored as part of the alerts feature. See [Alerts โ Data retention](/alerts/overview#data-retention).
* **Radar.** Searches and questions in Particle Radar are not covered.
* **Account and billing data.** Your organization's name, members, projects, plan, invoices, and billing emails are kept to run your account.
* **Requests made before zero data retention was turned on.** The setting applies to requests from the moment it takes effect. Contents already in Request Logs expire on the normal 90-day schedule.
## Check your organization's setting
Open **Organization settings** in the platform dashboard. The **Data retention** section shows **On ยท 90 days** when Particle keeps request contents, or **Zero data retention** and the date it was turned on.
## Request zero data retention
Zero data retention is turned on by Particle staff; there is no self-serve switch.
1. In **Organization settings โ Data retention**, click **Contact support**. The email is addressed to and names your organization.
2. Particle staff turn the setting on for your organization. It takes effect on every request within about 30 seconds.
3. The **Data retention** section then shows **Zero data retention** and the date it was turned on.
To turn zero data retention off, contact support the same way. You can also reach the team from the support page.
## Subprocessors and commitments
The subprocessors that handle customer data, and Particle's contractual commitments, are listed in the [Particle Trust Center](https://trust.particle.pro).
## Related
* [Alerts โ Data retention](/alerts/overview#data-retention): what alerts store for an organization with zero data retention.
* [Authentication](/auth): the credentials a request can use.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.