Security at StrataSpace
Last updated: November 9, 2026
StrataSpace, Inc. (“StrataSpace”) operates a multi-tenant collaborative document platform. This page summarizes the controls that protect customer data and the disclosures we make about how the platform is built and operated. For contractual commitments see the Terms of Service and the Privacy Policy.
1. Encryption in transit and at rest
All client traffic to StrataSpace is served over HTTPS with TLS 1.2 or later. Customer document content stored in Amazon S3 is encrypted at rest with AES-256 under one encryption key per environment that StrataSpace manages in AWS Key Management Service, with automatic key rotation. Metadata, presence, comments, and access policies in Amazon DynamoDB are encrypted at rest with AWS-managed keys. Credentials for connected third-party services are sealed under separate StrataSpace-managed keys. Postgres search indexes are hosted on Neon with at-rest encryption enabled. StrataSpace does not offer per-customer encryption keys or customer-managed keys.
2. Tenant isolation
Every request that reads or changes workspace data is authorized by Cedar policies scoped to the user's Company, Organization, Team, and Space membership. A request acts in a company only while the user holds an active membership there. Document content, search results, audit events, and presence are filtered by tenant in application code before leaving the API, and search queries carry a tenant condition. Tenants share the same storage and compute, so isolation is enforced by these application controls and not by separate infrastructure or separate encryption keys per tenant. When an admin or identity provider removes a member from a company, StrataSpace revokes their sessions, refresh tokens, and connected-service credentials. Access changes take effect within 60 seconds.
3. Authentication and access
User authentication is brokered by Amazon Cognito with TOTP-based multi-factor authentication available on every plan and required for company admins on plans where the company MFA policy is enabled. Enterprise customers can enforce SAML or OIDC SSO against their corporate IdP and provision users via SCIM 2.0 with automated deprovisioning on offboarding. Service-to-service access via the Model Context Protocol uses OAuth 2.1 with Dynamic Client Registration and short-lived access tokens.
4. Audit logging
On the Enterprise plan, every mutating API operation emits a structured audit event tagged with actor identity, tenant, resource, action, IP, and timestamp. Audit events are retained for a limited period and are queryable by company admins. Agent-initiated edits are attributed distinctly from user-initiated edits so review of AI activity is unambiguous.
5. Active threat monitoring
StrataSpace runs on Bowshock, an on-call security agent from StrataSpace, Inc. Sensors in our API middleware report suspicious activity, such as requests aimed at internal addresses, reads across tenant boundaries and forged tokens. Once Bowshock has a solid case, it can block an IP address or suspend an account for a limited time, within limits we set. During the day it pages us first. Overnight it acts on its own, with blocks capped at 15 minutes.
We built it after a three-day campaign against our MCP connector in September 2026. Every attempt was denied and no customer data was read. Read what one attacker tried against our MCP connector over three days.
6. Data residency
Production customer data is stored in AWS region us-east-2 (Ohio). Document content lives in S3, metadata and access policies in DynamoDB, and search indexes in Neon Postgres in the same region. StrataSpace does not currently offer EU or APAC data residency. Customers requiring regional residency should contact sales@strata.space.
7. Subprocessors
StrataSpace relies on the following subprocessors to operate the platform. Use of new subprocessors is communicated to active customers under our DPA before they take effect.
- Amazon Web Services, Inc. Compute (ECS Fargate, Lambda), storage (S3, DynamoDB), authentication (Cognito), email, and CDN (CloudFront). All AI model inference and embeddings run on Amazon Bedrock, including Claude, GPT-OSS and Cohere Embed models. Customer content sent to these models stays with AWS. AWS does not share it with the model providers and does not use it to train models.
- Neon, Inc. Managed Postgres hosting for search indexes, which contain document text.
- Stripe, Inc. Payment processing and subscription billing.
- TypeSafe AI. Threat classification for Bowshock, the security layer we own and operate. Receives categories of request events and our own detection rules. Never names, addresses or other identifiers, request bodies or document content.
- Anthropic, PBC. AI models that investigate security events for Bowshock. Receives request metadata such as method, path, headers and timing. Before Anthropic sees it, credentials, tokens and email addresses are removed and IP addresses are replaced with keyed hashes. Never request bodies or document content. Document AI features do not use Anthropic directly. They run on Amazon Bedrock.
- Brave Software, Inc. Web search for AI agents. Off by default for every company. Only a company admin can turn it on. Receives only the search queries an agent writes, which can include words from your documents.
TypeSafe AI and Anthropic receive Bowshock data under commercial API terms that prohibit training on it and limit retention. Integrations you choose to turn on, such as Slack notifications or third-party MCP connectors, send data to those services under your own account with them.
8. Vulnerability reporting
Report security vulnerabilities to security@strata.space. We acknowledge reports within two business days and aim to remediate confirmed high-severity findings within thirty days. Coordinated disclosure is appreciated; please do not publicly disclose unpatched issues.
9. Contact
General security and compliance questions, including DPA requests and subprocessor disclosures, go to security@strata.space.