Here's exactly how we handle your stuff
No compliance theater. Just a clear explanation of what runs where, what we store, and how it's protected.
Your code runs in isolated containers
Preview environments spin up as isolated Docker containers on dedicated worker servers. Each container runs your code and only your code. When the PR closes, the container is torn down completely.
We never cache your source code. We never inspect it. The workers exist solely to run Docker instances — they're not part of FlightDesk's application infrastructure.
What we store vs. what we don't
We store
- Task metadata (titles, descriptions, status)
- Timeline events (status changes, PR links)
- Check results (pass/fail, issue counts)
- Context notes you save (test plans, summaries)
We don't store
- Your source code
- Your environment variables (passed to containers, not stored)
- Git history or diffs
- Claude Code session contents
GitHub tokens are short-lived
We use GitHub App installation tokens, not personal access tokens (PATs). These tokens are automatically issued by GitHub, last about an hour, and auto-refresh when needed.
You never have to create, paste, or rotate a PAT. The GitHub App only requests the permissions it needs (repo contents, pull requests, issues) — no admin access, no org management.
Integration credentials are encrypted
When you connect integrations like SonarQube, those API tokens are encrypted at rest using AES-256. The encryption key lives in the environment, not in the database.
Tokens are only decrypted when making API calls to those services on your behalf.
SSH access uses your public key
When you SSH into a preview environment, authentication happens via the public key you've added to your FlightDesk account. No shared passwords, no credentials to manage.
Preview containers run as non-root users with limited capabilities. They can run your app, but they can't escape the container or access other users' environments.
HTTPS everywhere
All traffic to FlightDesk and preview environments is encrypted in transit via TLS. Preview URLs get auto-provisioned certificates. No HTTP fallback.
What we don't have (yet)
We're a small team building fast. Here's what's not in place:
- SOC 2 certification — we don't have it
- Bring-your-own-cloud — preview environments run on our infrastructure for now
- On-premise deployment — not available
If you have specific security requirements we don't meet yet, let us know. We're happy to discuss what we can accommodate.
Questions about security?
We're happy to answer specific questions about how we handle your data.