> 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/2025/15-september-access-controls-device-intelligence-and-session-tracking.md).

# 15 Sep: Access Control & Device Fraud

Access Controls, Device Intelligence and Session Tracking. Product updates for access restriction lists, device fraud signals, session tracking, banned face accuracy, and portal analytics.

This release added powerful new fraud prevention tools, deeper workflow visibility, and enhanced intelligence features to help compliance teams stay ahead of emerging risks.

### **New features**

* [Access Restriction Lists](https://portal.complycube.com/accessRestrictionLists) were introduced, allowing businesses to maintain and enforce rules that prevent high-risk customers from accessing verification services.
* [Device Intelligence](/documentation/product-guides/digital-fraud-intelligence/device-intelligence-check.md) was launched (beta), analyzing a customer’s device for signs of tampering or suspicious activity to assess fraud risk.
* Detailed **activity** and **event tracking** was added for customers navigating a workflow session, providing greater transparency into user behavior and session progression.

### **Improvements**

* The [Banned Faces](https://portal.complycube.com/bannedFaces) engine was improved, with upgraded algorithms that greatly reduce false positives while continuing to automatically flag customers whose facial biometrics match entries on a banned list.
* [Analytics and Insights](https://portal.complycube.com/analytics) in the Portal were upgraded with richer metrics and activity trends, from customer usage and verification outcomes to workflow performance, giving compliance teams the insights they need to drive smarter decisions


---

# 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/2025/15-september-access-controls-device-intelligence-and-session-tracking.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.