Privacy notes

Privacy notes

Heads up: plain-English explainer, not a legal document. Describes how Aarmos works today. Last updated November 5, 2026. For the binding agreement, see the Terms of Service.

The short version

Aarmos is local-first. API keys, OAuth tokens, chat history, agents, connector configuration, and the local audit ledger are stored on the device unless a separately described feature sends specific data elsewhere. By default, agent content stays on your device. Customer-configured providers and connectors may receive data as described below. Customer-operated evidence forwarding can send evidence to a destination you choose when you enable it. An opt-in Aarmos-hosted workspace evidence relay is designed for Team and Enterprise, but is not currently enabled; Aarmos does not currently store customer governance evidence through the held workspace relay. Every server-side surface — narrow proxies for services that block CORS, account and entitlement records, team pointers, and entitlement checks — is listed under When Aarmos's server touches traffic.

What's saved on this device

  • LLM API keys added to the on-device vault.
  • OAuth access + refresh tokens for connected services.
  • Custom REST API configs, MCP server URLs, and agent definitions.
  • Chat history, tool-permission rules, and consent decisions.
  • Signed audit ledger entries and cost / token telemetry.
  • If you set a device password, a PBKDF2 verifier — never the password itself.

Anyone with access to this browser profile — including extensions — can read unlocked vault contents. Set a device password, enable auto-lock, and treat the profile as sensitive.

What the hosting company can see

The static hosting that serves the app may log basic request info (like your IP and timestamps) to keep the site up and prevent abuse. There are no ads and no session recording.

When you talk to other services

When the model runs a tool or answers a prompt, your browser connects directly to:

  • Your LLM provider — OpenAI, Anthropic, Google, Azure OpenAI, Groq, Mistral, or your local Ollama / LM Studio runtime — using your own API key. Their terms and privacy policies apply to the prompt and any tool arguments the model sends.
  • Connectors and MCP servers you configured — GitHub, Slack, Notion, Google, Linear, custom REST APIs — using the OAuth tokens or keys in your on-device vault.

For services that support direct browser requests, traffic goes from the browser to that service. A narrowly scoped Aarmos-hosted compatibility relay is designed for services that cannot be reached directly, but is not currently enabled; customer-operated forwarding remains available and customer-controlled. Review each provider's own privacy documentation before sending sensitive data.

AI Assist

  • AI Assist runs only when you invoke it. Nothing is sent otherwise.
  • You choose the provider and model. Aarmos does not supply, host, select or fall back to any model.
  • When invoked, Aarmos sends the drafting request and a minimised context to that provider and model only.
  • Credentials, Evidence and unrelated policy values are not sent.
  • The request may be kept with the resulting draft.
  • Normal invocation logs keep metadata, not the raw request.
  • AI output is an ordinary draft. It needs the same preview, independent review and activation as any other change, and AI Assist cannot preview, review or activate anything itself.
  • Aarmos works fully without AI Assist.

Your provider's own terms and privacy policy apply to what it receives. This disclosure describes product behaviour; it adds no privacy commitment beyond it. How AI Assist works.

Account and evaluation applications

Hosted account and application records include your sign-in email, request status and review timestamps. Organization applications include the organization name, optional applicant role, intended use and optional note. Founder-invited engineers may use a personal email address and supply an optional invitation note. We store additional-information questions, the current applicant note or reply, and review decisions, reasons and applicable access records. Applicant replies update the current note rather than creating a guaranteed transcript of every previous note. Review and security audit records are retained separately. These records support manual review, correspondence, access administration and audit accountability. Do not include credentials or confidential customer datasets in an application.

When Aarmos's server touches traffic

Governance is local-first. Hosted services handle account and entitlement records, team membership and administration, static delivery, and optional telemetry. A narrowly scoped hosted compatibility relay and an opt-in Aarmos-hosted workspace evidence relay are designed but not currently enabled; customer-operated evidence forwarding to a destination you choose remains available. Policy evaluation, receipt signing, and key custody do not require an Aarmos-hosted service.

  1. Compatibility relays (designed, not currently enabled) — would narrowly forward requests for configured services that cannot be reached directly from the browser. They are not evidence stores.
  2. Authorization exchanges — complete selected provider authorization flows where direct browser exchange is not available. Resulting credentials are stored on the device.
  3. Connector authorization — handles the minimum exchange required for supported connectors. The provider remains responsible for its own data handling.
  4. Discovery — fetches public service metadata for an address the user supplies.
  5. Purchase records — Self-service checkout is not currently active. Existing purchase records, where present, include subscription and price identifiers, status and billing period used to administer prior purchases and applicable obligations. Information required for a future private commercial arrangement will be described before commitment in its applicable disclosures.
  6. Team pointers (Team/Enterprise only) — team identity, membership references, and the location and public verification material for a customer-controlled policy bundle. Bundle content remains in customer-controlled storage.
  7. Entitlement verification — confirms current access to approved product surfaces. It carries commercial state, not agent content, policy content, or evidence.
  8. Command-line telemetry (opt-in) — sends coarse product events and environment categories, not receipts, policies, prompts, tool results, file paths, or hostnames. It can be disabled from the command-line settings.
  9. Workspace evidence relay (Team/Enterprise, opt-in; designed, not currently enabled) — the relay is designed to transport governance evidence without participating in policy evaluation or authorization. If enabled in future, evidence your device signs would be copied to your workspace so teammates, exports, and compliance reviews can reach it. Two evidence classes would be held with distinct access and retention handling:
    • Receipt evidence — signed lifecycle records and declared extensions, accepted under a bounded evidence contract and scoped to the customer workspace.
    • Policy evidence — can be protected separately from receipts. Custody and storage responsibility depend on the selected deployment mode.
    The relay would preserve the signed evidence bytes it accepts. Retention would follow the workspace policy and applicable plan; responsibility for storage operation would depend on whether the relay is Aarmos-hosted, uses customer-controlled storage, or is customer-operated. Policy evaluation, receipt signing, and local evidence production do not depend on relay availability. This designed capability does not change the currently enabled customer-operated evidence-forwarding path. See Terms §16 for the designed retention and export model.

