> For the complete documentation index, see [llms.txt](https://bify.gitbook.io/rwa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bify.gitbook.io/rwa-docs/bify-rwa/security.md).

# RWA Security

## Eligibility

RWA purchases are restricted by identity, compliance, jurisdiction, offering terms, and issuer status. These controls are evaluated before purchase and remain relevant to permissioned token transfers.

## Wallet authentication

Portal access requires a signed challenge and a backend session. The wallet address is associated with the authenticated role and issuer or investor record; it is not accepted as an authorization claim by itself.

## Data protection

Identity and customer records are encrypted at rest. Personal data and KYC documents remain off-chain. Contracts use identity claims, status flags, and hashes rather than raw documents or personal data.

## Contract controls

The RWA contracts enforce issuer roles, identity registry membership, compliance rules, supply, price, purchase state, certificate state, and redemption permissions. Administration keys and signing keys are held in protected deployment infrastructure.


---

# 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://bify.gitbook.io/rwa-docs/bify-rwa/security.md?ask=<question>&goal=<endgoal>
```

`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.