AI Security Controls
AI security controls for prompt injection, post-quantum cryptography, EU data residency, and customer-held keys, with scope tied to deployment and contract.
Dweve security and privacy
Dweve describes controls for prompt injection, jailbreaks, model extraction, context-aware PII detection, post-quantum terminology and supported customer-held keys. An EU-only deployment posture is available for defined scopes; data coverage and privacy responsibilities depend on the deployment and contract.
- The page maps controls to security questions, but a control description is not a certification or a universal compliance result.
- Review the Trust and technical records for the applicable scope, status, owner and evidence before making a deployment decision.
Choose the audience that matches your question
The page contains three selectable readings of the same subject.
For consumers
Dweve describes security controls for a selected deployment, including access controls, data handling and configured protection against malicious input. The deployment and contract decide what applies; Trust records provide the next evidence layer.
For businesses
A Dweve security review asks where data goes, who can access it, who holds keys, how personal data is handled and how long encryption remains useful. EU-only posture and control coverage are available only for defined scopes.
For engineers
The security route documents controls for prompt injection, jailbreaks, model extraction, context-aware PII detection, post-quantum algorithms and BYOK for supported providers. Data coverage and privacy responsibilities remain deployment- and contract-scoped.