Security
Your environment files stay in your local workspace.
EnvDesk is designed around files already stored on your computer. Values are masked by default, optional workspace passphrases protect access inside the app, and changes are shown for review before EnvDesk writes them back to disk.
What stays local?
Project folders, environment files, keys, and values are handled by the desktop application on your machine. EnvDesk does not require a cloud workspace for environment-file management.
How are accidental changes reduced?
- Sensitive values are masked by default.
- Environment files can be compared by key.
- Writes require a review step before reaching the file on disk.
- A workspace can be protected with a passphrase.
What remains your responsibility?
Local-first does not make plaintext files safe for production. Keep `.env` files out of version control, use operating-system access controls, rotate exposed credentials, and use a dedicated secrets manager where production access control, rotation, sharing, or audit logs are required.
How do I report a security concern?
Email [email protected] with reproduction details and affected versions. Do not include live secrets in the report.