Contents
Overview
ARMES separates intelligence from memory. AI providers process a request and forget it. Your workspace — chats, notes, files, and personalization — is stored for you, encrypted, until you delete it. Both are true at once.
Personalization is a third, inspectable layer of that workspace: facts your agents can use, visible in Settings, not an advertising profile and not a hidden model about you. This page describes the technical and organizational controls that protect all of it. It is written to be accurate and verifiable — where a control is provided by an infrastructure partner, we say so, and where we are not certified for a given standard, we say that too.
For the legal framing of how we collect and use data, see our Privacy Policy and Terms of Service. For the request-flow deep dive, see our Architecture page.
Encryption
In Transit
All traffic between you, ARMES, and AI providers is encrypted with TLS 1.3 (modern ciphersuites).
At Rest
All data stored on disk — database files, indexes, and backups — is encrypted at rest with AES-256 by our database provider (Supabase, on AWS). This is always on and cannot be disabled.
Private Inference (Zero Data Retention)
ARMES routes every AI request through our gateway (OpenRouter) to endpoints with an enforced zero-data-retention (ZDR) policy. ZDR is enforced at the account level, not left to individual requests. That includes chat completions and the inference used to extract memories, summarize conversations, and build search embeddings. For a full walkthrough, read how private AI inference works.
Glass-Box Personalization
System agents can remember facts about you because those facts live in a user-owned layer of your workspace — not in a provider-side profile, and not in a store you cannot see. If an agent can use a fact, you can inspect it in Settings.
Access & Isolation
Data Retention & Deletion
We minimize what we keep and make deletion real. Uploaded files are handled on two distinct tracks. Personalization is workspace data you can inspect and delete without deleting your account.
Files attached to a conversation are purged automatically within 10 days, or immediately when you delete the chat.
External cloud files remain on Google infrastructure and are accessed on demand. ARMES does not hold copies unless explicitly imported to your Knowledge Vault. Disconnecting Google Drive immediately deletes all encrypted OAuth tokens.
Files saved to your Notes knowledge base, and the text extracted from them, remain until you delete them or your account.
Stored in your private workspace for as long as you choose.
Visible in the personalization ledger. Deleting a source chat may orphan or purge memories that came from it. Turning the master toggle off stops injection without deleting stored facts.
Rolling summaries of threads, listed in Settings. Deleting an episode removes it from search and from agents.
Numerical search indexes of memories and episodes. Deleted with the memory or episode they belong to. Used only to search your workspace.
Preferred name, role, style, and similar fields you enter. The master toggle can stop agents from using this without wiping the fields.
Discarded by the provider after the response, under zero-data-retention — including extraction, summarization, and embedding calls.
Encrypted point-in-time recovery and daily backups rotate out within 30 days.
Your data (conversations, agents, notes, files, memories, and episodes) is permanently deleted from the active database and object storage. Your profile row is retained briefly as an anonymized tombstone — all personal information is scrubbed — before being purged from backups within 30 days. Full detail is in our Privacy Policy.
Subprocessors
We rely on a small set of established infrastructure providers. Each is bound by contractual data-protection obligations.
Compliance Posture
We aim to be precise about where we stand — including what we are not certified for.
What our infrastructure provides
What ARMES does not currently offer
Incident Response
Breach Notification
In the unlikely event of a data breach affecting your personal data, we will notify affected users and relevant supervisory authorities within 72 hours of becoming aware of the breach, as required by applicable law.
We perform dependency audits and vulnerability scanning, and maintain encrypted backups with automatic rotation and purge schedules.
Report a Vulnerability
We welcome responsible disclosure. If you believe you have found a security vulnerability, please contact our security team. We will acknowledge your report and work with you to understand and resolve the issue.
security@armes.aiSecurity & Compliance Inquiries
Conducting a vendor security review? This page is designed to answer most questions directly. For anything further — including subprocessor attestations — reach out and a real person will respond.
Contact SecurityARMES Labs, Inc.
Delaware, United States