Security at Cyrigo
How we protect the Cyrigo platform and your data: hosting, access control, monitoring, backups, incident handling, use of AI and privacy.
Last updated
22 October 2026
At a glance
Data in the EU/EEA
Hosted in an ISO 27001-certified data centre, with all customer data stored and processed in the EU/EEA.
Encrypted connections
All traffic is encrypted with modern TLS, and backups are encrypted.
Single sign-on and MFA
Sign in with Microsoft Entra ID or with multi-factor authentication.
Backups every 4 hours
Plus daily encrypted copies, stored separately in Norway.
Tested every year
An annual penetration test, plus regular vulnerability scanning.
You decide on AI
We never send your data to AI services unless you choose to.
Our approach
Security is built into how we develop and run the Cyrigo platform. We follow ISO/IEC 27001 as our principal standard for information security management and are working towards certification.
We take a risk-based approach and keep a clear overview of our suppliers, systems and security controls, which we manage in our own platform. Company devices and identities are centrally managed with strong authentication.
Hosting and data location
The platform runs in an ISO 27001-certified data centre in Denmark, and daily backup copies are stored separately in Norway. All customer data is stored and processed in the EU/EEA. The data centre has 24/7 monitoring, physical security and redundant power and network connections, and DDoS protection stops attacks before they reach our servers.
Every server is built from the same standardised, automated setup, so all environments are configured the same way.
Access control
Your users can sign in with single sign-on through your own Microsoft Entra ID, using your own policies for multi-factor authentication and sessions. Password sign-in is protected by multi-factor authentication with an authenticator app, strong password requirements, secure password storage and automatic lockout after repeated failed attempts.
Role-based access control gives each user only the access they need, and a built-in audit log lets you follow up activity yourself.
On our side, access to production systems is limited to a few named people, requires VPN and multi-factor authentication, and is logged and traceable to individuals. We only access customer data when it’s needed to solve a specific support or operational task.
Infrastructure and monitoring
Firewalls that only allow necessary traffic, and a web application firewall against common attacks.
Automatic blocking of malicious traffic and repeated sign-in attempts.
Hardened servers where services run with minimal privileges.
Critical security updates installed without undue delay, plus weekly automated maintenance.
Centralised logging, endpoint detection and response (EDR) and uptime monitoring with automatic alerts.
Logs that can’t be altered, kept for at least six months.
Backup and recovery
Backups are taken automatically every four hours, and daily encrypted copies are stored separately in Norway. Our backup and restore routines are tested periodically, and our target is to restore the service within the same working day.
Secure development
Development, test, staging and production are kept separate. Every change is reviewed and tested before it reaches production, we develop with the OWASP Top 10 in mind, and we monitor our dependencies for known vulnerabilities.
The platform is scanned regularly for vulnerabilities, and a penetration test is carried out once a year.
Use of AI
We use AI tools to support development and operations, for example to write and review code and to troubleshoot errors. We don’t use AI to analyse your data, profile users or track how the service is used, and your data is never used to train AI models.
AI tools never receive personal data or your content. When we test changes such as database migrations, we use synthetic or anonymised data. When we troubleshoot an error, we remove personal data and customer content from logs before sharing anything, and share only the technical details needed to solve the problem. We only use business AI services whose terms exclude our inputs from model training.
This describes our own use of AI. You can connect your own AI assistant through our MCP server once your administrator has switched it on. The assistant reads only what the user behind its access token may read, and nothing it suggests reaches a register until a person with the right to do so publishes it. What the assistant reads is processed by your AI provider under your agreement with them, not by Cyrigo.
Incident handling
We have established routines for handling incidents. If an incident could affect your data or the service, we notify you without undue delay, also while we’re still investigating. Personal data breaches are handled in line with the GDPR and our data processing agreement.
Privacy and GDPR
We process personal data on your behalf as a data processor, under a data processing agreement. All customer data is stored and processed in the EU/EEA. Our subprocessors are established in the EU/EEA or in NATO countries, and any transfer outside the EU/EEA has a valid legal basis under the GDPR, such as the European Commission’s standard contractual clauses.
You can export your data at any time. When the agreement ends, you can retrieve your data for 30 days, after which it is irreversibly deleted from the platform. Backups are deleted on their fixed rotation. We confirm the deletion in writing.
Our subprocessors and the other suppliers we use are listed in our privacy policy. The binding list for the platform is Annex 1 to our data processing agreement, and we notify customers before we replace or add a subprocessor.
People and partners
Our team is small, stable and based in Norway, and access to systems and data is limited to a few named people. All personnel have signed confidentiality agreements and receive regular security awareness training. We operate our infrastructure together with our Norwegian partner, Offcenit AS.
Contact and documents
Report a vulnerability
If you think you’ve found a security vulnerability in the Cyrigo platform or on our website, please email security@cyrigo.com with a description and the steps to reproduce it. Please don’t access other people’s data or disrupt the service while testing, and give us reasonable time to fix the issue before sharing it publicly.
Request documentation
Customers and prospective customers can request our detailed security and operations description and our data processing agreement at contact@cyrigo.com.
