Skip to content
  • Reporting since 11 Sept 2026
  • Full application from 11 Dec 2027
  • Servers in Germany
  • System status →

Privacy policy

This is a translation for convenience. The German version is legally binding.

1. Controller

Jean Bogner, Ostring 6, 64832 Babenhausen, Germany, email: info@nebrino.de – see also the legal notice (Impressum).

No data protection officer has been appointed; there is no statutory obligation to do so.

2. Hosting

We operate the website, application, database and file storage on our own servers provided by Hetzner Online GmbH (Gunzenhausen, Germany) in Germany: in the Falkenstein data centre (operation) and the Nuremberg data centre (encrypted backup copies). A data processing agreement under Art. 28 GDPR is in place with Hetzner. Server log data is generated in the process (IP address, time, page accessed, browser). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation and in defending against attacks). Retention period: server log data is deleted after 14 days at the latest.

3. Database and sign-in

We store accounts, organisations and the data entered in the application (products, SBOMs, findings, reporting cases, documentation, evidence) in a self-hosted database (Supabase, open source) on these servers. No data is transferred to the provider of the software. Legal basis: Art. 6(1)(b) GDPR (contract). For security, sign-in events are logged with IP address and browser; we delete these entries after 90 days (Art. 6(1)(f) GDPR, legitimate interest in detecting misuse). We back up the database and file storage daily in encrypted form; the backups are kept on the server in Falkenstein and, as a copy, on a second Hetzner server in Nuremberg. Daily backups are deleted after 30 days, monthly backups after three months.

Changes to subject-matter details (such as products, assessments, documentation, reporting cases) are recorded in a change log with time and the person making the change, so that your organisation can trace changes; it is part of your organisation’s data. Retention: we keep an organisation’s data, including the change log, until the organisation is deleted – by you or at the latest 30 days after the end of the contract (Terms § 8); your user account until you have it deleted. The data disappears from backups when they expire, after three months at the latest. Statutory retention obligations (for example for invoices) remain unaffected.

We store acceptances of the terms and conditions, pilot terms and rules of use with version and time. If a person in an organisation created by an advisor accepts the client terms, we also store their name, position and the email address of the advisor whose engagement they confirm. The purpose is to prove the conclusion of the contract; legal basis Art. 6(1)(b) GDPR, retention as for the organisation’s data.

4. Cookies and local storage

We only use technically necessary cookies and entries in the browser’s local storage (localStorage) that are required for sign-in or for settings you have chosen. We do not use analytics or marketing cookies; for our cookieless audience measurement see below.

NamePurposeDuration
sb-…-auth-token (possibly split into .0, .1 …)Sign-in: Supabase Auth sessionuntil sign-out, at most 400 days
nebrino_orgactive organisation if an account has several organisations1 year
nebrino_localeselected interface language1 year
nebrino_themeselected colour scheme (light/dark)1 year
nebrino_pilot_hintnotice about the pilot phase in the application dismissed1 year
nebrino_notifications_seen (localStorage)time up to which notifications count as readuntil deleted in the browser
nebrino_sidebar_collapsed (localStorage)state of the sidebar (collapsed/expanded)until deleted in the browser
nebrino_survey_laterpilot survey in the application set to “Later”7 days

Legal basis for storing and reading: Section 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act – strictly necessary for the service you requested); for the subsequent processing Art. 6(1)(b) GDPR (sign-in) or Art. 6(1)(f) GDPR (settings; legitimate interest in keeping the settings you chose).

Audience measurement (Umami)

To understand how our website is used, we use the open-source software Umami. Umami runs on our own servers at Hetzner in Germany; no data is transferred to third parties. Only the public website and the sign-in and registration pages are measured – not the application after sign-in, not the supplier portal and not the vulnerability disclosure portal.

Measurement runs entirely on our server: when your browser requests a page, our server reports the page view to Umami. We only use information your browser sends with every request anyway – page visited (without parameters in the address, except campaign details such as utm_source), time, referring page (without parameters), user agent (from which browser, operating system and device type are derived), language setting and IP address (from which the country or region is derived). No tracking script runs in your browser; nothing is read from or stored on your device, and no cookies are set. The IP address is not stored. To group the page views of one visit, Umami derives an identifier from the IP address, user agent and a regularly changing secret, from which the IP address cannot be recovered. If your browser sends “Do Not Track” or “Global Privacy Control”, no measurement takes place.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in improving our offering). You may object to the processing at any time (Art. 21 GDPR), e.g. by email to info@nebrino.de, or prevent it with “Do Not Track” or “Global Privacy Control” in your browser. Retention: the data is deleted after 13 months.

5. CRA check

