Security and sovereignty, by design.
Qriton is built for organisations that must control where data goes, who decides, and how every decision can be reviewed later.
Your perimeter
Deployed where your data lives. There is no Qriton-hosted copy of your data.
Policy first
Outbound connections are restricted by default and only made where your policy allows.
People in charge
Low-confidence or consequential cases go to an accountable reviewer.
Evidence by default
Decision records, run records and receipts, kept in your environment.
Security controls.
- Identity and sign-on
- Deploys behind your identity provider or zero-trust gateway, so your sign-on and MFA policies apply first.
- Access
- Passwordless sign-in for people and individually issued keys for systems. No shared credentials.
- Encryption
- Encrypted in transit throughout. At rest, data stays in your storage under your own keys.
- Outbound access
- Validated against your policy. Every connection is recorded.
- Audit
- Runs and decisions recorded end to end, exportable for review.
Built for the EU AI Act.
Qriton Signals took part in EUSAiR, the EU-funded pilot for EU AI Act regulatory sandboxes, from January to July 2026, and completed a structured self-assessment of human oversight under Article 14.
Article 12
Record-keeping: decision and run records, kept together and available for review.
Article 13
Transparency: answers cite their sources, and each exchange is recorded in a tamper-evident audit log.
Article 14
Human oversight: review thresholds, approvals and refusals when evidence is missing.
Article 15
Robustness and cybersecurity: Qriton Shield for server defense, and controlled, recorded changes.
Qriton supports these obligations. Compliance depends on how the whole system is designed, deployed and run.
Runs where your data lives.
Vulnerability disclosure
Found a security issue in a Qriton service? Email hello@qriton.com. We acknowledge within three working days, keep you updated until it is fixed, and will not take legal action over good-faith research that avoids privacy harm, data loss and service disruption. Please give us reasonable time to fix before publishing. Machine-readable: security.txt.