Consent, security, accuracy, and residency. Explicit, auditable, and the same line items your CISO or GC already asks about.
Permissions and ACL
Permissions are checked at query time, not at index time. A permission revoked five minutes ago is honoured five seconds later. Every retrieved chunk carries its source-system ACL: SharePoint inheritance chains, Google Drive sharing scopes, Confluence space permissions, GitHub repo and branch protections, Jira project roles, Salesforce sharing rules, NetSuite roles. The retriever filters candidate chunks against the asker's resolved group membership before any LLM call. The index itself is encrypted per tenant and segmented by ACL group, so a misrouted query cannot leak a chunk it should not see.
Data residency
Pick where the brain lives. On-prem on your hardware. Single-tenant VPC in AWS, Azure, or GCP in the region you name: Frankfurt, Mumbai, Singapore, Virginia, São Paulo, Sydney. Or a node we provision in a sovereign cloud where one is required. All embeddings, vectors, logs, and model traffic stay inside that boundary. Keys are held in your KMS or HSM. We never see them. SOC 2 Type II, ISO 27001, and HIPAA-ready controls. GDPR DPA and India DPDP addenda signed at order. No training on your data, ever.
Citation discipline
Answers are grounded at the paragraph anchor or function range, not the document. The generator is constrained to quote only chunks the retriever returned, and a separate verifier rejects any sentence whose claim is not supported by a cited chunk. When the corpus has nothing relevant, the agent refuses and says so, instead of guessing. When two sources disagree, both are shown with dates and the asker is told there is a conflict. Every cite carries a freshness stamp. If the source is older than the policy half-life for that doc type, the answer leads with a stale warning.