Processing, storage and failover can be confined to one agreed region or named geography. The actual model, endpoint, subprocessor and transfer path are recorded; a provider region label is not enough.
Eligible inference paths use 0-day prompt and response retention. Files, retrieval state, embeddings, traces, logs and backups are separate components with their own approved storage, key and deletion rules.
All YPAI-controlled persistent data can use customer-managed keys. Provider-side key coverage is confirmed for each selected service and feature.
Architecture can support legal and regulatory obligations. Architecture alone does not establish compliance.