Praesidia Trust Center
One page for security reviewers and procurement: what we attest to today, where customer data is processed, how to verify our audit evidence, and who to contact.
Security review kit
Everything a security reviewer or procurement team usually asks for first, in one list. Each link goes to the published source.
- Security status table — where each control stands today, plus SOC 2, ISO/IEC 27001 and penetration test status.
- Hosting & data location — the operating company, the production host and other documented providers.
- Service provider inventory — the technical list of subprocessors.
- Architecture — how the system is put together.
- Security controls — per-agent identity, tenant isolation, SSO and SCIM, guardrails, vaulted secrets.
- Verify your audit trail — check exported audit evidence offline, and what the check does not prove.
- Framework control mappings — mappings that support your assessment, not certification.
- Vulnerability disclosure — how to report an issue safely.
Have a questionnaire? Send it to security@praesidia.ai with the format you work from, the deployment you are evaluating and your deadline. The DPA is available on request from legal@praesidia.ai. Want to see the product first? Book a demo.
Where each control stands today
One table, four statuses: available now, in progress, planned, and not certified or not published. Nothing moves up a bucket until it is true.
| Capability | Status |
|---|---|
| Available now | |
| Encryption in transit and at rest | Yes |
| Tenant isolation | Yes — org-scoped on every request |
| MFA (TOTP) | Yes — all plans |
| Passkeys (WebAuthn) | Yes — all plans |
| Single sign-on (SAML/OIDC) | Yes — Enterprise plan |
| SCIM 2.0 provisioning | Yes — Enterprise plan |
| Signed outbound webhooks | Yes |
| Audit verification (signatures + hash chain) | Yes — under the default configuration; how to check it offline |
| Production hosting | Amazon Web Services, eu-central-1 (Frankfurt, Germany) — details |
| Service provider inventory | Published — technical list |
| Vulnerability disclosure | Published — policy and security.txt |
| DPA | Available on request from legal@praesidia.ai |
| Data retention | No period is published here; available on request via security review |
| Software bill of materials (SBOM) | Available on request via security review |
| In progress | |
| Nothing is listed here until work has started. | |
| Planned | |
| Nothing is listed here until it has been scheduled. | |
| Not certified or not published | |
| SOC 2 | Not certified — none published |
| ISO/IEC 27001 | Not certified — none published |
| External penetration test | Not published. No third-party penetration test has been published. |
| HIPAA Business Associate Agreement | Not offered. Praesidia does not sign BAAs today. Do not send protected health information (PHI) to the service. |
| Public status page | Not published — Praesidia does not operate a public status page today. |
| Dedicated single-tenant instance | Not in production — scoped per signed engagement; deployment options |
| Live failover drill | Not yet exercised — what is tested today |
Praesidia does not currently publish a SOC 2 report or an ISO/IEC 27001 certificate. We say this plainly so that your assessment starts from the right baseline. What we publish instead is a control mapping per framework on the compliance hub; mappings support your assessment and are not certification.
The controls behind these answers — per-agent identity, tenant isolation, SSO and SCIM, guardrails, vaulted secrets — are described on the security overview.
Where customer data is processed
Praesidia is built and operated by Squad Technology SRL, registered in Cluj-Napoca, Romania, so it operates under GDPR as an EU company. Registration details are on the About page.
Praesidia's production app, API, MCP server and model gateway run on Amazon Web Services in the eu-central-1 region (Frankfurt, Germany), and the data those services store is held in that region. The website and the app are delivered through Amazon CloudFront, which terminates TLS at edge locations in North America, Europe and Israel before requests reach Frankfurt, so we do not describe the data path as EU-only end to end; API, MCP and gateway connections terminate TLS in Frankfurt. Cloudflare provides DNS only and does not carry requests.
Other documented providers are Stripe (billing), Sentry (error monitoring, when configured), Sigstore Rekor (transparency-log anchoring, when external anchoring is enabled), OpenAI (model inference only when an organization uses the platform-configured default rather than its own provider connection, and guardrail screening when configured), Anthropic (guardrail content evaluation, when configured), and Microsoft Azure AI Content Safety (guardrail content moderation, when configured).
The service provider inventory lists each provider, what it is used for, and the region of every Amazon Web Services service production runs on. Beyond those regions and the OpenAI processing region for platform-configured calls, it does not assert provider regions, transfer mechanisms, or negotiated legal roles. Data-residency options are discussed during evaluation; reviewed contractual information is available from legal@praesidia.ai.
Verify our audit evidence without trusting us
Audit records are signed under the default configuration, which an operator can turn off. Every exported compliance bundle can then be checked by your team or your auditor with an Apache-2.0, dependency-free command-line verifier that runs fully offline and never calls our servers.
It confirms every signature and tamper check and — when external anchoring is enabled — the Sigstore Rekor anchor, a public log we do not control. It also states what it does not prove.
What is measured, and what recovery looks like
Each organization can see its own task success rate, average task latency, and agent availability for a time window it chooses — scoped to that organization's data only, never a fleet-wide view.
An organization can configure up to three alert thresholds — for success rate, availability, or latency — checked every few minutes; threshold alerts go to a webhook at a URL the organization supplies.
A recovery drill we run restores a backup into a clean environment and verifies that the platform reports itself unhealthy when it loses its connection to one of its own data stores, and recovers on its own, without a restart, once the connection returns.
We do not claim automatic failover for today's production deployment, and no live failover drill has been run.
Availability commitments, response times, and support severities are set contractually, not published as a general number here — talk to us.
Terms, privacy, and data processing
Terms of service, privacy policy, and the data processing agreement are available on request. Email legal@praesidia.ai with the documents you need. Technical privacy questions go to privacy@praesidia.ai.
Found a vulnerability? Tell us
The disclosure policy explains what to include, which systems the channel covers, and how to keep testing safe. Machine-readable details: /.well-known/security.txt.
Working through a vendor assessment?
Send questionnaires and architecture questions to security@praesidia.ai. Include the questionnaire format, the deployment you are evaluating, and your deadline, so the reply is useful the first time.
How the system is put together is documented on the architecture page. For everything else, see Contact.
The full control list, in one place
Every control the platform provides, and how it maps to the frameworks you are measured against.