---
title: Can I set data retention for a whole organization?
seoTitle: "Data Retention Is Configured per Project"
description: Data retention in Langfuse is configured per project, not per organization. Plans, minimum retention, and how deletion works.
tags: [administration, platform]
---

# Can I set data retention for a whole organization?

No. Data retention is configured **per project**. To apply the same policy across an organization, set it on each project.

Set it in **Project Settings → General → Data Retention**. The value is a number of days, with a minimum of 3. Set it to 0 to keep data indefinitely. You can also set it via the [Organization Management API](/docs/administration/scim-and-org-api). Changing it requires the `Owner` or `Admin` role on the project. Deletion happens asynchronously in the background.

Configurable data retention is available on Langfuse Cloud Pro, Teams add-on, and Enterprise plans, and on Enterprise self-hosted. On self-hosted Langfuse you can also set a retention for the initial project with `LANGFUSE_INIT_PROJECT_RETENTION`.

See [Data retention](/docs/administration/data-retention) for what retention deletes, and [Data access vs. data retention](/faq/all/data-access-vs-data-retention) for how retention relates to your plan's data access window.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/data-retention-per-organization.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.