Privacy policy

Last updated 28 October 2026

OpsAgent is run by Binary Labs LLC. This page says what we store when you use it, why, and what you can ask us to do with it. For anything here, use the contact form.

What we store

OpsAgent connects through a read-only role you create. It cannot read your stored data (objects, database rows, secret values). The few scoped reads it can make are listed on the security page.

Why

To run the service: sign you in, check your cloud, write your briefings and deliver them. We never sell your data, and we don't use it for advertising.

Where it lives and how long

Data is stored on Railway, in the United States. Encrypted nightly database backups are kept on Amazon Web Services, in a storage bucket Binary Labs controls. Secrets such as Slack tokens are encrypted with a per-organisation key.

Evidence excerpts are stripped of secret-shaped strings and common personal data before they are stored. Evidence and inventory snapshots expire after 90 days. Findings are kept while your organisation exists.

Who else processes it

Cookies

OpsAgent uses only first-party cookies needed to sign you in and to approve agent connections. No advertising or tracking cookies. Your browser also remembers, in its local storage, if you dismissed the passkey suggestion.

Your choices

Ask through the contact form and we will delete your account and your organisation's data within 30 days. We keep a record that the deletion happened, containing no customer data, for one year. You can also ask for an export of your organisation's data as JSON, delivered within 30 days. Disconnecting a cloud account stops OpsAgent using its role at once.

If an incident on our side affects your data, we tell you within 72 hours of confirming it.

Changes

When this policy changes we update this page and the date at the top.