The CRA check runs entirely in your browser: your answers and the result are not transmitted to us and not stored. Until 2 October 2026 it was possible to leave an email address there; we delete these earlier entries (email address, optionally company, answers) at the latest twelve months after they were made, or immediately on request. The waiting list of the pilot programme is described in the section on the pilot programme.

Survey under guides

Under some guides you can answer two questions anonymously (your role and whether support in Nebrino would help you). We only store your two answers, the guide, the language and the time – no IP address, no account and no contact details. To limit mass submissions, our server counts submissions per IP address for one hour in memory only; the IP address is not stored. We discard obviously automated submissions and store at most a limited number of answers per guide and day. Nothing is stored in your browser for the survey. We also count the submission and clicks on “Register your interest” as events in our audience measurement (guide, role, answer; as described above). Anyone who registers interest is taken to the contact form and decides there whether to write to us. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in improving our service).

6. Contact form

We forward enquiries submitted via the contact form (topic, name, company, email address, message and, for certain topics, the number of products or clients) by email via Brevo (section 15) to our mailbox; replies are sent to the address provided. Enquiries are not stored in the application. To prevent abuse, we count enquiries per IP address for one hour; only a hash of the IP address is stored for this purpose and deleted after two days at the latest. Legal basis: Art. 6(1)(b) GDPR where your enquiry relates to a contract, otherwise Art. 6(1)(f) GDPR (legitimate interest in answering enquiries). Retention in the mailbox: we delete enquiries once they have been dealt with, at the latest two years after the last message – unless statutory retention obligations (e.g. for business letters under Section 147 AO, Section 257 HGB) apply.

7. Pilot programme

When you sign up with a pilot seat, we store which account and which organisation a pilot seat was assigned to, as well as the domain of the email address (e.g. “example.com”; no domain for general email providers), in order to grant no more than one pilot seat per person and per company. This assignment is retained even after the organisation is deleted and is deleted together with the user account. The operator receives a weekly report on the pilot organisations (name of the organisation, email address of the owner, number of members, usage figures such as the number of products, SBOMs and reporting cases, last activity, open feedback) in order to support the pilot phase. Legal basis: Art. 6(1)(b) GDPR (pilot agreement); for the weekly report Art. 6(1)(f) GDPR (legitimate interest in supporting the pilot phase and checking the allocation of places).

8. Pilot waiting list

If all pilot seats have been taken (or sign-up for the pilot programme is closed), you can join a waiting list on the registration page. If we grant pilot seats only on request, you use the same form to request a pilot seat; we review the request based on your details. We store your company, business email address, your role (manufacturer, importer, distributor, consultant), optionally the approximate number of your products and a message, the language and the times of entry, confirmation, offer and notification. Purpose: allocating pilot seats that become available and informing you once about the general launch of Nebrino.

Double opt-in: after submitting, you receive an email with a confirmation link (sent via Brevo, section 15). Only after confirmation is the entry active and the operator informed by email; unconfirmed entries are deleted after 30 days. If we offer you a pilot seat, you receive a personal registration link valid for 14 days and only for your email address. You receive a one-time notification when Nebrino launches.

You can unsubscribe at any time via the link in every email; we remove your optional details (number of products, message) immediately and delete the entry completely after 30 days. We also delete entries 30 days after the launch notification or after registering via an offer, and immediately on request. Waiting entries are stored until the launch notification, at most 18 months after your confirmation. Offers (email address, validity, redemption) are deleted 30 days after expiry or redemption. To prevent abuse, we count entries per IP address (one hour) and per email address (one day); only hash values are stored and deleted after two days at the latest. Legal basis: consent (Art. 6(1)(a) GDPR); you can withdraw it at any time with effect for the future.

9. Feedback in the application

We store messages sent via the feedback function together with the category, text, the page accessed (without query parameters), account and organisation. The operator is notified of new messages by email. Replies appear in the application and are also sent by email; the email can be switched off in the settings. Messages are deleted together with the organisation; if the user account is deleted, the message is retained without reference to the account. Legal basis: Art. 6(1)(b) GDPR (support under the contract) and Art. 6(1)(f) GDPR (improving the application).

10. Demo playground

On request, we create a separate demo organisation with sample data for your account. It is assigned only to you, receives no emails from automated checks and is automatically deleted with all its content 30 days after it was last opened; if your user account is deleted, it is also removed automatically. Legal basis: Art. 6(1)(b) GDPR (contract).

11. Supplier portal (third-party data)

Customers can record suppliers with a contact person and email address and send them a link for uploading documents (SBOM, VEX, security information). When uploading, suppliers provide their name and email address; we store this information together with the files in the customer’s organisation. We process this data on behalf of the customer (Art. 28 GDPR); the customer is the controller. We send requests and reminders by email via Brevo (section 15).

