> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/for-apps/partners-and-compliance.md). # Partners and compliance Money is regulated differently in every country. The modules are designed to respect that, not to work around it. ## Licensed local partners In each country, activities that need a license, such as holding money for others, lending, issuing cards, exchanging currency or offering investment products, run through partners licensed for them. Zirodelta does not take on regulated roles it does not hold. ## Client money stays where the rules allow * Money your users pay in advance stays in the place your country's rules require. * It is put to work only through products that are allowed for it, through licensed partners, and with the owner's consent where required. * Zirodelta never invests money that is not the investor's to put at risk. ## Risk sits with Zirodelta first Riskier roles, such as the first-loss buffer in the Yield Engine and the capital behind advances, are filled with Zirodelta's own capital. ## Identity and sanctions Identity checks and sanctions screening are done where the rules require them, by the licensed partner responsible or by Zirodelta. ## Your responsibilities Your app remains responsible for its own licenses, what it tells its users, and the rules in the countries where it operates. --- # 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.zirodelta.com/for-apps/partners-and-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.