Security by design

Hydrofoil reviews real applications without giving an AI unrestricted access to your code, your credentials or your infrastructure.

Access

What Hydrofoil can access on GitHub

Hydrofoil reads your code and writes only comments and checks. It cannot change your code.

PermissionLevelWhy
MetadataReadBasic repository information
ContentsReadRead the diff and repo instructions
Pull requestsRead & writePost the summary and inline review comments
IssuesReadRead linked GitHub issues
ChecksRead & writeReport results as a check
DeploymentsReadFind the preview deployment
Commit statusesReadFind the preview URL when it's reported there
Organisation membersRead(optional)Match PR authors to Hydrofoil users
Encryption

Credentials are encrypted

Test credentials and secrets are encrypted with AES-256-GCM envelope encryption. Each organisation has its own data key, protected by an AWS KMS key. Values are write-only: once saved, they're never shown again. Every create, update, delete and use is recorded in an audit log.

  1. AWS KMS keyProtects each organisation's data key
  2. Organisation data keyOne per organisation
  3. Secret valueEncrypted with AES-256-GCM
  • Write-only
  • Fully audited
  • Per-organisation keys
Secrets

The AI never sees your secrets

When the agent logs in, it uses a reference such as{{persona.admin.password}}. A separate layer swaps in the real value inside the sandbox, so the secret never reaches the AI model.

Network

Network isolation

All browser traffic goes through an egress proxy that only allows the domains you've configured. Internal, loopback and cloud-metadata addresses are blocked, and previews must use HTTPS.

Prompt injection

Text from pull requests, tickets and web pages is treated as untrusted data, never as instructions. The agent has a narrow toolset with no general web-request tool. Navigation is limited to an allowlist, and results are calculated by our code from the findings, not taken from the model's say-so.

  • Untrusted input
  • Narrow toolset
  • Navigation allowlist
  • Code-calculated results

Protecting your test environment

For each repository you can list forbidden actions in plain English and block specific requests. We recommend previews that use seeded or sandbox data.

Redaction

Known secret values are replaced with ••••in logs, step records, transcripts and findings. Password fields stay masked in screenshots. Transcripts are stored redacted.

fill password••••

Tenant isolation

Every query is scoped to your organisation. Screenshots, videos and traces are served only through short-lived signed links after an access check.

Retention and deletion

Artifacts are kept for[TBD: 30 days by default, plan-dependent]. Deleting an organisation purges secrets immediately and removes artifacts on the retention schedule.

Infrastructure

Infrastructure and subprocessors

Hydrofoil runs on AWS ([TBD: region]). Subprocessors: AWS (hosting, storage, email, key management and AI models via Amazon Bedrock), Stripe (payments), GitHub, and Jira if you connect it.

[TBD: AWS statement on how Bedrock handles customer data. Use their documentation's wording.]

  • AWSHosting, storage, email, key management and AI models via Amazon Bedrock
  • StripePayments
  • GitHubPull request integration
  • JiraOnly if you connect it

Compliance

[TBD: certifications held, or "We don't hold any compliance certifications yet."][TBD: security questionnaire available on request]

Report a vulnerability

[TBD: security contact and disclosure policy]