> 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/2023/16-august.md).

# 16 Aug: Compliance Controls

Compliance Controls and Platform Enhancements. Product updates for archival policies, image redaction, portal performance, audit logging, and mobile SDK reliability.

This release focused on strengthening compliance management and giving organizations greater flexibility in how customer data is handled, alongside several platform-wide improvements.

### **New features**

* Added customizable [archival policies](https://portal.complycube.com/policies), allowing teams to define how long customer data and verifications are retained before secure deletion.
* Introduced enhanced [image redaction](/documentation/product-guides/identity-verification/document-check/redaction.md) policies to align with global compliance requirements, helping businesses control the visibility of sensitive PII across reports.

### **Improvements**

* Improved Portal performance for organizations with large client volumes, including faster search and filtering.
* Enhanced audit logging with more granular event tracking for administrative actions.
* Upgraded mobile SDK error handling for network interruptions and device-level permission issues.

### **Documentation**

* Added new compliance guidance for archival and redaction policies.
* Updated best practices for secure API key management and audit trail usage.


---

# 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/2023/16-august.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.