Security

Security.

Orchid is local-first by design. Your data and credentials stay on your machine unless you explicitly choose to share them.

Credentials

Database credentials are stored in your operating system's keychain (Keychain on macOS, Secret Service on Linux). They're scoped per project and never leave your machine — not to us, not to model providers, not to collaborators.

When you collaborate on a published project, each collaborator supplies their own credentials locally. The project file only references the profile by name.

Connections

• Read-only by default. New connections start with read-only access. Granting write access requires a confirmation step and shows a lock icon on every cell using that connection.
• Per-connection IP allowlists. Use your warehouse's native allowlist; Orchid runs locally so your machine's IP is the one that connects.
• SSH tunnels & SSL. Both supported per-connection.

Published views

Published notebooks and dashboards are static snapshots — they don't hold credentials and they don't re-run on the viewer's machine. Viewers see the same outputs you saw when you hit Publish.

Agent safety

• Every agent action is logged with inputs and outputs.
• Write operations (INSERT, UPDATE, DELETE, DROP) pause for explicit user approval.
• Agent prompts run under zero-retention agreements with the model providers we use.

Account & auth

Authentication is handled by Supabase Auth. We support email + magic link, Google, and GitHub. Tokens are short-lived; sessions can be revoked from your account settings.

Reporting a vulnerability

Email security@orchidide.com with details and steps to reproduce. We respond within 48 hours and publish fixes with credit.