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

# 2025

- [3 de diciembre: Políticas y Aadhaar](https://docs.complycube.com/documentation/changelog/changelog-es/2025/1-december-compliance-policies-and-aadhaar-plus-multi-bureau-updates.md): Políticas de cumplimiento y Aadhaar, además de actualizaciones de Multi-Bureau. Actualizaciones de producto para la aplicación de políticas de flujo de trabajo, verificación de Aadhaar, evaluación de políticas y una cobertura ampliada de Multi-Bureau.
- [15 de septiembre: Control de acceso y fraude de dispositivos](https://docs.complycube.com/documentation/changelog/changelog-es/2025/15-september-access-controls-device-intelligence-and-session-tracking.md): Controles de acceso, inteligencia de dispositivos y seguimiento de sesiones. Actualizaciones de producto para listas de restricción de acceso, señales de fraude de dispositivos, seguimiento de sesiones, precisión en rostros vetados y analíticas del portal.
- [6 de febrero: Orquestación y fraude móvil](https://docs.complycube.com/documentation/changelog/changelog-es/2025/6-february-orchestration-mobile-intelligence-and-white-labeling.md): Orquestación, inteligencia móvil y marca blanca. Actualizaciones de producto para orquestación de flujos de trabajo, inteligencia móvil, marca blanca, gestión de casos AML y herramientas para desarrolladores.


---

# 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.complycube.com/documentation/changelog/changelog-es/2025.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.