We use essential cookies to run this site. With your permission, we'd also like to use analytics cookies to see how the site is used, and functional cookies for chat and videos. Change your choice any time under Cookie settings. Read our Cookies Policy
Trust Center
You’re trusting us with a view of your infrastructure. Here’s exactly what we collect, where it lives and how we protect it.
Your environment
SeqOps
Cloud accounts connect with read-only permissions. SeqOps can’t change your cloud environment.
The server agent connects out over HTTPS on port 443 (Windows servers also use port 8443 while being provisioned). No inbound ports, no cloud credentials on the server.
Configurations, software versions, security settings and results. Not your application data.
Amazon Web Services, eu-north-1 (Stockholm, Sweden).
AWS (hosting), Stripe (payments), Sentry (error monitoring).
SeqOps AB, Tynäsgatan 12 a, 652 16 Karlstad, Sweden.
TLS for all connections.
Cloud credentials and agent secrets are encrypted before storage; passwords and API keys are stored as one-way hashes. Download links are signed and short-lived.
Multi-factor authentication with an authenticator app or email code.
Each organisation’s admins can see who did what and when, including partner sessions.
Role-based access for the people in your organisation.
Access is revoked the same day. You have 30 days to export your data, after which it’s deleted through an approved deletion process (suspended only under legal hold).
Our Data Processing Agreement is in the legal hub.
When a partner opens a customer workspace, SeqOps asks for a reason first. The session is recorded in the customer’s audit log.

SeqOps doesn’t hold SOC 2 or ISO 27001 certification today.
Our platform and processes are designed with those frameworks in mind.
Not yet offered: single sign-on (SAML/SSO) and SCIM provisioning, and a public status page.
Found a security issue in SeqOps? Email support@seqops.io.
Machine-readable contact details: security.txt.