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

# Deprecation Policy for Resources

**Deprecation Policy for Resources**

1. Purpose

This policy aims to establish clear guidelines for the deprecation and discontinuation of resources provided by Combateafraude Tecnologia da Informação S.A. (hereinafter referred to as "CAF"), ensuring transparency, predictability, and appropriate support for clients, partners, and developers using CAF’s services.

1. Scope and Assumptions

This policy applies to all resources developed, maintained, and made available by CAF, including APIs, SDKs, libraries, features, and associated services.

The assumptions include a commitment to clear and timely communication regarding any changes in the resource lifecycle, support during the transition period, and minimizing operational impacts for clients.

1. Coverage and Applicability

This policy is applicable to all clients, partners, and integrators who use CAF’s resources.

1. Definitions

| **Resource Category** | **Description**                                                                                                                                                                                     |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Active                | Available, maintained, and fully supported. Receives continuous improvements, updates, and full technical support.                                                                                  |
| Deprecated            | Still functional, but in the process of being discontinued. Does not receive new features, only critical fixes. Technical support is limited. Migration to updated resources is highly recommended. |
| Obsolete              | Still functional, but officially discontinued. No longer receives updates, fixes, or support. Its use is strongly discouraged.                                                                      |

Other definitions, when applicable, will be available in our official documentation:

[https://docs.caf.io](http://docs.caf.io/).

1. Deprecation Guidelines

\
CAF will follow a structured process for the deprecation and discontinuation of resources, ensuring clients have sufficient time to adapt.

* 1. Communication and Notices

**Advance notice:** CAF commits to informing about the discontinuation of any resource **at least 60 days in advance** of the date when the resource will be officially discontinued and considered obsolete. From the time the notice is issued, the resource will be classified as **deprecated**, and its transition period will begin.

**Communication channels:**

* Official documentation
* Release notes
* Emails to registered contacts (when applicable)
* Service status page (<https://status.caf.io/>)
* Customer Success team support (when applicable)

**Contents of the communication:**

* Resource status marked as “deprecated”
* Reasons for deprecation (e.g., outdated architecture, insecure dependencies, replacement by superior technology)
* Benefits and guidance for migration
* Recommended replacement resource (if applicable)
* Useful links such as documentation, migration guides, and code examples
  1. Transition Period

Deprecated resources will remain functional during the transition period; however:

* They will **not receive new features or improvements**
* **Only critical fixes may be applied**, evaluated on a case-by-case basis depending on the impact and complexity of the fix versus the benefit of migrating to active resources
* Immediate migration to updated and actively maintained versions is **strongly recommended**
  1. Exceptions

CAF reserves the right to discontinue any resource **immediately and without prior notice** under the following circumstances:

* Identification of **critical security risks**
* **Legal or regulatory obligations**
* **Misuse, abuse, or fraudulent use** of the resource

1. Final Provisions

This policy ensures that users operate with the most secure, efficient, and up-to-date versions of CAF resources. We **strongly encourage proactive migration** to newer versions to maximize benefits and ensure future compatibility. We are committed to maintaining clear and informative communication throughout the deprecation process to support all stakeholders.

We also emphasize that **the fraud prevention process is not guaranteed to function properly in deprecated or obsolete resources**.

1. Version History

| **Version** | **Date** | **Change Description** | **Made by**                                                         |
| ----------- | -------- | ---------------------- | ------------------------------------------------------------------- |
| 1.0         |          | Document Conception    | Platform, Identity Intelligence, Smart Onboarding and Data & IA Hub |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.caf.io/caf-api/deprecation-policy-for-resources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.