OrgMCP

Trust Center

Last updated: 2026-08-12

OrgMCP is a multi-tenant hosted Model Context Protocol server operated by Werkdata OÜ (Estonia). This page is a single place to review how we protect customer data and where to find the authoritative policy behind each claim. We keep it honest: where a control is in progress rather than complete, we say so.

Data residency

All Customer Data is stored in AWS eu-central-1 (Frankfurt) by default, keeping data within the EU. A small amount of operational metadata is processed by sub-processors outside the EEA (for example WorkOS and Stripe); those transfers rely on the EU-US Data Privacy Framework and/or Standard Contractual Clauses with supplementary measures. Custom regions are available on the Enterprise plan.

Details: Privacy Policy — International transfers and Sub-processors (Annex III).

Encryption

  • In transit: TLS 1.2+ terminated at the load balancer, with HSTS.
  • At rest: RDS Postgres storage encryption and S3 SSE-KMS.
  • Connector credentials: per-tenant OAuth tokens are stored as AWS-KMS-encrypted secrets using envelope encryption, isolated per workspace, and never written to logs.

Details: Privacy Policy — Security.

Tenant isolation

Every workspace is isolated at the database layer with PostgreSQL row-level security (FORCE ROW LEVEL SECURITY), scoped by a per-request tenant context. On top of that, every knowledge-retrieval query carries a mandatory server-side audience filter (tenant + groups + user) applied in middleware, so one team cannot see another team's documents — even by accident.

Availability & disaster recovery

The application runs on autoscaling ECS behind a load balancer in private subnets. Encrypted RDS backups run automatically with point-in-time recovery, and a daily cross-region backup copy is replicated to eu-west-1.

Our most recent restore drill (staging, 2026-07 GA-readiness sign-off) measured RTO ≈ 37 minutes and RPO ≈ 5.6 minutes, both inside target. These are point-in-time drill figures, not a contractual SLA; contractual uptime commitments are defined per plan (99.9% on Enterprise).

Live reachability and incident history: /status and status.orgmcp.io.

Application security

  • Edge protection: AWS WAFv2 in front of the load balancer with AWS managed rule sets (Common, Known-Bad-Inputs, SQLi) and per-IP rate limiting.
  • Rate limiting: per-user and per-plan request ceilings, with denied attempts recorded to the audit log.
  • Authentication: WorkOS AuthKit with sealed-session cookies is the only user-auth path; MFA and SSO/SCIM are available through WorkOS. Programmatic access is served by an OAuth 2.1 authorization server.
  • Error monitoring: Sentry with request bodies scrubbed and PII kept out of events.
  • Audit log: per-tenant, RLS-isolated record of security-relevant events (logins, invites, role changes, connector edits, deletions), exportable on Business and Enterprise plans.

To report a vulnerability, see our Security & Responsible Disclosure policy or the machine-readable contact at /.well-known/security.txt (RFC 9116).

Privacy & compliance

OrgMCP is designed to comply with the EU GDPR and UK GDPR. Workspace owners can export their data (GDPR Art. 15/20) and schedule deletion (Art. 17) self-serve, with a 30-day soft-delete window before permanent purge.

Certifications & attestations

We want to be precise here, because it matters: OrgMCP is not currently SOC 2 certified and holds no third-party security certification.

  • SOC 2: in progress / on our roadmap. We have mapped our controls to the SOC 2 Trust Services Criteria and are preparing for a Type I observation window; no report exists yet.
  • Independent penetration test: planned; scope defined but not yet executed.

We will update this page as soon as either milestone is complete. In the meantime, we are happy to walk security reviewers through our architecture and controls — email security@orgmcp.io.

Contact