Data location and subprocessors
This page describes the service that Affectra hosts for you. Your own exports, and what your own tools and AI assistants do with your data, are under your control. See Organizations and data isolation for how your data is kept apart from other organizations’ data.
Where your data is
Section titled “Where your data is”The hosted service runs on Amazon Web Services (AWS) in the region Europe (Frankfurt), eu-central-1. Your data is stored there and processed there.
| What | Where it is kept |
|---|---|
| Your organization, members, products, variants, releases, components, findings, VEX statements, units and their packages, API keys, trusted publishers and package mappings | A PostgreSQL database (Amazon RDS) in eu-central-1. It is encrypted at rest, and accepts only encrypted connections. Its backups are in the same region: seven days of automated backups, and a daily backup kept for 35 days. |
| The SBOM files you upload, and their signatures and attestations | Object storage (Amazon S3) in eu-central-1. It is encrypted at rest, and has no public access. A file that is deleted or replaced is kept as an old version for 30 days, so that a mistake can be undone, and then removed. In the browser, you download files through links that expire about a minute after they are issued. |
| Sign-in accounts: email address, name, password and second factors | Affectra’s own sign-in service, which runs with the rest of the service in eu-central-1 and keeps its data in a database of its own on the same database server. No outside identity provider is involved. |
| Emails that the sign-in service sends, such as the invitation to set up your account and password resets | Sent through Amazon Simple Email Service (SES) in eu-central-1. |
| Finding emails you turned on: release names, vulnerability IDs, severities and links | Sent through Amazon SES in eu-central-1, to your account’s address. Your choices are in the database above. SES keeps a list of addresses that bounced or complained, which Affectra reads to stop sending to them. |
| The daily digest of agent proposals you turned on: the organization’s name, the kind of each pending proposal, its vulnerability ID, the agent’s name and links; no evidence, explanation or proposed text | Sent through Amazon SES in eu-central-1, to your account’s address. Your choice and the time of your last digest are in the database above. |
| Webhook events: release names, vulnerability IDs, severities and links | Sent from eu-central-1 straight to the URLs your admins add, wherever those hosts are. The URLs, signing secrets and extra header values are encrypted in the database above; the delivery log keeps no URL. |
API keys are kept as a hash. Affectra shows a key once, when it is created, and cannot show it again.
The only AWS resource that Affectra runs outside eu-central-1 is the key that signs Affectra’s DNS records (DNSSEC), because AWS requires that key in us-east-1. It holds no customer data.
Subprocessors
Section titled “Subprocessors”A subprocessor is another company that processes your data for Affectra.
| Company | What it does for Affectra | Your data it processes | Where |
|---|---|---|---|
| Amazon Web Services | Hosting: servers, database, object storage, email | Everything in the table above | Europe (Frankfurt), eu-central-1 |
What Affectra contacts on your behalf
Section titled “What Affectra contacts on your behalf”Affectra contacts a few other services in the course of its work. None of them receives your component lists, findings or VEX statements.
- Vulnerability sources. Affectra downloads whole public data sets and matches them inside Affectra. It never asks a source about a particular package, so no source learns what is in your products. Vulnerability sources lists each one.
- GitHub. When an admin adds a trusted publisher, Affectra asks GitHub’s API for the ID of that public repository. To check the token of a GitHub Actions upload, Affectra uses GitHub’s public signing keys. Neither sends your data to GitHub.
- Sigstore. To check signed SBOMs, Affectra downloads Sigstore’s public list of trusted keys. The signature itself is checked inside Affectra, and nothing about your upload is sent to Sigstore.
- No AI service of its own. Your AI assistant works with Affectra over MCP: it reads what its credentials may read and proposes, and a member decides. Affectra itself calls no AI model and sends no data of yours to one. See Connect an AI assistant.
Who at Affectra can see your data
Section titled “Who at Affectra can see your data”Affectra staff cannot read your products, SBOMs, units, findings or VEX statements. See Staff cannot read your data.