> For the complete documentation index, see [llms.txt](https://docs.fractit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fractit.com/compliance/jurisdiction-controls.md).

# Jurisdiction Controls

***

### Restricted jurisdictions

**US persons and entities are not permitted to access this product.**

Additional restricted jurisdictions may be added in accordance with applicable regulatory requirements and sanctions regimes. The current list of restricted jurisdictions is enforced at:

1. **Onboarding** — jurisdiction is checked during KYC. Users in restricted jurisdictions cannot complete onboarding and will not be whitelisted.
2. **Contract layer** — Canton's compliance module checks jurisdiction status on every transfer. A wallet associated with a restricted jurisdiction cannot receive tokens even if it was previously whitelisted.

***

### How restrictions are enforced

Jurisdiction restrictions are not UI-level controls. They are encoded in the DAML compliance module on Canton Network. This means:

* Restrictions cannot be bypassed by interacting with contracts directly
* A change in a user's jurisdiction status (e.g. sanctions designation) can trigger automatic transfer restriction at the contract level
* New jurisdictions can be added to the restricted list and enforced immediately on-chain

***

### Future markets

As Fractit expands to new index markets — ALDREIT (Abu Dhabi), SGREIT (Singapore), and HKREIT (Hong Kong) — each product will carry its own jurisdiction controls mapped to the regulatory requirements of that market. The same on-chain enforcement model applies across all products.

***

> **Note:** Users are solely responsible for determining whether their participation in Fractit is lawful in their jurisdiction. Nothing in this documentation constitutes legal advice.