> For the complete documentation index, see [llms.txt](https://onza.gitbook.io/onza/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onza.gitbook.io/onza/onza-app/eligibility-and-kyc-verification.md).

# Eligibility & KYC Verification

## Overview

To maintain platform security, compliance standards, and account integrity, all ONZA users are required to complete the verification process before accessing certain platform features and services.

The verification process helps protect the ecosystem and ensures that users meet the platform's eligibility requirements.

### Eligibility Requirements

To use **ONZA App**, users must:

* Be at least 18 years of age
* Have full legal capacity to enter into binding agreements
* Not be located in restricted or prohibited jurisdictions
* Ensure participation is lawful under the laws and regulations of their country of residence

Users are responsible for complying with all applicable local laws and regulatory requirements.

### KYC Verification

As part of ONZA's compliance framework, users must complete identity verification before accessing platform services.

Verification helps confirm user identity and supports the security of the ONZA ecosystem.

### Verification Process

* **1️⃣ Create Your Account**\
  Register your ONZA account and complete the initial onboarding process.
* **2️⃣ Submit Verification Information**\
  Provide the required documentation for identity verification.
* **3️⃣ Compliance Review**\
  Submitted information will be reviewed as part of the verification process.
* **4️⃣ Verification Approval**\
  Once approved, users can access available platform features and services.

### Required Documentation

Verification may include:

* Government-issued identification
* Proof of address (if required)
* Additional compliance documentation when necessary

Requirements may vary depending on jurisdiction and compliance obligations.

### Account Security

Users are responsible for maintaining the security of their accounts.

**To help protect your account:**

* &#x20;Use a strong password
* Enable available security features
* Never share login credentials
* Report suspicious activity immediately

### Verification Limitations

Failure to complete the verification process may result in:

* Restricted account access
* Limited platform functionality
* Inability to access certain services or features

Verification must remain accurate and up to date throughout the user's relationship with the platform.

### :pushpin: Important Notice

ONZA reserves the right to request additional information when necessary to satisfy compliance, security, or regulatory requirements.

Providing false, inaccurate, or misleading information may result in account restrictions or termination of access to platform services.


---

# 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://onza.gitbook.io/onza/onza-app/eligibility-and-kyc-verification.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.
