How Signals handles your access

Signals asks for tokens to the services your product runs on. This page explains exactly where they go, who can open them, and what happens when you delete your project.

Encrypted in your browser

When you paste a key, your browser seals it before sending. Each project server has its own key pair; your browser encrypts with that server's public key, so only that server can open it.

  1. Your browser Sealed here Encrypted with your project server's public key before it's sent anywhere.
  2. Signals servers Passed through, never opened Our servers relay the sealed key. They have no way to read it, and it never lands in our logs.
  3. Your project server Opened only here An isolated machine that runs your project and nothing else.
Key agreementECDH P-256, one-time key per seal
Key derivationHKDF-SHA256
EncryptionAES-256-GCM
ImplementationStandard Web Crypto API, no custom cryptography

One project, one isolated server

Every project runs on its own machine. Your code, findings and keys stay on that machine and are never shared with another project. Signals' web servers only see summary numbers, such as how many findings there are and when the last scan ran. They never see what the findings say.

Write access is double-sealed

Keys that can change something, such as a GitHub token that opens pull requests or a database or deployment token, get a second seal held in a key management service. Your project server can't open them alone, and neither can ours.

  1. The agent proposes a fix and asks for your approval.
  2. Your approval releases the outer seal for that one fix.
  3. The project server uses the key, then clears it from memory.

Code changes always arrive as pull requests. You review and merge them.

What we ask for, and why

ConnectionUsed toChanges anything?
GitHubRead your code and repo settings to confirm findingsAfter you approveOpens a fix PR. You merge.
AnthropicRun the agents on your own API accountNo changes
Vercel, SupabaseRead deployment, database and DNS security settingsAfter you approveOnly the change you approved.
AWSRead security groups, instance and storage settingsNo changesThe IAM policy we give you is read-only.

We keep adding services you can connect. Each new one will be listed here with what it reads and what it can change.

Delete your project and nothing is left

Revoke any token at its source and Signals stops using it. Delete a project and its server is deleted with it, along with its keys, code copy and findings.

Found a vulnerability?

We'd like to hear from you first. Write to support@signalsagent.app.