Armore
Security · last reviewed 14 Oct 2026

What we hold,
and what we do not.

Armore holds no security certification. Studio, our cloud workflow product, has been retired — if you connected an account to it, the one action entirely in your hands is below. An earlier version of this page overstated Studio’s controls.

If you used Armore Studio

Retiring a product does not revoke your tokens

Studio connected to Google (Gmail, Drive, Docs, Sheets, Forms, Meet), Slack, Notion and WhatsApp using OAuth. Taking the product’s pages down is not the same as revoking those grants, and we are not going to let the two be confused.

The action that is entirely in your hands: revoke Armore’s access from the provider’s own security settings — Google Account → Security → Third-party access, and the equivalent page in Slack or Notion. A revocation made at the provider cannot be undone by anything on our side, which is exactly why it is the one we are recommending. For anything else, including deletion of stored data, email security@armore.ai.
Edge and Sovereign

The posture on the products we are still building

Edge keeps the work local

Reasoning happens on your own hardware, so the content of what you ask is not sent to a cloud to be answered. Device sync can route through a relay that cannot read the traffic, but can see which devices are talking, when, and how much.

Signed builds, named accurately

Edge v1.0.10 publishes 94 files on the public mirror — the 47 payload files among them each carrying their own Sigstore attestation of how and where it was built, 1:1. Each is a signature over that payload’s digest, bound by certificate to the repository, workflow and commit that built it, and recorded in a public transparency log. That is not SLSA build provenance and not an OS-trusted signature — the Windows and Linux builds are not code-signed.

Sovereign stays in your perimeter

Our enterprise line, coming soon as a custom implementation on hardware the customer controls. It holds no certification, and no benchmark has been run for it.

Compliance

No certification is held

We are doing SOC 2 readiness work, scoped to the cloud tier we intend to offer. No auditor is engaged, no observation window has opened, and no report exists — readiness work is not an audit and discharges none of your obligations. We hold no compliance certification or attestation in any industry we build for. Sovereign is built for customers in regulated industries, and we claim no compliance posture in any of them — any assessment in your industry remains yours. We publish no uptime figure and offer no SLA, because availability has never been measured. Our one performance figure is Edge’s ~99.5% context reduction on extraction and lookup, 98% accurate against a no-document control; on yes/no judgement it scores 54% against 42%, which is noise. No benchmark has been run for Sovereign.

Reporting a vulnerability

Tell us and we will answer

Email security@armore.ai with details and reproduction steps. We acknowledge reports and will keep you updated through resolution. Please give us a chance to fix an issue before disclosing it publicly.

entityArmore Private Limited, Om Chambers, 1st Main Road, Indiranagar 1st Stage, Bengaluru 560038, India
CINU62013KA2026PTC229797
contactsecurity@armore.ai