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.
Who we are. SeQurance (eenmanszaak), trading as SeQurance, Dutch Chamber of Commerce no. 81889798, address Reigersweg 154, 7331 TR Apeldoorn. Contact for privacy questions and requests: legal@sequrance.nl.
1. Our role
We are the controller for account administration, billing, accounting and the security of our own service. For the personal data that customers put into their inventories, SBOMs, notes and evidence files we are the processor, under the Data Processing Agreement; the customer decides why that data is used.
2. What we process, why, and on what basis
| Data | Why | Basis (when we are controller) |
|---|---|---|
| Organisation name, work e-mail address, optional name, password (stored only as a salted scrypt hash), role, two-step verification secret (encrypted) | Registration, sign-in, providing the service | Contract |
| Terms acceptance: version, time and who accepted | Evidence of the agreement | Contract, legitimate interest |
| Subscription, plan, Stripe customer and subscription references, invoice data | Billing and administration | Contract, legal obligation |
| Audit trail of sensitive actions (who did what and when, with the IP address) and request logs (time, address, path, status, signed-in e-mail) | Security, abuse detection, investigation, accountability | Legitimate interest (security of the service) |
| E-mails we send (confirmation, password reset, alerts the customer configured, billing notices) and delivery results | Operating the service | Contract |
| Customer content: inventory, SBOMs, findings, decisions, notes, evidence files | Providing the service on the customer's instructions | We are processor; the customer determines the basis |
| Messages you send us | Answering you | Contract, legitimate interest |
We do not use analytics, advertising or tracking services, we do not sell data, and we do not make decisions about people by automated means.
3. Who receives data
See the subprocessor list. In short: a hosting provider (all data is stored on our server there), an e-mail delivery provider (Resend), and a payment provider (Stripe, which sees payment details; we never see card numbers). One feature sends customer-derived data to a third party: to find known vulnerabilities in the packages of your inventory, the package identifiers (ecosystem, name, version) of components that have one are looked up at OSV.dev. These identifiers are not personal data but can reveal what software you run; if that is a concern, do not add such components, or ask us.
4. Where
The server is in the European Union (provider confirmed; the data centre is in Frankfurt, Germany). Some providers may process data outside the EEA (in particular Stripe). Where that happens we rely on a valid transfer mechanism (an adequacy decision such as the EU-US Data Privacy Framework, or standard contractual clauses). We do not claim that all processing stays within the EEA.
5. How long
- Account and workspace data: as long as the account exists. When an administrator deletes the organisation it is removed from the live system immediately; copies in back-ups expire within 35 days at the latest.
- Sessions: 12 hours; expired sessions are removed automatically.
- Synchronisation records: 30 days. Processed alert events: 90 days.
- Audit trail: for the life of the account (it is part of the customer's own accountability).
- Server logs (including IP addresses): rotated automatically, kept for days rather than months.
- Invoices and payment records: at the payment provider and in our accounts for the statutory period, generally seven years.
6. Your rights
You can ask us for access, correction, deletion, restriction, portability and object to processing, and withdraw consent where we rely on it, by writing to legal@sequrance.nl. We answer within one month. Administrators can export all data of their organisation and delete the organisation themselves in the application. If we are only the processor for data in a customer's workspace, we refer the request to that customer. You can complain to the Dutch Data Protection Authority (autoriteitpersoonsgegevens.nl).
7. Security and incidents
See the Security Statement. A personal data breach is handled under a written procedure: we notify affected customers without undue delay and, where we are controller and there is a risk to people, the Authority within 72 hours.
8. Cookies
Only strictly necessary cookies and one preference; no banner is needed. See the Cookie and Browser Storage Notice.
9. Changes
We publish updates here and keep earlier versions. Version 2026-11 (draft, 19 November 2026).