English translation of the German text.

Dengel privacy notice

As of 22 November 2026.

1. Controller

NMA Venture Capital GmbH, Am Sandtorkai 27, 20457 Hamburg, Germany. Contact: info@nma.vc, +49 178 4497585. See the imprint for further details.

This notice applies to dengel.dev, the Dengel web application, and its Git and API services. For personal data in content we process on a customer's instructions, the customer determines the purposes of processing. The data processing agreement also applies.

2. Data and purposes

Activity Data and purpose Legal basis
Website, Git, and API IP address, time, resource, client and error data for delivery, stability, and abuse prevention Article 6(1)(f) GDPR: secure operation
Account and workspace Email, profile, sign-in and security attributes, roles, and settings for sign-in and collaboration Article 6(1)(b) GDPR for the contracting party and Article 6(1)(f) for its authorised team members
Git hosting Content and Git metadata, including commit authors' names and email addresses, for version control and agreed display Article 6(1)(b) or (f) GDPR for our own purposes. For data processed on a customer's behalf, the customer's instructions and legal basis apply
Development and verification jobs Selected source code, tasks, documents, model requests, results, and approvals for the requested job As for Git hosting, applied to the specific job
Billing Billing name, address, customer type, relevant registration or VAT details, payment references, amounts, and usage Article 6(1)(b) and (c) GDPR: contract and tax or commercial law
Support, reports, and legal claims Contact details, messages, and necessary case information for responding, handling abuse, and legal defence Article 6(1)(b), (c), or (f) GDPR, depending on the circumstances

We receive data from you, authorised workspace members, expressly connected services, and payment service providers. Git metadata may also relate to people without a Dengel account. Where we are the controller for that data, this notice also provides information under Article 14 GDPR. Forms identify required information. We cannot provide the relevant service without it.

3. Visibility and protection of personal data

Public repositories and published Git metadata can be accessed worldwide. Third parties may copy or index them. Deleting them from our service later does not remove independent copies.

Access to private content is limited to authorised workspace members, necessary service providers, and access for specific purposes such as operations, security, requested support, or legal obligations. Access and jobs are subject to permissions. Execution environments are separate from the authoritative repository.

We make no commitment to complete automated anonymisation of all content. Account data, recipient addresses, and Git authorship details remain personal data. Requested AI work may also require content containing personal data. Send only the necessary data and use suitable test data in place of real production datasets where possible. Keep credentials out of tasks and publicly accessible repositories.

4. AI processing, training, and storage

Git hosting alone does not authorise sending code to an AI model. For requested AI services, we use Cortecs GmbH in Austria and the approved inference providers listed in the annex. The model name and the provider actually processing the request are separate details.

We do not use non-public customer inputs or results to train general-purpose AI models. Managed inference is restricted to providers contractually prohibited from using the data for training. The active routing rule requires providers established in the EU and Zero Data Retention for request and response content. Individual requests cannot override these rules. The annex lists the processing locations.

Cortecs processes request content only transiently in its gateway. Dengel may still store the corresponding tasks and results. Under the Cortecs data processing agreement (DPA), technical metadata may remain for up to 12 months. We handle our own data and backups as described in Section 6. Customer-supplied provider credentials and other external connections do not grant blanket permission for additional data use. Any different rules must be disclosed before activation.

5. Recipients and international processing

OVHcloud provides hosting in France and regular backups in Germany. The inference chain uses the approved European providers listed in the annex. Some locations listed there are in the EEA outside the EU.

Cloudflare processes connection data and, where applicable, transmitted content for network, TLS, and protection services. Its service provider chain and any necessary support access must also be taken into account. We do not promise that all data are processed exclusively in Europe. Transfers to third countries must use the applicable safeguards, in particular EU standard contractual clauses and any necessary supplementary measures. You can request the applicable safeguards, subject to any necessary redactions.

AhaSend processes recipient details, necessary message content, and delivery data for transactional emails. According to the provider, it stores data in Germany and Finland, with transit also in the EEA. Open and click tracking are disabled on the account we use. Final delivery requires the email service chosen by the recipient.

Mollie B.V. in the Netherlands receives the payment details and any billing information it needs. Mollie acts as an independent controller for payment processing. It does not need repository content for this purpose. Mollie privacy notice.

If you sign in with Google or GitHub, the sign-in provider receives the information needed for the sign-in, and we receive the identity details you authorise it to share. Connections you activate, such as GitHub or Linear, transfer only data authorised for the selected feature. Those providers' own processing also depends on their privacy notices and your settings. Disconnecting does not automatically remove copies held by those providers. We disclose data to authorities only where we have an applicable legal basis.

6. Retention and deletion

We delete or anonymise data when they are no longer needed for their purpose, unless a legal obligation or the need to defend legal claims requires retention. We limit and protect any records that remain.

