Security

How EnvManager handles your secrets

What we do, what we do not do yet, and who is responsible. Questions about any of it go through our contact page.

Encryption and who can decrypt

Values you mark as secret are encrypted by Supabase Vault before they are written to the database, using authenticated encryption from libsodium. Values you do not mark as secret are stored as plain text in the same database, behind the same access rules.

Access rules live in the database itself, as row-level security: a request only sees data from organisations you belong to and environments you were given access to. Secret values need value access to that environment on top of that.

Secrets are decrypted on our server when someone with access reveals, pulls, runs or syncs them. The dashboard and the CLI record reveals, pulls and runs in the access log, with who and when.

Because decryption happens on the server, we as the operator can technically decrypt your secrets. EnvManager is not zero-knowledge, and we do not claim it is.

All traffic to envmanager.com goes over HTTPS.

Where your data lives

The database, including encrypted secrets, accounts and audit logs, is hosted by Supabase in Frankfurt, Germany, in the EU.

Who runs EnvManager

EnvManager is built and run by DigitX B.V., a company registered in the Netherlands.

Sub-processors

These companies process data on our behalf. We update this page when the list changes.

CompanyWhat it does for us
SupabaseDatabase, encrypted secret storage (Vault) and authentication. Hosted in Frankfurt, Germany.
CloudflareSits in front of envmanager.com and caches the public pages.
StripePayments and invoices. We do not store full card details.
MailgunTransactional email: account confirmations, password resets, security alerts and service notifications.
BrevoNewsletters and other marketing email.
PostHogProduct analytics.
GoogleTag Manager and Google Ads conversion measurement.

PostHog and Google only load after you accept cookies. Where a provider processes data outside the EU, the safeguards are described in our privacy policy.

Data processing agreement

If your company processes personal data through EnvManager and needs a data processing agreement under the GDPR (Article 28), ask for a copy at info@digitx.nl.

Export and deletion

You can export your variables at any time, including during the trial and after it ends. When a trial ends nothing is deleted: you can still sign in, see and export your variables and pull them with the CLI, while changes and syncs pause until someone subscribes.

Secrets stay stored until you delete them or close your account. Our privacy policy sets out how long each kind of data is kept, including backups.

What envmanager run protects against

envmanager run starts a command with only the keys you allow, through --only or the agent.allowed_keys list in envmanager.json. It refuses to start without one of those, or an explicit --all. Secret values are masked in the command's output, so they do not end up in an AI agent's chat transcript or in logs.

It helps with

  • Keys pasted into a chat and kept in the transcript
  • Values printed in logs or error output
  • An agent getting keys it does not need

It does not stop

  • A process reading its own environment and sending a value somewhere
  • A value that is encoded or changed before it is printed
  • Anything holding your CLI login fetching the values another way, for example with envmanager pull
  • Secret values shorter than 6 characters, which are not masked (the CLI warns you)

Certifications

Certifications: none yet.

EnvManager is not SOC 2, ISO 27001 or HIPAA certified. If your company requires one of these, we are not the right fit yet, and we would rather say so here than on a sales call.