> For the complete documentation index, see [llms.txt](https://docs.apacx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apacx.io/xafer-waas/xafer-waas/compliance-and-ops.md).
# Compliance & Ops
### KYB/AML Policies
Xafer follows internationally recognized KYB and AML standards, aligned with partner banks, payment gateways, and exchanges. For enterprise-facing use cases, we support:
* Business identity verification (e.g. incorporation docs, directors, registration data)
* Configurable risk monitoring for transaction patterns and fund movements
We also enable integration with custom AML engines, allowing clients to correlate on-chain activity with off-chain data for advanced risk screening.
### Compliance Support for Ecosystem Partners
Xafer extends its compliance infrastructure to partners across the ecosystem. With standardized onboarding and tooling, we offer:
* KYB/AML policy templates and process documentation
* Embedded risk APIs and webhook callbacks
* Response assistance for regulatory events (e.g. emergency freezes, investigations)
* Periodic risk reviews and security advisory reports
This helps wallets, SaaS providers, and Web3 platforms quickly close compliance gaps and accelerate time to market.
### Data Privacy & Encryption Standards
Xafer adheres to global standards like GDPR, ISO/IEC 27001, and NIST to safeguard data confidentiality and integrity. Our privacy practices include:
* TLS encryption for all data in transit
* AES-256 encryption for stored data with strict access controls
* No full key material ever exists—MPC shards are processed only in memory
Our infrastructure ensures that sensitive data never leaks, persists, or crosses boundaries unnecessarily.
### Service Level Agreement & Operational Resilience
Xafer offers enterprise-grade SLAs and an operations framework to support mission-critical wallet workflows:
* 99.9% uptime guarantee with redundant API clusters
* Real-time monitoring and 24/7 technical incident response
* Auto-scaling for signing services to handle usage spikes
* Regularly tested disaster recovery plans with validated RTO/RPO metrics
Custom operational alerts (e.g. via Slack, email, webhook) are also supported to ensure seamless business continuity for clients.
\
\
\
\
---
# 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.apacx.io/xafer-waas/xafer-waas/compliance-and-ops.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.