12. Vulnerability disclosure portal (CVD portal)

Customers can use Nebrino to operate a public page for coordinated vulnerability disclosure with a reporting form. Reporters provide their email address and, optionally, their name, the affected product, a description and the potential impact, and can choose whether and under which name they want to be credited. We store this information in the customer’s organisation; the customer’s team is notified by email via Brevo (section 15). To prevent abuse, we count reports per IP address for one hour; only a hash of the IP address is stored for this purpose and deleted after two days at the latest. We process the reports on behalf of the customer (Art. 28 GDPR); the customer is the controller.

13. Brokering to notified bodies

When customers submit a conformity assessment enquiry, we store the contact person, email address, product data and the details of the enquiry in the customer’s organisation and forward them by email to the operator. We only pass the enquiry on to notified bodies at the customer’s express request, and only to bodies that match the enquiry. Legal basis: Art. 6(1)(b) GDPR (contract).

14. Single sign-on and two-factor authentication

If a customer sets up single sign-on (SAML), its identity provider transmits the person’s email address and, where available, name when signing in; we store this information in the user account and the identity provider configuration (metadata, domains) in Supabase Auth. For two-factor authentication, we store the registered factor (TOTP authenticator app) in Supabase Auth with the user account. Legal basis: Art. 6(1)(b) GDPR (contract) and Art. 32 GDPR (security of processing). The factor is stored until you remove it or your user account is deleted.

15. Sending emails

We send emails (sign-in and confirmation links, invitations, notifications about actively exploited vulnerabilities and reporting deadlines) via Brevo (Sendinblue SAS, Paris, France) as a processor (data processing agreement as part of Brevo’s terms of use). Brevo stores the data on servers in France, Germany and Belgium; for delivery, Brevo also uses Cloudflare (USA/EU, basis: EU-U.S. Data Privacy Framework or standard contractual clauses). Brevo records in anonymised form whether emails are opened and links are clicked (“anonymous tracking” setting); we do not evaluate this information.

If a customer enters their own webhook address in the settings (e.g. for Microsoft Teams or Slack), we also send alerts there: type of alert, name of the organisation, product, title of the reporting case or vulnerability identifier, reporting stage, deadline and a link into the application – no email addresses or names of persons. The customer chooses the receiving service and is responsible for its processing. Legal basis: Art. 6(1)(b) GDPR (contract).

16. Payment processing

We process payments, subscriptions and invoices via Stripe (Stripe Payments Europe, Limited, Dublin, Ireland). Stripe processes the name or company name, billing address, email address, VAT ID and payment details. Only Stripe receives card details, not us. Stripe also transfers data to Stripe, Inc. in the USA on the basis of the EU-U.S. Data Privacy Framework or standard contractual clauses. Legal basis: Art. 6(1)(b) GDPR (contract) and Art. 6(1)(c) GDPR (retention obligations under tax law). Stripe processes the data partly on our behalf (operating the payment platform) and partly as an independent controller, for example for fraud prevention, to comply with legal obligations (anti-money-laundering checks) and for its own billing; Stripe’s privacy policy applies to this: stripe.com/privacy.

17. External data sources

For vulnerability matching, the server queries public databases (OSV.dev, NVD, CISA KEV catalogue). Package names and versions from your SBOMs are transmitted in the process, but no personal data. If the CISA website cannot be reached, the server downloads the KEV catalogue from CISA’s official mirror on GitHub (GitHub Inc., USA); nothing is transmitted in the process. From the European Union Vulnerability Database (EUVD) operated by ENISA, the server retrieves the list of exploited vulnerabilities and searches for vulnerability identifiers (CVE); no information about you or your products is transmitted. The EPSS scores (Exploit Prediction Scoring System by FIRST) are downloaded daily as a public complete file; nothing is transmitted in the process. For the information on harmonised standards and notified bodies, the server checks public EU sources (Official Journal of the EU, NANDO) and ENISA’s information pages on the reporting platform for changes daily; no personal data is processed in the process. All subprocessors and data sources are listed on the subprocessors page (German).

18. Your rights

Right of access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21 GDPR), as well as the right to lodge a complaint with a supervisory authority. The authority competent for us is: The Hessian Commissioner for Data Protection and Freedom of Information, Gustav-Stresemann-Ring 1, 65189 Wiesbaden, datenschutz.hessen.de. You may also contact the authority of your place of residence or work. To exercise your rights, an informal message to info@nebrino.de is sufficient.

Last updated: 23 Oct 2026