AnnexProof
How we protect your data and evidence
Primary application data at rest is stored in EU regions, mainly Frankfurt. Each organisation has its own isolated workspace, and signing in requires a second factor. This page describes only what runs in the app today.
Data in the EU, in Frankfurt
The app runs in Vercel’s fra1 region, the database in Supabase’s eu-central-1 region, and the Evidence Vault and the audit log anchors in AWS eu-central-1. All three regions are in Frankfurt. Vercel may also process traffic, short-lived logs and metadata outside the EEA. The sub-processor list names the entities and transfer safeguards.
Vercel fra1 · Supabase eu-central-1 · AWS eu-central-1
Tenant isolation
Each organisation works in its own workspace. Tables in the database have row-level security (RLS) enabled and forced. Some reads are made by the app server with a separate database role that bypasses RLS and scopes the data to the workspace itself. The browser never connects to the database directly, only through the app server.
forced RLS
Mandatory multi-factor authentication
A second factor (an authenticator app with one-time codes, TOTP) is required for every user. Both the app and the database check it, so without it no workspace data is visible. Recovery codes work only once.
MFA · AAL2
Audit log anchored in WORM storage
Decisions, approvals and changes in a workspace go into a log whose entries are linked by a hash chain, so an entry cannot be changed or removed unnoticed. Every hour a signed checkpoint of the chain is written to an AWS S3 bucket with write protection (Object Lock in COMPLIANCE mode) for 10 years. You can export the log as CSV.
hash chain · S3 Object Lock COMPLIANCE
Evidence Vault
Evidence files go into an AWS S3 bucket with Object Lock, encrypted with AWS KMS keys. Every uploaded file is scanned for malware (Amazon GuardDuty) and the result is recorded with the file. Files are always downloaded as attachments.
S3 Object Lock · KMS · GuardDuty
Encryption
Connections use TLS 1.2 or 1.3 only, with HSTS. Data at rest is encrypted: files in S3 with KMS keys, and the database by its provider.
Backups
Daily database backups.
Vulnerability disclosure
We take reports of vulnerabilities in AnnexProof at security@annexproof.com and acknowledge them within 3 business days. The policy is below, and the address is also in our security.txt.
Documents for procurement and security reviews
- Data processing agreement (DPA)The draft data processing agreement under Article 28 GDPR is under legal review and is not yet ready for signature. We send the current draft on request.Request the draft DPA
- Sub-processorsWho processes data for AnnexProof, for what purpose and where.List of sub-processors
- Security questionnaireHave your own vendor questionnaire? Send it and we will fill it in.Send a questionnaire
Vulnerability disclosure policy (CVD)
Vulnerability disclosure policy (CVD)
If you find a vulnerability in AnnexProof, please tell us. This is how we handle vulnerabilities in our own product, in line with the good practice the Cyber Resilience Act expects from manufacturers.
1. Scope
- annexproof.com (this website),
- app.annexproof.com (the app),
- the AnnexProof API (app.annexproof.com/api/v1),
- the AnnexProof CLI and the AnnexProof GitHub Action, in all supported versions,
- the AnnexProof service.
2. How to report
Write to security@annexproof.com, in English or Polish. These help us most:
- the affected URL or component;
- steps to reproduce the issue;
- the impact: what an attacker could do with it;
- your contact details, and whether you would like to be credited by name.
The same address is in /.well-known/security.txt.
3. What we do after you report
- We acknowledge your report within 3 business days.
- We triage the issue and update you on progress at least every 14 days.
- We agree disclosure with you. By default we publish details 90 days after the report, or earlier once a fix is deployed.
- With your consent, we credit you as the person who reported the issue.
- We do not run a bug bounty programme and do not pay rewards for reports.
4. Good-faith research
We will not take legal action against people who look for vulnerabilities in good faith and follow this policy. Good faith here means you do not harm our users, you do not disrupt the service, and you give us time to fix the issue before you describe it publicly. This commitment is ours; we cannot speak for other companies or authorities.
5. Out of scope
- Denial of service (DoS) and volumetric or load testing.
- Social engineering and phishing, against us or our customers.
- Physical attacks.
- Spam, and automated scanner output without a demonstrated impact.
- Accessing or changing other people's data beyond what is needed to demonstrate the issue. If you come across someone else's data, stop and report it to us.
6. Vulnerabilities in our customers' products
This channel is for AnnexProof itself. To report a vulnerability in another manufacturer's product, including one of our customers, contact that manufacturer directly: through its PSIRT page, its CVD policy or its security.txt file. You can look these up with the CRA Snapshot.