> For the complete documentation index, see [llms.txt](https://docs.goevolve.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goevolve.xyz/legal-documents/verifications-and-screenings.md).

# Verifications and Screenings

Evolve implements a layered set of technical, compliance, and operational controls to help enforce eligibility restrictions and mitigate misuse. These controls support compliance and risk management, but they do not guarantee prohibited users will never attempt access and they do not eliminate all risks.

### 1) In-app screening processes

#### A) IP and geolocation screening

When you visit the Evolve website or application, your IP address may be analysed to estimate geographic location. If an IP is identified as originating from a restricted jurisdiction, access to the website or certain functionality may be blocked. This may include measures designed to detect or restrict access via VPNs, proxy services, or anonymisation tools where inconsistent with compliance requirements.

#### B) Wallet screening

When you connect a wallet, Evolve may screen the wallet using third-party tools to identify wallets associated with:

* sanctioned entities
* known illicit activity
* high-risk blockchain exposure
* other compliance red flags

If a connected wallet is flagged, Evolve may disconnect the wallet, block access, restrict mint/redeem, or require enhanced verification.

### 2) KYC/KYB and AML checks (where applicable)

Certain features (especially mint/redeem) may require identity verification or business verification (KYC/KYB), including AML screening, to satisfy compliance requirements. If required, you must complete verification before accessing restricted flows.

### 3) Ongoing monitoring and rescreening

Evolve may:

* rescreen wallets or users periodically
* request updated information
* apply enhanced due diligence for elevated risk signals
* restrict or suspend access based on compliance outcomes

### 4) Limitations

Screening tools and data sources can be incomplete, delayed, or inaccurate. A “pass” result is not a guarantee that a user is low-risk or compliant, and a “flag” may require manual review. These controls reduce risk but do not eliminate it.

### 5) Actions we may take

Based on screening/verification outcomes, Evolve may:

* block access from restricted jurisdictions
* restrict mint/redeem functionality
* place accounts/wallets into a review state
* request additional information
* report activity where required by law
* terminate access consistent with the Terms & Conditions


---

# 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:

```
GET https://docs.goevolve.xyz/legal-documents/verifications-and-screenings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.