01
What we encrypt and how
Each item is encrypted with an AES-256-GCM key, and that key is protected with ML-KEM-768 (NIST FIPS 203). Incident and audit reports also carry an ML-DSA-65 signature (NIST FIPS 204). All of this runs inside goPrevina; it does not depend on an external cryptographic service.
- Health data
- Results and clinical text from health surveillance are stored encrypted with each company's data key.
- Sensitive documents
- Files are encrypted before they are stored, in segments, with a different key for each file.
- Stored secrets
- Integration credentials and other secrets are stored encrypted, never in plain text.
- Signatures
- Incident reports and audit records carry an ML-DSA-65 signature, so you can check they have not been modified.
02
The risk of copying today and decrypting later
A large enough quantum computer will be able to break the public-key encryption used on the internet today. That computer does not exist yet, but someone can copy encrypted data now and keep it until they can open it. This is known as "harvest now, decrypt later".
Health surveillance records are kept for many years. They have to stay protected for that whole time, not only while quantum computers do not exist.
In August 2024 NIST published the first post-quantum cryptography standards: FIPS 203 (ML-KEM, key establishment), FIPS 204 (ML-DSA, signatures) and FIPS 205 (SLH-DSA, signatures). goPrevina uses the first two.
03
One key per company, in the EU
- One key per company
- Each company has its own data key, protected with ML-KEM-768. One company's data cannot be opened with another company's key.
- Rotation
- Keys are rotated on a policy. When the protecting key is rotated, the data keys are protected again with the new one.
- Key copies
- Keys are copied, encrypted, to two EU locations: Azure and Scaleway (Amsterdam).
- Hosted in the EU
- Data is hosted at Scaleway, in Paris.
04
Who gets in and from where
- Single sign-on
- SSO with SAML 2.0 or OIDC, so people sign in with their corporate account.
- SCIM provisioning
- User creation and removal is synchronised from the company directory.
- Two-factor
- Two-step verification (2FA) for accounts.
- IP allowlist
- Each company can restrict access to the IP addresses it specifies.
05
What was done, who did it, and that it has not been changed
- Audit log
- Actions are attributed to a person and a date.
- Signed reports
- Incident reports and audit records carry an ML-DSA-65 signature.
- Streaming to your SIEM
- Audit events can be streamed continuously to the company's SIEM.
06
Backups: what exists today
The database is backed up every 6 hours, and once a day a copy is stored in another region. If the database fails, at most the last 6 hours can be lost; if a whole region is lost, up to 24 hours. Today we do not offer high availability or a guaranteed recovery time.
- Every 6 hours
- Database backup.
- Every day
- Copy in another region.
- Keys
- Encrypted copies in Azure and Scaleway (Amsterdam).
07
Where the data is
Customer data is stored and processed in the European Union. The locations are:
- Application and database
- Scaleway, Paris (France).
- Backups
- Scaleway, Amsterdam (Netherlands).
- Artificial intelligence
- Microsoft Azure in Sweden and Ireland, processed in the EU data zone.
- Exception: Nora web search
- When Nora searches the internet, the text of the search is sent to Google and DuckDuckGo (US), without the user's IP address, cookies or identity.
08
Who else processes data
These are the providers involved in the service. Integrations a company turns on itself (e-signature, messaging, calendars) are not sub-processors: the company chooses them. Changes to the list: 30 days' notice.
- Scaleway SAS (France)
- Servers, database, documents, backups, logs and transactional e-mail. Paris and Amsterdam.
- Microsoft Ireland Operations Ltd (Azure)
- Nora's artificial intelligence and voice models, in the EU data zone (Sweden and Ireland), and storage of encrypted key copies.
- Google LLC and DuckDuckGo, Inc.
- Only the text of Nora's web searches, without identifying the user.
- Mollie
- Payment of subscriptions. Billing data of the contracting company, not of its workers.
- Vercel
- Only the public website goprevina.eu, not the application.
09
Processing agreement, dossier and impact assessment
Provided to anyone who asks. The dossier also says what does not exist yet: goPrevina has no ISO 27001, ENS or SOC 2 certification and no external penetration test report.
- Data processing agreement (GDPR art. 28)
- The agreement accepted at sign-up is published. A signable template with annexes on measures and sub-processors is available on request.
- Security dossier (CAIQ v4 questionnaire)
- An answer for each domain, with where each control is implemented or a statement that it does not exist.
- Impact assessment and records of processing
- Reference data protection impact assessment for health data (GDPR art. 9) and the record of processing activities.