Data processing agreement
Version of 17 November 2026 (version 2.0)
This English version is a convenience translation. The German version is binding.
1. Subject matter, parties, term
1.1 This agreement governs the processing of personal data that we:namix GmbH, Hugo-Distler-Str. 10, 90411 Nürnberg, Germany (“we”, “processor”) carries out on behalf of the customer (“customer”, “controller”) when providing 1001lessons.io (the “service”). Under clause 10.1 of the Terms it forms part of them and is accepted with them. Terms have the meaning given in the General Data Protection Regulation (“GDPR”).
1.2 This agreement runs as long as the contract for the use of the service and beyond it until we have deleted the data under section 10.
1.3 For the processing of personal data, this agreement prevails over the Terms where they conflict.
1.4 For account, contact and billing data and for the data of visitors to our website we are controller ourselves; the privacy policy applies to them, not this agreement.
2. Nature, purpose and scope of the processing
2.1 Purpose. We process the data solely to provide the service under section 2 of the Terms: capturing knowledge from Slack and the web app, storing it, organising it in Clouds, tagging, searching and summarising it, answering questions about it with the AI assistant jinni, providing it as a Markdown feed and export, and returning answers and notices to the customer’s Slack workspace.
2.2 Nature. Collection, storage, organisation, alteration (such as generating titles and summaries), retrieval, consultation, use, disclosure to the customer’s users and to its Slack workspace, and erasure. Processing by AI models through Amazon Bedrock is part of the service, not a purpose of its own. The customer’s content is not used to train AI models.
2.3 Types of personal data.
- the content of entries (text, links and what users add to them), including persons named in it;
- for forwarded Slack messages, the original author’s id and name and the channel;
- questions to jinni and its answers;
- data derived from these: titles, summaries, tags, vector embeddings;
- ids and names of users as far as they are linked to content (who created, changed or deleted an entry), and the change log of it.
2.4 Data subjects. The customer’s users (such as its employees and the members of its Slack workspace) and persons named in content or whose messages are forwarded.
2.5 The service is not intended for special categories of personal data (Art. 9 and 10 GDPR). The customer works towards its users not capturing such data.
2.6 Location. The processing takes place exclusively in the European Union. We process data in a third country only with the customer’s prior consent in text form and under the conditions of Art. 44 et seq. GDPR.
3. Instructions
3.1 We process the data only on the customer’s documented instructions. Instructions are this agreement, the Terms and the settings and actions through which the customer and its users operate the service (such as capturing, editing, sharing and deleting entries). The customer gives further instructions in text form to privacy@1001lessons.io.
3.2 If Union or Member State law requires us to process data otherwise, we inform the customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.
3.3 If in our opinion an instruction infringes the law, we inform the customer without delay. We may suspend carrying it out until the customer confirms or changes it.
3.4 An instruction that would change the scope of the service is treated as a change request.
4. Confidentiality
Every person at our end who may have access to the data has committed to confidentiality or is under a statutory obligation of confidentiality. They access customer content in the production system only as far as operation, fixing faults, security or carrying out an instruction (such as an erasure) requires.
5. Security of processing
5.1 We take the technical and organisational measures under Art. 32 GDPR described in Annex 1.
5.2 We develop the measures with the state of the art. We may replace them with equivalent or better ones; the level of protection must not decrease. We document material changes.
6. Sub-processors
6.1 The customer gives us general authorisation to engage other processors (“sub-processors”). Those named in Annex 2 are authorised.
6.2 We announce a new or replaced sub-processor at least four weeks before engaging it, in text form to the contact address stored with the account. Within that period the customer may object in text form on important data-protection grounds. If we find no solution, the customer may terminate the contract with effect from the date the sub-processor would be engaged; clause 12.4 of the Terms applies accordingly.
6.3 We bind every sub-processor by contract to the same data-protection obligations as this agreement sets out, in particular to sufficient guarantees of appropriate technical and organisational measures. We are liable to the customer for its performance as for our own.
6.4 Ancillary services such as telecommunications are not sub-processing. Slack is not our sub-processor: the customer runs its Slack workspace with its own provider; what we send there we send on its instruction.
7. Assisting the customer
7.1 Data subjects’ rights. We assist the customer with appropriate measures in responding to requests under Art. 12 to 23 GDPR. For this the service offers in particular editing and deleting single entries and exporting all content; we erase a user or the whole account on request in text form under clause 10.3 of the Terms. If a data subject contacts us, we forward the request to the customer without delay and do not answer it ourselves unless the customer instructs us to.
7.2 Obligations under Art. 32 to 36 GDPR. Taking into account the nature of the processing and the information available to us, we assist the customer with the security of processing, with notifications and communications after personal data breaches, with a data protection impact assessment and with a prior consultation of the supervisory authority.
7.3 Assistance beyond the functions of the service we may provide against reimbursement of the documented effort, unless it is caused by a breach of this agreement or the GDPR on our part.
8. Personal data breaches
We notify the customer of a personal data breach affecting its data without undue delay after becoming aware of it, where possible within 48 hours, to the contact address stored with the account. The notification contains, as far as known, the information under Art. 33(3) GDPR; what is not yet known we provide later. We take the measures needed to contain and remedy the breach without delay.
9. Evidence and audits
9.1 On request we make available to the customer all information necessary to demonstrate compliance with the obligations of Art. 28 GDPR — in particular this agreement with its annexes and our sub-processor’s evidence of its certifications and audit reports.
9.2 Where this information is not sufficient in a given case, the customer may require an audit by itself or by an auditor it appoints who is bound to confidentiality and is not our competitor. The customer announces an on-site audit at least 30 days in advance in text form; it takes place during normal business hours without disrupting operations, and at most once per calendar year unless a personal data breach or a supervisory authority gives reason for another. The customer bears its own costs.
9.3 Our sub-processor’s data centres are not our business premises; their audit follows its certifications and audit reports.
10. Erasure and return
10.1 Data is returned through the export in the service: the customer can download its knowledge as Markdown files or retrieve it via the Markdown feed at any time, including during a notice period (clause 12.3 of the Terms), during the lock before a deletion (clause 10.3 of the Terms) and when switching provider (clause 12.7 of the Terms).
10.2 We delete the data under clause 10.3 of the Terms: 14 days after a Knowledge Master deleted the workspace in the app’s settings, 7 days after a user deleted their own account, 14 days after the Slack app is removed unless it is added again within that period, and after a switch of provider at the end of the retrieval period under clause 12.7 of the Terms. Copies in backups are overwritten within 14 days. Any obligation to retain data under Union or Member State law remains unaffected.
10.3 We keep a record of every erasure stating that and when it took place; on request we confirm the erasure in text form.
11. Liability
Liability towards data subjects under Art. 82 GDPR remains unaffected. Between the customer and us, section 9 of the Terms applies.
12. Changes and final provisions
12.1 We announce changes to this agreement like changes to the Terms under their section 11; for sub-processors section 6 applies. Every version stays retrievable at its own address.
12.2 Declarations under this agreement require text form. Otherwise section 14 of the Terms applies (governing law, place of jurisdiction, severability).
Annex 1 — Technical and organisational measures (Art. 32 GDPR)
1. Confidentiality
- Data centres: the service runs entirely on Amazon Web Services in Frankfurt am Main. We run no servers of our own; physical access control, fire protection and power supply of the data centres are AWS’s responsibility (certified to ISO/IEC 27001 and audited under SOC 2, among others).
- Access to the service: users sign in through Slack or Google; the service has no passwords of its own. The session is held by a secure cookie sent over HTTPS only.
- Administrative access: day-to-day work on the infrastructure runs through AWS IAM Identity Center without long-lived access keys. The root and emergency access are protected with a hardware key or passkey as second factor; every use of the emergency access is logged. Operator accounts of the application require a second factor (one-time code). The databases cannot be reached from the internet.
- Access control and separation: each customer’s data is separated from other customers’ in several independent layers; every query is bound to the customer. Within a customer, a role and permission model governs who may read and edit which Clouds; private spaces are accessible only to the person they belong to. Development and production are fully separate (own databases, storage and sign-in services); no customer content is used in development.
- Encryption: databases and file storage are encrypted at rest (AES-256). Each customer’s Slack app credentials are additionally encrypted in the application (AES-256-GCM, key in AWS Secrets Manager). Every transfer between browser, Slack and the service is TLS-encrypted; unencrypted requests are redirected to HTTPS.
2. Integrity
- Transfer control: data does not leave the EU. AI requests go exclusively through Amazon Bedrock with EU inference profiles; the application checks this at every start and does not start if a setting would process data outside the EU.
- Input control: a change log records who created, changed or deleted which entry and when (kept twelve months). AWS CloudTrail logs administrative actions in the infrastructure.
3. Availability and resilience
- Automatic backup of the production database with restore to any point in the last 14 days; deletion protection of the production database.
- A web application firewall with rate limiting in front of the service; threat detection (Amazon GuardDuty); automatic scanning of container images for known vulnerabilities; monitoring with alarms.
4. Testing, assessing and evaluating
- Every change to the service passes automated tests and a check for accidentally published secrets before it ships; code changes are additionally checked for security flaws automatically.
- We keep a data protection impact assessment and records of processing activities and review these measures with every material change, at least once a year.
- Data protection by default: no use of content to train AI models, no tracking or analytics services in the application, limited retention of logs (application 5 or 7 days, database 7 days).
- Control of processors: we engage sub-processors only under section 6 and Annex 2, each with a contract under Art. 28 GDPR.
Annex 2 — Sub-processors
Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg
- Service: operation of the whole service — compute, database, file storage, e-mail sending, logs — and AI processing through Amazon Bedrock (models by Anthropic that AWS runs itself; Anthropic receives no content).
- Location of processing: Frankfurt am Main (EU); AI processing in EU regions only.
- Contract: the AWS Data Processing Addendum with Standard Contractual Clauses as an additional safeguard.