Dazr Compliance trust centre
Last updated 20 October 2026
If a translation of this page differs from the English version, the English version applies.
Where your data is stored
All application data, files and backups are stored on servers in the European Union, and every sub-processor below processes them there. The data processing agreement sets out how they are protected.
Sub-processors
The sub-processors of Dazr Compliance are listed by name in the sub-processor list, with the server region we use for each. We give 30 days’ notice before one is added or changed.
| Provider | Location | Purpose | Data |
|---|---|---|---|
| Vercel (EU cloud infrastructure) | EU | Compute and edge functions that run the portal and the API, and page statistics without cookies | Workspace content (records encrypted at the application layer), member identities and billing status |
| Upstash (key-value storage) | EU | The key-value database of the portal, and short-lived counters that limit requests to public endpoints and sign-in | Workspace records (encrypted at the application layer), IP addresses, email addresses and counter values |
| Hetzner Online (our own servers) | EU (Germany, Nuremberg) | Storage of uploaded files and backups, and our own mail server, which sends sign-in codes, invitations and notifications | Uploaded files and backups, encrypted at the application layer; emails while they are sent |
| Mollie (payment processor) | EU (Netherlands) | Card payments and recurring billing for paid plans | Billing contact, VAT number, invoice address and payment status; card data never reaches our servers |
| Namecheap Private Email (support mailbox) | EU | Support email and Enterprise enquiries | What the sender writes, kept for 24 months after the last activity |
How we protect your data
- Encryption at rest. Workspace records (controls, risks, incidents, intake reports, the activity log, member and profile data and the other registers) are encrypted with AES-256-GCM at the application layer, on top of the hosting provider’s own encryption, with keys derived from a master key that is kept as a server secret, separate from the data, and can be rotated without downtime. Uploaded files (evidence, policy and profile documents, breach-report attachments) are encrypted at rest by the storage provider, stored under unguessable addresses and served only after an access check; SBOM files in the Cyber Resilience Act module are also encrypted by the application.
- Encryption in transit. All traffic is encrypted with HTTPS. Browsers are told to use only HTTPS for dazr.eu and all its subdomains (HSTS, with the preload directive).
- Sign-in. With Google, Microsoft or a one-time code sent to your work email, on every plan; Dazr stores no passwords. “Sign out everywhere” ends every session of an account.
- Access checks and roles. Every request is checked against current membership and scoped to your workspace, so a removed member loses access at once. Roles: owner, admin, member and auditor.
- Time-limited auditors. External auditors confirm a one-time code on every visit and get read-only access for 1 to 60 days, which an admin can revoke at any time.
- Activity log. Every change is logged, including actions by Dazr support, and the workspace receives an email when support acts in it. The log keeps the latest 2,000 events on Free, 25,000 on Pro and 50,000 on Enterprise, and you can search and export it.
- Sealed evidence trail for the Cyber Resilience Act. Entries in the CRA module (products, releases, SBOMs, vulnerabilities, reports) are append-only and hash-chained per workspace, and Dazr seals each one with an ES256 signature that anyone can check against the public keys at identity.dazr.eu/oauth/jwks. Corrections are added as new entries.
- Signed webhooks. On Enterprise, outgoing webhooks carry an HMAC-SHA256 signature with a timestamp, made with a secret for each webhook, and go only to HTTPS addresses that resolve to public networks.
- Rate limits. Sign-in, public reporting and the API are rate-limited.
- Status. Live checks and incident reports are published at dazr.eu/status.
- Deletion schedules. Sign-in codes expire after 10 minutes and public intake submissions are deleted after 365 days. When a subscription ends, workspace content stays available for export for 30 days.
- Content Security Policy. Browsers run only the scripts we list: our own files and inline scripts identified by their hash. Plugins are blocked, and other websites cannot show our pages in a frame.
Privacy
The privacy policy explains what we process as controller and as processor, the data processing agreement covers Dazr as your processor under the GDPR, and the terms of use set out the rules for using the service.
For data inside a workspace, the organisation that owns the workspace is the controller: contact your workspace owner first. For data we hold as controller, such as your account and billing details, write to privacy@dazr.eu. We reply within 30 days.
You can also complain to a data protection authority: in Italy the Garante per la protezione dei dati personali (garanteprivacy.it), or the authority where you live or work.
Compliance and assessments
- GDPR. For workspace content Dazr is the processor for your organisation, under the data processing agreement; for accounts, billing and the website, Dazr is the controller. Company details: Dazr, Viale Cesare Poggi 1, 15061 Arquata Scrivia (AL), Italy, VAT IT 02801250065.
- ISO/IEC 27001: first audit planned. Our first ISO/IEC 27001 certification audit is planned for April 2027. Dazr is not certified yet.
- CSA STAR Level 1: self-assessment in preparation. Dazr is completing the Cloud Security Alliance’s Consensus Assessments Initiative Questionnaire (CAIQ) for the CSA STAR Registry. This page will link to the published entry.
Reporting a vulnerability
If you find a security vulnerability in one of our services, please report it to security@dazr.eu. Describe what you found and the steps to reproduce it, and name the address or app version concerned.
- Scope. The Dazr websites and services on dazr.eu and its subdomains, their APIs, Dazr Browser and the Dazr Suite apps.
- Testing with care. Use your own accounts and test data, access other people’s data only as far as needed to show the problem, and keep the service running for everyone: no denial-of-service tests, spam or social engineering.
- Safe harbour. If you act in good faith and follow this policy, we consider your research authorised and will not take legal action against you. Please give us reasonable time to fix the problem before you share details publicly.
- Our response. We acknowledge your report within 5 working days and keep you informed until the problem is fixed.
Our security contact is also published in security.txt (RFC 9116).
The full policy, including what is out of scope and how we publish fixes, is our vulnerability disclosure policy.
Contact
- Privacy and data requests: privacy@dazr.eu
- Security: security@dazr.eu
- Questions and plans: sales@dazr.eu
- Post: Dazr, Viale Cesare Poggi 1, 15061 Arquata Scrivia (AL), Italy