Privacy policy
Last updated 12 November 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
- Your account: email address and name.
- Sign-in identities: the Google or GitHub account you sign in with, and the public keys of your passkeys. A passkey's private key and any fingerprint or face data never leave your device.
- Your organisation: its name, members and their roles.
- Cloud inventory metadata: what resources exist in the accounts you connect and how they are configured.
- Findings, and the evidence behind them.
- Billing: your plan, trial dates and payment status. Card details stay with Stripe.
- Delivery settings: your Slack workspace and channels, and briefing recipients.
- An audit log of sign-ins, member actions, model calls, agent calls and deliveries, which you can view.
- If you join the waitlist or use the contact form: your email address and message.
- If you request a human review: your email address, what it is for, and your note, which is emailed to us.
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 Amazon Web Services, in the United States (Oregon). Encrypted nightly database backups are kept there too, 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
- Cloudflare: DNS and traffic proxy for opsagent.dev, and Turnstile, the security check on the sign-up, sign-in, waitlist and contact forms.
- Amazon Web Services: hosting, the database and encrypted nightly backups.
- Stripe: payments, subscriptions and tax, as merchant of record. It receives your email and your organisation's name, and collects your card details.
- Resend: sending sign-in and briefing email.
- Slack: delivering briefings, when you connect it.
- Google and GitHub: signing you in, when you choose them.
- Anthropic: Dashboard AI explanations and chat, only after an owner of your organisation turns Dashboard AI on. OpsAgent sends the details of the findings and resources you ask about. Anthropic does not train on this data.
- OpenAI: the backup model provider for Dashboard AI on OpsAgent's key, used the same way as Anthropic.
- The AI provider you choose, or the endpoint you configure, if you add your own key: OpsAgent sends that provider the context it needs to answer, under your account with them.
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.