Trust

Security at Shieldra

What Shieldra does today to protect customer data, and what it has not done yet. Questions go to security@shieldra.ai.

Key takeaways

  • Customer records are scoped to their workspace in application queries; a CI lint fails the build on unscoped queries.
  • HTTPS everywhere with HSTS preload on www.shieldra.ai; MFA secrets, AI-provider API keys and newly saved integration credentials are additionally encrypted at the application layer.
  • MFA for every user, with an MFA-required policy on new workspaces; SSO is on the roadmap.
  • New audit-log entries (since September 2026) are hash-chained with SHA-256; older entries are reported as an unverified legacy segment.
  • Shieldra has not completed a third-party audit yet.

Tenant isolation

Customer records are scoped to their workspace in application queries. A lint in CI fails the build when a new query on tenant data is not scoped, and regression tests seed two workspaces and check that one cannot read or change the other’s data.

Encryption

All traffic is served over HTTPS, with HSTS (including preload) on www.shieldra.ai. Stored data is encrypted at rest by our database and object-storage providers, listed on the sub-processors page. Multi-factor authentication secrets, AI-provider API keys and newly saved integration credentials are additionally encrypted at the application layer.

Access control

Role-based access control inside each workspace. MFA is available to every user (authenticator app, email codes and backup codes). New workspaces start with an MFA-required policy, which workspace admins can adjust. SSO is on the roadmap.

Audit log

Security-relevant actions are written to an audit log. Since September 2026 each new entry stores the SHA-256 hash of the previous one, so an edited or removed entry breaks the chain, and admins can run an integrity check from the app. Entries written before sealing was in place are reported separately as an unverified legacy segment, never counted as verified. Removing the newest entries cannot be detected without an external anchor.

Incidents

Our security program includes incident response procedures aligned with NIST SP 800-61. If a personal-data breach affects you, we notify you without undue delay and within 72 hours, as our Data Processing Addendum commits.

Vulnerability reports

We accept responsible disclosure at security@shieldra.ai and publish a security.txt file.

Compliance posture

Shieldra has not completed a third-party audit. When we engage an audit firm, we will name it and the observation-window dates here.

FrameworkStatus
SOC 2 Type IINot yet audited
ISO 27001Not yet audited
HITRUST CSFNot yet audited
HIPAANo-PHI service by default; BAA only by separate written agreement
GDPRDPA available, with Standard Contractual Clauses

Frequently asked questions

How is customer data kept separate between customers?

Customer records are scoped to their workspace in application queries. A CI lint fails the build on new unscoped queries, and two-tenant regression tests check that one workspace cannot read or change another’s data.

Does Shieldra support SSO and MFA?

MFA is available to every user, and new workspaces start with an MFA-required policy that admins can adjust. SSO is on the roadmap; it is not available today.

How do I report a security vulnerability?

Email security@shieldra.ai with steps to reproduce. Please do not test against other customers’ data.

Is Shieldra SOC 2 certified?

No. Shieldra has not completed a third-party audit; SOC 2 Type II, ISO 27001 and HITRUST CSF are not yet audited.