Legal

Data Processing Addendum.

Who is the controller, who is the processor, who else is involved, how it is secured, and how it is deleted: a summary for your privacy and procurement teams.

01

Scope

This is a summary of the data processing terms that apply when Sentinel processes personal data on your behalf.

  • A signed addendum for your own paper is available on request; write to team@gigahertzcompany.com.
02

Roles

  • You are the controller (or a processor acting for your customer) of personal data that appears in the code and data you ask us to scan.
  • Black Llama is the processor of that data. We process it only to run the scans you request, on your documented instructions.
  • For account, billing and security-log data about your users, Black Llama is an independent controller, as described in the Privacy Policy.
03

What we process

  • Source code and archives, read once in a sealed sandbox and deleted at the end of the scan.
  • Findings derived from that code, with secrets cut to a prefix, stored encrypted to your organization’s key.
  • Your users’ names and work email addresses, and audit-log entries about their activity.
04

Subprocessors

We use these to deliver the service. We will notify account owners before adding or replacing one, and you may object on reasonable grounds.

VercelApplication hosting and deliveryServes the website and the web application.
Vercel SandboxScan isolationRuns each scan in a disposable microVM with the network denied.
NeonDatabaseStores findings metadata, sealed blobs, the access ledger and badge records.
ResendTransactional emailDelivers sign-in links, scan results and billing notices to the addresses you give us.
StripePaymentsTakes payment and issues receipts. Card details never reach Sentinel.
GitHubCode source (optional)Only if you connect it: we read the repositories you pick, read-only, for the scan.
05

Security measures

Summarized here; described in full on the Security page.

  • A fresh Firecracker microVM per scan, started on Vercel Sandbox with a deny-all network policy and no persistence.
  • Archive extraction is guarded against zip-slip, symlink escapes, executable bits, runaway file counts, oversize files and compression bombs.
  • Anything derived from your code is encrypted inside the sandbox to your org’s public key.
  • The scan machine and the coordinator hold write access only. The web application is the only part that can read, and only through the vault.
  • Opening a sealed result calls the vault, which writes a signed, tamper-evident ledger entry before decrypting. No log, no decrypt.
  • Your admins and your auditor can see who read what, and when.
  • Source and archive: overwritten and deleted inside the machine at the end of the scan; the upload is destroyed from storage.
  • Findings metadata (rule, file path, line, severity, mapping): kept so your history and your tier stay provable.
06

Personnel and assistance

  • People with access to customer data are bound by confidentiality.
  • We help you answer data-subject requests and regulator inquiries about data we process for you.
  • We tell you without undue delay after we become aware of a personal-data breach affecting your data.
07

Deletion and return

  • Source code: deleted when each scan ends.
  • Results: on request, or when you close your account, we destroy your organization’s encryption key (crypto-shredding), which makes sealed results unreadable. We can export your reports first.
  • Ledger and audit entries are retained, since they record access rather than content. Backups age out on their normal schedule.
08

International transfers

  • Our subprocessors may process data outside your country. Where required, transfers rely on standard contractual clauses or an equivalent mechanism; details in the signed addendum.
09

Audit and contact

  • On request we provide the information needed to show we meet these terms, and reasonable audit questionnaires.
  • Contact: team@gigahertzcompany.com.

Draft v1 — under review by counsel; last updated October 13, 2026