Draft. This document has not yet been reviewed by a lawyer; it describes our intended and current practice and will be finalised before it is relied on as a contract.
Parties: (1) the Customer named in the order or registration (controller) and (2) SeQurance (eenmanszaak), Chamber of Commerce no. 81889798, address Reigersweg 154, 7331 TR Apeldoorn (processor, "SeQurance"). This agreement applies where SeQurance processes personal data on the Customer's behalf; it does not cover SeQurance's own activities as controller (see the Privacy Statement). It forms part of the Terms of Service.
1. Subject and duration
Hosting, delivery, support and security of the SeQurance service, and wind-down, for the term of the subscription plus the deletion period in section 9.
2. Instructions
SeQurance processes personal data only on the Customer's documented instructions, which include the configuration the Customer makes in the service and the Terms, unless EU or Member State law requires otherwise (then SeQurance informs the Customer beforehand unless the law forbids it). SeQurance tells the Customer if an instruction appears to infringe data-protection law.
3. Confidentiality and security
People with access are bound to confidentiality. SeQurance implements the measures of Article 32 GDPR that fit the risk, as described in Annex B and the public Security Statement. Material reductions of that level are announced.
4. Subprocessors
The Customer gives general written authorisation for the subprocessors in the list (Annex C). SeQurance announces a new or replaced subprocessor at least 30 days ahead to the administrators by e-mail and in the application; the Customer may object on reasonable data-protection grounds within that period, after which the parties look for a solution or the Customer may terminate the affected subscription. SeQurance imposes equivalent obligations on subprocessors and remains responsible for them.
5. Assistance
Considering the nature of the processing, SeQurance helps the Customer, with the information it has, to answer data-subject requests, to meet security, impact-assessment and prior-consultation duties, and to answer supervisory authorities. A request that reaches SeQurance directly is passed on without undue delay. The administrators can export and delete the organisation's data themselves in the application.
6. Personal data breaches
SeQurance notifies the Customer without undue delay after becoming aware of a personal data breach concerning data it processes for the Customer, and provides the information it has about nature, categories, consequences and measures, adding to it as it learns more. The Customer, as controller, decides on notifying the authority and the people concerned.
7. Transfers outside the EEA
Only with a valid mechanism under Chapter V GDPR (an adequacy decision or standard contractual clauses). The subprocessor list says which subprocessors can involve such transfers. Hosting in the EU does not by itself mean that all access stays within the EEA.
8. Audit
SeQurance provides the information needed to show it complies with Article 28 and contributes to audits by the Customer or an auditor it mandates, with reasonable notice and subject to confidentiality and the security of other customers.
9. End of the processing
When the subscription ends, the Customer can export its data and delete the organisation in the application. Remaining copies in back-ups are removed as they expire, within 35 days, unless the law requires keeping them.
10. Other
Liability and governing law follow the Terms to the extent consistent with mandatory data-protection law. Changes are made in writing, including electronically.
Annex A — Processing details
| Item | Description |
|---|---|
| Purpose | Vulnerability intelligence and analysis of the Customer's software inventory and SBOMs |
| Data subjects | The Customer's staff and contacts; people named in SBOM or inventory metadata |
| Types of data | Names, work e-mail addresses, roles, sign-in and audit records (including IP addresses), and whatever the Customer enters in free-text fields, notes and evidence files |
| Special categories | Not intended. The Terms forbid uploading them (for example patient data) |
| Operations | Storing, organising, matching, displaying, backing up, securing and deleting |
| Location | European Union (data centre in Frankfurt, Germany); see Annex C for transfers |
| Duration | The subscription, plus deletion as in section 9 |
Annex B — Technical and organisational measures
The measures below are in place; the evidence for each is in the Security Statement and in SECURITY_REVIEW summaries available on request.
- Role-based access (viewer, analyst, administrator); two-step verification, mandatory for operators and enforceable per organisation; single sign-on via OIDC.
- Tenant separation enforced in the database itself (Row-Level Security) in addition to the application, with automated cross-tenant tests.
- Encryption in transit (TLS with HSTS); passwords as salted scrypt hashes; two-step secrets encrypted; uploaded files stored privately with integrity checks.
- Audit trail of sensitive actions; tamper-evident decision records.
- Locked and scanned dependencies, hardened containers, automated tests on every change.
- Back-ups of the database and uploaded files, kept 14 days on the server and encrypted; an encrypted copy is stored outside the server every night.
- Server hardening (automatic security updates, firewall, key-only SSH) and uptime monitoring are being completed.
Annex C — Subprocessors
See the public list, which is part of this agreement.