Security at Seqora

Last updated: July 31, 2026

Security is the product

Seqora is built by a practicing security engineer with 9+ years in enterprise security. The same standards we help clients meet are the standards we hold ourselves to.

Our practices

All traffic to seqora.app is encrypted in transit with TLS. The platform is being built with least-privilege access, MFA on all administrative accounts, encrypted storage, and a minimal data footprint. We collect only what the product needs to function.

What Seqora is not for

Seqora is a compliance workspace, not a clinical system. It is not designed to hold protected health information, we do not offer a Business Associate Agreement, and you should not enter patient records or identifiers into it.

This is a deliberate choice rather than a gap we have not gotten to. An assessment, a risk register and a board report describe your systems, vendors, policies and controls. None of that work requires patient data, so the product does not ask for it and should not receive it.

We would rather say this plainly than let the absence of a claim be mistaken for the presence of one.

During private beta

Seqora is in private beta. Founding members will receive documentation of our security architecture, data handling practices, and subprocessor list as part of onboarding. Formal certifications (SOC 2) are on the roadmap as the platform matures.

Reporting a vulnerability

If you believe you've found a security issue in seqora.app, we want to hear about it. Email tony@seqora.app with details. We'll acknowledge within 48 hours, and we won't pursue action against good-faith research.

Contact

Security questions: tony@seqora.app