Last updated: April 12, 2026
At ShipDock, we treat your servers exactly as we treat our own. Security is baked into the foundation of the builder engine.
All database records containing SSH keys, server passwords, and environment configuration variables are heavily encrypted at rest natively. We utilize AES-256-GCM authenticated encryption.
We explicitly never pipe environment variables through standard SSH shell commands (e.g., echo ENV=val). Instead, our engine initiates an isolated SFTP session to drop a secure `.env` file directly into the Docker context, preventing rogue shell interpolation and command injection attacks entirely.
If you believe you have found a vulnerability within our deployment agent or control plane, please contact security@shipdock.example.com. We operate a private bug bounty program.