Security and trust
Where Armalo data lives, how it is kept apart, and who can reach it. The tables below list our hosts, what we store, and every subprocessor.
The short version
Hosting and data residency
Armalo runs on Amazon Web Services in the us-west-2 region (Oregon), behind a global edge network at the public edge; the edge provider is named in the subprocessor list. There is no EU hosting today.
Encryption
Traffic is encrypted in transit at the edge. Long-term storage and backups are encrypted. Connected-account credentials sit in an encrypted vault, and the AI never receives your actual credential.
Access and isolation
Each workspace is separate from the others. Members see data according to their workspace role. Armalo staff have limited access, only for support or incident response.
Certifications and agreements
Certifications and agreements
Armalo itself is not SOC 2 certified. Any certification held by a provider belongs to that provider, not to Armalo. Security monitoring and compliance evidence are in design partner today.
Our Data Processing Addendum covers processor duties, transfers, breach notice, audits, and deletion. The subprocessor list names every provider that handles customer data.
Where Armalo is listed
Listed in the Cloud Security Alliance’s Agentic AI startup showcase. A listing is not a certification.
Where your data lives and who can touch it
The hosting table, residency matrix, and subprocessor list below answer the questions an enterprise buyer brings to this page: where your data lives, how long we keep it, and who can access it.
Quarterly review cadence, owner: Armalo security team security@armalo.ai
Hosting & infrastructure
Armalo runs on Amazon Web Services in the us-west-2 region (Oregon), behind a global edge network at the public edge. Application servers, the account database, and long-term storage are separate parts of that setup. Armalo itself is not SOC 2 certified. A certification held by a provider belongs to that provider, not to Armalo.
| Hosting | Component | Data type | Region | Compliance posture | Legal-review status |
|---|---|---|---|---|---|
| Application and work servers (AWS) | Sign-in and identity, workspace separation, permissions, billing, audit records, secrets storage, workspace rules, conversation history, and the servers where customer work runs | Account details, organization and workspace details, workspace conversation history, permission settings, usage records, temporary work state, a working copy of your code, build files | United States (AWS us-west-2) | Covered by the provider's contractual and data-processing terms | Pending |
| Database (AWS RDS) | The account database for workspaces, conversation history, billing records, and audit records | Account, organization, and workspace details, conversation history, permission settings, usage records, audit entries | United States (AWS us-west-2) | Covered by the provider's contractual and data-processing terms | Pending |
| Encrypted long-term storage (AWS) | Long-term encrypted storage for approved work results, backups, long-term audit exports, image files, and saved copies | Encrypted files and file details | United States (AWS us-west-2) | Covered by the provider's contractual and data-processing terms | Pending |
| Public edge network (Cloudflare) | TLS termination, proxying, traffic filtering, DNS | IP address, request metadata, TLS session metadata, cached public responses where configured | Global network | Covered by the provider's contractual and data-processing terms | Reviewed |
Data residency matrix
Your saved account and workspace data and your temporary work files live in different places and have different deletion paths. Backups are kept in the same region as the data they copy.
| Data class | Where stored | Default retention | Who can access | Deletion path |
|---|---|---|---|---|
| Workspace conversation log | Stored in Armalo's account database; encrypted backups in encrypted storage | Routine conversation retention: active for the life of the workspace plus 90 days after the conversation. Workspace deletion or an accepted erasure request removes data in live systems within 30 days; database backups rotate at 7 days | Workspace members, according to their workspace role; Armalo staff with limited access, for support or incident response; the AI receives only the context for its own task | Delete workspace or submit an erasure request; policy requires removal on workspace deletion or accepted erasure; database backup copies expire within the 7-day rotation after live deletion; today we confirm each removal through a direct request; automatic removal at the routine window is not yet in place |
| User-uploaded files | Encrypted storage; temporary working copies inside your private work area | Active for the life of the workspace; 30 days after deletion request; temporary work-area copies expire when the work area is deleted | Workspace members, according to their workspace role; the AI only when you grant the file to its task; Armalo staff with limited access, during support or incident response | Delete the file or workspace, or revoke the AI's access to it; uploaded files are not currently backed up, so deleting the stored file is final |
| Generated code artifacts | Workspace code storage and encrypted storage; temporary build files in the work area | Active while attached to the workspace or its code storage; 30 days after workspace deletion; work-area output lasts only until it is saved to the workspace or the work area is deleted | Workspace members; connected code host; the AI, when it has access to your code; Armalo staff with limited access, during support | Delete from code storage and the workspace artifact store; delete the work area; request workspace erasure - Armalo keeps no independent backup copy of generated artifacts beyond workspace code storage and our encrypted storage, so deletion removes every copy Armalo holds; copies at a connected code host follow that host's retention |
| Integration credentials | An encrypted vault for your connected accounts; the AI receives only short-lived, limited access | Your stored credential stays until you revoke it, replace it, disconnect the integration, or delete the workspace; the AI's short-lived access expires at its set deadline | Owners and Admins you authorize manage the connection; Armalo issues the AI's access; the AI never receives your actual credential | Disconnect the integration, revoke access at the provider, replace the secret, or delete the workspace; any short-lived access still open is revoked or left to expire |
| Workspace audit logs | Workspace audit log in Armalo's account database, where entries are added and never edited; Enterprise exports may be copied to your own destination | 30 days by default; Enterprise override available | Owner and Admin by default; a security Viewer role where you configure one; Armalo security staff with limited access, for incident response | Automatic daily removal after the 30-day window; the workspace deletion process; you control how long Enterprise exports are kept |
| Request logs | Log of tool use in Armalo's account database; entries are added and never edited | No automatic expiry yet; these records are append-only | Armalo security staff with limited access, for incident response; authorized admins through the admin audit log | Not yet deletable on request; if a request covers them, we will tell you |
| Billing data | Armalo's account database, for your usage records and account link; Stripe for payment processing and regulated payment records | Usage ledger retained while the account is active and as needed for accounting, tax, dispute, and legal obligations; payment-card data remains with Stripe | Owner and billing Admin; Armalo's billing team; Stripe for payment processing | Close account and request deletion; Armalo removes data not subject to legal retention; Stripe follows its contractual and legal deletion obligations |
| Telemetry | Armalo's monitoring systems and encrypted storage; our providers' own monitoring where it applies | Our policy target: monitoring data that can identify a workspace is kept up to 30 days unless needed for an active incident; automatic expiry is not yet in place; combined, anonymous metrics may be kept indefinitely | Armalo engineering, reliability, and security staff with limited access; workspace administrators, for views inside their own workspace | Scheduled expiry is not yet automatic; policy requires removal of workspace-linked records on account deletion, and today we confirm removal through a direct request; combined, anonymous metrics cannot be linked back to a workspace |
Residency controls
- The United States is the only region where Armalo stores long-term data today.
- All hosting is in the AWS us-west-2 region (Oregon) today; there is no EU hosting.
- Request details at the public edge follow the edge provider's global network.
- When a model runs, your data may be processed in another location. The provider you select and your account determine that location.
Subprocessors
A provider receives only the data needed for its purpose. This list is current as of 2026-10-21; it may evolve as Armalo adds regions, integrations, models, and delivery providers. Notice is provided through the DPA or customer agreement where required.
| Subprocessor | Purpose | Data shared | Region | DPA status | Legal-review status |
|---|---|---|---|---|---|
| Amazon Web Services (AWS) | Hosting for account services and customer work, the account database, long-term storage, backups, secrets storage, and model inference through Amazon Bedrock | Encrypted customer data, account and workspace details, conversation history, work results, audit records, system monitoring data, and the prompts sent for Bedrock model requests | United States (AWS us-west-2) | AWS terms apply; the data-processing terms are under review | Pending |
| Cloudflare | Edge proxy, TLS termination, traffic filtering, DNS | IP address, request metadata, TLS metadata, public response data, DNS query metadata | Global edge | DPA available; transfer terms governed by Cloudflare agreement | Reviewed |
| Stripe | Subscription billing, invoices, payment processing | Customer name, billing contact, plan, invoice data, payment method data handled by Stripe, transaction status | Stripe service regions, including US processing | Stripe DPA available; payment data governed by Stripe terms | Reviewed |
| OpenAI | Model processing when selected | Prompt and context required for the model request; generated response; request metadata | Provider-selected region or customer-contracted region | The provider's DPA applies when Armalo runs the model; if you bring your own key, your agreement with the provider also applies | Reviewed |
| Anthropic | Model processing when selected | Prompt and context required for the model request; generated response; request metadata | Provider-selected region or customer-contracted region | The provider's DPA applies when Armalo runs the model; if you bring your own key, your agreement with the provider also applies | Reviewed |
| Model processing when Gemini is selected | Prompt and context required for the model request; generated response; request metadata | Provider-selected region or customer-contracted region | The provider's DPA applies when Armalo runs the model; if you bring your own key, your agreement with the provider also applies | Reviewed | |
| Google Workspace | Identity and organization sign-in, and email delivery through Gmail | Email address, display name, account identifier, sign-in details, organization-domain metadata, outgoing email content and recipients | Google global service | Google Workspace or Google data terms apply; customer agreement may govern BYO identity | Reviewed |
| GitHub | Code connection, download, and sync of changes and review requests | Code project details, selected source code, change history, installation identity, limited-access code token | GitHub service regions | GitHub DPA available; customer may connect its own organization agreement | Reviewed |
| PostHog | Product analytics | Product usage events and browser metadata | Provider service regions | The provider's data terms apply | Reviewed |
Report a vulnerability
Report a vulnerability
Found something we should know about? Email security@armalo.ai with what you found, where you found it, and how to reproduce it. We read every report and confirm we have received it.
Email security@armalo.ai