> For the complete documentation index, see [llms.txt](https://brd-digital.gitbook.io/brd-digital-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brd-digital.gitbook.io/brd-digital-docs/compliance.md). # Compliance Every BRD account is identity-verified, and screened continuously. BRD Digital operates under the Brazilian virtual-asset regulatory framework. Access is gated on the way in, monitored continuously, and restricted where regulatory clarity is pending. ## The framework * **KYC** — who is eligible, and how verification works. * **AML** — screening, monitoring, reporting. * **Data Security** — how accounts, sessions and data are protected. * **Risk Disclosures** — what holding and using BRD involves. ## The posture, plainly * Every participant is identity-verified before transacting — individuals through Sumsub, organizations through KYB — and screened continuously afterwards. * Transaction limits follow verification depth. * Service availability varies by jurisdiction, and BRD is restricted in sanctioned regions and where digital-asset services lack a clear legal footing. * Anonymous access does not exist on any tier. Questions about eligibility? Contact the compliance team. --- # 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://brd-digital.gitbook.io/brd-digital-docs/compliance.md?ask=&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.