> For the complete documentation index, see [llms.txt](https://docs.warpstream.com/warpstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warpstream.com/warpstream/reference/deprecation-policy.md).

# Deprecation Policy

This page describes our policy in the event of removal of customer-usable functionality from WarpStream services.

## Potential customer impact

* Large: could prevent use of service if the customer relies on the feature.
* None: totally transparent, depending on customer usage of the service.

## Examples

* Complete removal of a feature from the UI.
* Shutting down `api/v1/foo`.

## Frequency

Rare (\~1 or fewer per year)

## Communication before the change

* Guaranteed: multiple email notifications to all registered WarpStream users, starting at least 180 days before the deprecation date, with details about the change and available alternatives.
* May also include: in-app messaging; updated documentation and release notes; communication from Sales and customer support.

## Timing of the change for each customer

100% at Confluent’s discretion.\\


---

# 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.warpstream.com/warpstream/reference/deprecation-policy.md?ask=<question>&goal=<user_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.