Whether a configured external service is reached directly or through a compatibility relay depends on that service and the chosen connection method. Review the connection details before sending sensitive data.

Analytics (off by default, opt-in only)

Aarmos does not load any analytics, tracking pixels, or third-party scripts unless you explicitly turn analytics on in Settings → Appearance & consent. No cookies are set for analytics. If you opt in, anonymous product events (screens, features, errors) are sent to PostHog EU with IP dropped server-side and Do-Not-Track respected — no message content, credentials, tokens, names, or emails. A random anonymous ID lives in local storage; no cross-site tracking. You can withdraw at any time from the same setting or the Analytics chip in the page footer.

Activity, runs & observability

A local ledger records agent runs and tool calls — model, tokens, estimated cost, errors — so operators can reconstruct what happened. Evaluation and above signs entries with a per-device key and hash-chains them so tampering is detectable. Tokens, emails, and common PII patterns are redacted before write.

Analytical views built on top of that ledger — including the operational readings under Operations — are computed on your device from the same local records. They do not add a separate hosted collection path; any enabled telemetry and evidence services remain governed by the disclosures above.

Retention & auto-purge

Aarmos prunes local data on a schedule you control from Storage:

  • Usage, cost, run history, and local audit data use configurable retention windows.
  • Chats, agents, connections, and keys — until you delete them.
  • Current operational constraints and retention options are listed in Docs → Operational Limits.

These are on-device retention windows. If the workspace evidence relay is enabled in future, server-side retention would be separate and would follow your workspace retention policy — see Terms §16 and the Limits page. Today, evidence remains on your device or in storage you control.

Shorten, extend, export, or wipe on demand. You'll get a warning at 80% storage capacity before writes start failing.

Team+ evidence forwarding (optional, off by default)

Team and Enterprise admins can enable Bring Your Own Bucket — signed ledger entries stream as NDJSON to your S3, GCS, R2, or compatible bucket via a pre-signed URL. Aarmos never holds long-lived storage credentials; nothing forwards until enabled on the device.

Admins can also configure an evidence destination — Splunk HEC, Datadog Logs, or an HMAC-signed webhook — so workspace audit events are forwarded outbound as they are written. Team includes one destination; Enterprise removes the cap. Only the audit event envelope is forwarded (actor, action, resource, timestamp, chain position, and metadata capped at 512 bytes) — never chat, tool results, keys, or tokens. The delivery credential is stored as an environment-variable name; the secret value lives in your secrets manager, not in the database.

Who controls your data & who we share it with

Aarmatix LLC (a Delaware limited liability company) is the data controller for the limited personal data described on this page — primarily your account email, evaluation application and review information, entitlement records, and, if you opt in, anonymous product analytics. You can reach us at support@aarmatix.com.

We share personal data only with the following categories of recipients, each acting as a processor or independent controller for a narrow purpose:

  • Paddle.com Market Ltd — Merchant of Record for purchases processed through Paddle; self-service checkout is currently disabled. Paddle collects billing details, processes payments, calculates and remits sales tax/VAT, issues invoices, and handles refund and chargeback requests. See the Paddle Privacy Notice.
  • Static hosting & CDN providers — serve the app and may log basic request metadata (IP, timestamp) for uptime and abuse prevention.
  • PostHog EU — only if you opt in to analytics; IP is dropped server-side.
  • Authorities or professional advisers — where required by law.

Cookies

No ads or cross-site tracking cookies. Local storage and IndexedDB remember settings, chats, run history, and consent choices — for the app to work.

Age

Built for adults using Aarmos in a professional capacity. Not designed for children or use below the age of digital consent in your jurisdiction.

Regulated data

No compliance claims (HIPAA, PCI DSS, GDPR-specific processing). Don't route medical records, cardholder data, or other regulated categories through Aarmos unless your provider, MCP servers, and APIs are individually approved and your organization accepts the flow.

Your controls

  • Remove any LLM API key from Settings → AI providers.
  • Revoke OAuth connectors and MCP servers; tokens are wiped from the vault.
  • Set a device password and auto-lock for shared machines.
  • Export an encrypted backup and restore on another device.
  • Use Reset app data in Settings → Storage to wipe the profile.

Security

The optional device password derives an AES-GCM key via PBKDF2-SHA256 (WebCrypto) that wraps the vault at rest. No browser vault defeats a compromised browser, extension, or device malware — use a strong password, store the recovery code in a password manager or HSM, and keep browser + OS patched.

Changes to these notes

We may update this page as Aarmos evolves. The date in the banner at the top shows when it last changed.

Last updated: November 5, 2026. Aarmos is a product of Aarmatix LLC. Evaluations are selective; scope, duration and any commercial terms are arranged directly. Contact: support@aarmatix.com.

How-tos · Terms · Trust