> For the complete documentation index, see [llms.txt](https://docs.stobox.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stobox.io/about/regulatory-and-compliance-foundations.md). # Regulatory and Compliance Foundations Stobox operates in regulated environments that require strict adherence to financial, operational, and identity standards. Our infrastructure is designed to meet the expectations of regulators, institutions, and market participants while supporting cross-border tokenization. *** ### **Stobox Regulatory Presence** **United States**\ Stobox is represented in the US through **Stobox Technologies**, supporting enterprise development, partnerships, and integration with US regulatory expectations for tokenized securities. **Poland**\ Stobox operates as a **registered Virtual Asset Service Provider (VASP)** in Poland.\ This registration covers activities related to digital asset transactions, identity verification, and compliance obligations under EU-aligned AML and CTF rules. **Qatar**\ Stobox holds a **QFC (Qatar Financial Centre) license**, enabling compliant operations and business activities within a recognized financial jurisdiction in the Middle East. These regulatory footholds allow Stobox to operate globally while respecting local frameworks. *** ### **Core Compliance Principles** Stobox technology is designed to ensure that tokenized assets remain compliant throughout their lifecycle. Compliance is embedded in the platform, protocol, and identity layers. #### **Key compliance standards include** * **KYC** for individuals * **KYB** for corporate clients * **AML and CTF screening**, including sanctions lists * **ongoing risk monitoring** * **transaction validation** based on identity and eligibility * **recordkeeping and audit logs** for regulators * **asset ownership transparency** within privacy boundaries These requirements apply across onboarding, issuance, transfers, and redemption events. *** ### **European Regulatory Alignment: MiCA and DORA Readiness** Although regulatory requirements continue to evolve, Stobox follows principles aligned with the European Union’s frameworks: **MiCA**\ Clear asset categorization, issuer responsibilities, consumer protection, transparency, and reporting. **DORA**\ Operational resilience, cybersecurity, incident management, third-party oversight, and continuity planning. Stobox systems and processes follow the structure and intent of these regulations to ensure long-term operational safety. *** ### **Identity Anchored Compliance** Verified identity is at the core of the Stobox ecosystem. Stobox DID ensures that all participants in tokenized markets are validated before they receive, hold, or transfer assets. Identity-driven compliance allows: * enforcement of jurisdiction rules * prevention of unauthorized transfers * support for public and private offerings * auditability for regulators and service providers By tying every wallet to a verified identity, Stobox ensures that tokenized assets behave according to real regulatory rules. *** --- # 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, and the optional `goal` query parameter: ``` GET https://docs.stobox.io/about/regulatory-and-compliance-foundations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.