Data Retention period or rule
Account and project content Kept during agreed use. Following an applicable deletion instruction or the end of an agreed export or switching process, we actively delete data without undue delay. The timeframe depends on the request and applicable legal or contractual requirements
Technical access and error logs Central system logs expire within 14 days. Other technical logs are deleted when no longer needed for operation, diagnosis, or security. Necessary extracts for specific security incidents may be kept until investigation and, where applicable, legal proceedings are complete
Our own AI work logs 30 days after the attempt ends, except where they remain part of a specifically required work result. Such copies follow the project retention period
AhaSend email content and delivery data 7 days each on the current account. Contract and invoice records that must be kept independently are treated separately
Cortecs Request content is transient in the gateway. Technical metadata may be kept for up to 12 months under the DPA. Zero Data Retention for managed inference content is separate from the treatment of that metadata
Ordinary support correspondence Until the matter is resolved and generally for no more than 2 years afterwards. Statutory business records are treated separately
Necessary contract, approval, and delivery records For the term of the contract and, as needed for the defence of legal claims, normally until the end of the third calendar year after the contract ends. We do not retain complete source code as a matter of course for this purpose
Invoices and accounting records Normally 8 years from the end of the relevant calendar year. Other statutory business records are kept for 6 or 10 years depending on the type of document. Statutory extensions and specific ongoing proceedings may affect these periods
Regular backups Current backup objects are kept for 30 days. Older object versions expire within a further 30 days. Older migration backups are separate and are used exclusively for recovery. Deletion instructions are taken into account when restoring data

Project deletion and account closure are separate processes. Project deletion removes project files and redacts free text from related journal events. Necessary billing and approval metadata may remain for a limited period. Hashes and identifiers that can be linked to a person are also subject to data protection law. We cannot directly delete copies held by others. Statutory switching and retrieval periods take precedence over routine deletion.

7. Browser storage and your rights

Access to device storage required for sign-in and security is limited to what is necessary under Section 25(2) of the German Telecommunications and Digital Services Data Protection Act (TDDDG).

Page view counting on dengel.dev. We count page views on dengel.dev with Plausible Community Edition, which we host ourselves at OVHcloud in Strasbourg, France. Plausible sets no cookies and stores nothing in your browser. IP addresses are not stored: they are only combined with a salt that is rotated every 24 hours to form a hash, and only the country derived from the IP address is kept. We count the page visited, the referring page, the country, and the browser, operating system, and device type. If your browser sends Do Not Track, the script is not loaded. No data goes to Plausible Insights OÜ. The legal basis is Article 6(1)(f) GDPR: we want to know which pages are used without tracking individual visitors.

Any other analytics that require consent may only be enabled after you have given that consent. It must be easy to withdraw. Registration does not constitute blanket consent.

Subject to the conditions set by law, you can request access, rectification, erasure, restriction, and data portability. You can withdraw consent with effect for the future. You can object to processing based on legitimate interests on grounds relating to your particular situation. You can object to direct marketing at any time without giving a reason.

Email info@nma.vc. We normally respond within one month and explain any extension permitted by law within that period. You can complain to a data protection supervisory authority, particularly in the place where you live or work or where the alleged infringement occurred. Our supervisory authority is the Hamburg Commissioner for Data Protection and Freedom of Information.

Annex: Service providers and processing locations

The fixed version provided when you enter into the contract forms an annex to the DPA insofar as the relevant activity involves data processed on a customer's behalf. Payment processing and connections you choose are treated according to their actual roles. Changes to subprocessors follow the DPA procedure.

Provider Function and data Processing locations and role
OVH GmbH, Germany Application, Git, databases, isolated execution, and encrypted backups Dengel runtime in Strasbourg, France. Execution in Gravelines, France. Backup region in Germany. German DPA dated 17 October 2025 accepted in the customer account on 2 November 2026
Cloudflare, Inc., United States DNS, front-end TLS, CDN and protection services, connection data and transmitted content where applicable International processing is possible. Cloudflare DPA with applicable transfer safeguards
AhaSend B.V., Netherlands Transactional email Storage in Germany and Finland, transit in the EEA. DPA and subprocessor chain
Cortecs GmbH, Austria Managed AI gateway, job inputs and outputs, and operational metadata Gateway in France according to the DPA. Cortecs DPA and subprocessor chain
TensorX Ltd, Ireland, Cortecs identifier "tensorix" Potential inference subprocessor Finland and Ireland according to the Cortecs annex
Inceptron AB, Sweden Potential inference subprocessor EEA according to the Cortecs annex
Scaleway SAS, France Potential inference subprocessor France according to the Cortecs annex
IONOS SE, Germany Potential inference subprocessor Germany according to the Cortecs annex
Mistral AI SAS, France, OVH SA, France, and Nebius B.V., Netherlands Other approved Cortecs subprocessors, whose involvement varies by request Mistral: EEA. OVH: France. Nebius: Finland, France, and Iceland according to the Cortecs annex
Mollie B.V., Netherlands Payment and invoicing functions where applicable Independent controller for payment. Other roles depend on the function
Google Ireland Limited, GitHub, Inc., and Linear Orbit, Inc. Selected sign-in method or expressly activated connection Depends on the connection chosen and its contract. Required international transfers must be considered separately