How CVD Portal handles your data
Written for the procurement, legal, and security reviewers who diligence us. No marketing language; only what we can evidence. Updated 12 November 2026.

Hetzner, Germany.
Customer data is stored in Germany. Application, database, and backups run on Hetzner infrastructure there. Optional AI features run on Google Vertex AI and Amazon Bedrock in EU regions. The in-app support assistant first sends messages to Anthropic in the United States. The subprocessor list below gives each region. Operational timestamps are Europe/Amsterdam.
Processor.
Tenants are the data controller for submissions their portal receives. We act as a processor under GDPR Art. 28 terms described in our Privacy Policy.
Policy at /security, machine-readable at /.well-known/security.txt.
Public Registries & Official Designations
Independent verification records and regulatory authority listings for CVD Portal:
Cloud Security Alliance (CSA) STAR Level 1
Public self-assessment against the Cloud Controls Matrix. Covers all 17 security control domains.
GCVE Numbering Authority (GNA 126)
Officially recognized GCVE Numbering Authority under the European decentralized CVE allocation initiative. Authorizes identifier allocation and coordinated disclosure records.
Subprocessors
These are the third parties that process tenant data on our behalf. We will give tenants 30 days' notice before adding a new subprocessor with material access to submission data.
Subscription billing and checkout
- Data processed
- Company billing contact, invoice history, card fingerprints (card data itself never touches our servers)
- Region
- Ireland (EU); payment data processed under Stripe's EEA data residency posture
Transactional email delivery (acknowledgments, notifications, auth)
- Data processed
- Recipient email, subject line, message body, delivery metadata
- Region
- Delivery infrastructure with EU sending region available; see Resend DPA
Hosting infrastructure (compute, database, object storage, backups)
- Data processed
- All platform data at rest, including tenant and submission data
- Region
- Germany (compute, database, object storage and backups)
DNS, CDN, TLS termination, and DDoS protection in front of all traffic
- Data processed
- Request metadata and content in transit (proxied, not stored)
- Region
- Global edge network; EU Data Localization options; SCCs under Cloudflare DPA
Product analytics on the marketing site and dashboard
- Data processed
- Pseudonymous usage events, page views, device metadata. No submission content.
- Region
- EU instance (eu.i.posthog.com), data stored in the EU
Optional AI features: AI triage on Enterprise, CRA document drafting and analysis, tabletop exercises, and the web search in the exposure scanner
- Data processed
- Submission text and CRA product documents, sent only when a tenant uses an AI feature. For the scanner web search, the domain name only.
- Region
- EU multi-region. The application refuses any Vertex AI location outside the EU.
Optional AI features: shorter CRA drafting tasks, and the second route of the in-app support assistant
- Data processed
- CRA product documents, assessment content and support messages in the AI request
- Region
- EU. Requests start in Frankfurt (eu-central-1) and use EU inference profiles only.
In-app support assistant (first route)
- Data processed
- Messages a user types into the support assistant, and product details the user asks it to read
- Region
- United States; SCCs. If this route fails, the request goes to Amazon Bedrock in the EU.
Email intake, only for tenants that turn it on: receives and stores messages forwarded to the tenant's private intake address
- Data processed
- The forwarded messages: sender, recipients, subject, body and attachments
- Region
- Germany (eu-central-1, Frankfurt)
AI usage logs for cost and reliability monitoring
- Data processed
- Per-request metadata (company ID, model, token counts, cost, outcome). No prompt or response text.
- Region
- Germany (eu-central-1, Frankfurt)
Internal operational alerts to on-call staff
- Data processed
- System health events and truncated error strings. No submission content, no tenant personal data by design.
- Region
- Global; used for operational telemetry only
Hosting
Application
Runs on servers that we operate in Germany. Administrator access goes through a private network only.
Database
Runs in Germany. Report content, researcher contact details and stored credentials are encrypted at the application layer. Records created before 6 September 2026 were migrated, so older reports are covered too. Reviewers can ask for the exact field list and our key management position.
Network
Every public endpoint uses TLS, with HSTS and the standard browser security headers.
Security controls
Encryption
- ·TLS on every public endpoint, with HSTS.
- ·Report content, researcher contact details, stored integration credentials and two-factor secrets are encrypted at the application layer. This protects against a direct database read. Reviewers can ask for our key management position.
- ·Passwords and API keys are stored only as one-way hashes.
- ·A tenant can publish an OpenPGP key in its security.txt, which lets a researcher encrypt a report before pasting it into the form. The portal does not perform that encryption. A researcher can also supply their own public key so the tenant can reply encrypted.
- ·Backup archives are encrypted before leaving the host, with the decryption key held offline.
Access control
- ·Role-based access in every workspace.
- ·Each customer's data is isolated from every other customer.
- ·Enterprise plan: SSO/SAML and EUDI Wallet identity verification (eIDAS 2.0).
Auditability
- ·Every change writes an append-only audit log entry with the person, the time, the IP address and the country.
- ·Audit entries are hash-chained, and a daily job checks each chain for breaks.
- ·Audit entries cannot be changed or deleted, except by a controlled retention job for operational entries.
- ·CRA Article 14 evidence entries (classification, notification, and remediation decisions) are kept permanently, and survive account deletion in pseudonymised form.
- ·Audit logs surface in the tenant dashboard and are exportable for CRA defense.
Operational security
- ·Secrets are never stored in source code.
- ·Dependencies and code are scanned on each change, and updates are automated.
- ·Production access goes through a private network only, with least-privilege deploy accounts.
Data ownership and exit
- ·You own every report your portal receives. We process it on your behalf, we do not sell it, and we do not use it to train models.
- ·Full export of all the data you provide, in HTML, CSV, and JSON, is available on every plan, including Free, for as long as your account exists.
- ·We delete your data on request. Closing your account removes your data within 30 days, except where a legal retention obligation applies. If a trial or subscription ends and the account stays inactive, we may delete it after a 90-day grace period and at least 30 days' prior notice.
- ·Operational audit entries are retained for 12 months. CRA Article 14 evidence entries are retained permanently and, on account deletion, are archived in pseudonymised form so your compliance record survives the erasure of personal data.
Data Processing Agreement
Our standard Data Processing Agreement (GDPR Art. 28) is published at /dpa, including processing details and the subprocessor list above as its annexes. For a countersigned copy or bespoke terms, email security@cvdportal.com.
Security testing
CVD Portal is penetration tested by an independent firm every quarter. The most recent test was completed in May 2026. Enterprise clients receive the full report under NDA. A summary of scope and outcome is available on request via security@cvdportal.com.
Report a vulnerability in CVD Portal itself
We run our own coordinated disclosure process. Report a security issue in CVD Portal through our disclosure policy, or read the machine-readable security.txt.
Incident response
- 01We learn of an incident via internal monitoring, tenant report, or researcher report to security@cvdportal.com.
- 02A responder acknowledges within the SLA on our Security page, scopes impact, and opens an incident record.
- 03Affected tenants are notified without undue delay (and within 72 hours for personal-data breaches, per GDPR Art. 33).
- 04A post-incident write-up is published to affected tenants. Material incidents are disclosed on /status with a resolution note.
Backups & business continuity
Database backups are taken on a defined schedule and stored encrypted off the primary host. We exercise restore drills periodically. Enterprise customers can request our current RPO/RTO targets, the most recent restore test date, and our business-continuity summary under NDA via security@cvdportal.com. We are deliberately not publishing specific numbers here that we cannot continuously evidence.
On the roadmap
Items we have committed to and are tracking publicly:
- →Disk-level (LUKS) volume encryption for the database and backup storage.
- →SOC 2 Type 1 readiness engagement.