Back to home

Data Processing Agreement

Last updated: November 15, 2026

1. About this agreement

This Data Processing Agreement ("DPA") applies when you use Nemi for a business, profession or organization and, in doing so, process personal data about other people through the Service. It is the agreement required by Article 28(3) of the General Data Protection Regulation (GDPR).

The DPA is part of our Terms of Service and takes effect automatically. No signature is needed. If your organization requires a signed copy, email support@nemilab.com. If you use Nemi only for personal or household purposes, this DPA does not apply to you.

Version 3.0, effective November 15, 2026.

2. Parties and roles

Processor: GuusLab (trading as Nemi), Emmaweg 46, 3603 AN Maarssen, province of Utrecht, The Netherlands, KVK 95954600 ("we").

Controller: the account holder or organization that uses the Service and decides what personal data is put into it ("you"). If you are a processor for your own customers, we are your sub-processor and this DPA applies accordingly.

You determine the purposes and means of processing the content you put into the Service ("Customer Data"). We process Customer Data only to provide the Service to you. For account, billing and technical data we are an independent controller, as described in our Privacy Policy.

As controller you are responsible for having a legal basis for the personal data you put into the Service, for informing the people it concerns, and for the lawfulness of the instructions you give us.

3. Instructions

We process Customer Data only on your documented instructions. Your instructions are this DPA and the Terms of Service, your use and configuration of the Service, including what your authorized users share, connect and ask the Service to do, and any further written instruction that is compatible with the Service and the law.

We tell you if we believe an instruction infringes data protection law. If the law requires us to process Customer Data in another way, we inform you first unless the law forbids it. We do not use Customer Data for our own purposes: we do not sell it, use it for advertising, or use it to train artificial intelligence models.

4. Data that must not be processed

The Service is not built or certified for data that requires special safeguards. As the Terms of Service state, you must not use it for special categories of personal data under Article 9 GDPR, data about criminal convictions under Article 10 GDPR, or data subject to sector rules such as HIPAA, the Dutch Wgbo, NEN 7510 or PCI DSS. You warrant that Customer Data stays within these limits.

5. Confidentiality

We treat Customer Data as confidential. Access is limited to people who need it to provide, secure or support the Service, and they are bound by a duty of confidentiality that continues after their engagement ends.

6. Security

We take appropriate technical and organizational measures under Article 32 GDPR. They are listed in Annex 2. We may update them, provided the level of protection does not decrease.

7. Sub-processors

You give us general authorization to use the sub-processors in Annex 3. Each is bound by a written agreement with data protection obligations equivalent to this DPA, and we remain liable to you for their performance.

Before we add or replace a sub-processor we announce it on this page and notify the account owner by email at least 30 days in advance. You may object on reasonable data protection grounds within that period. If we cannot offer a reasonable alternative, you may end the affected paid plan and receive a refund for the unused part of the period you paid for.

8. Rights of data subjects

The Service lets you view, correct, export and delete Customer Data yourself. Where that is not enough to answer a request under Articles 15 to 22 GDPR, we assist you on request. If a request reaches us directly and concerns Customer Data, we forward it to you without undue delay and do not answer it ourselves, unless the law requires us to.

9. Personal data breaches

We notify the account owner without undue delay, and within 48 hours, after becoming aware of a personal data breach affecting Customer Data. The notice describes the nature of the breach, the data and people concerned as far as known, the likely consequences and the measures taken or proposed. We help you meet your own notification duties under Articles 33 and 34 GDPR.

10. Assistance

On request we provide reasonable assistance with data protection impact assessments and prior consultation under Articles 35 and 36 GDPR, and the information needed to show compliance with Article 28 GDPR.

11. Requests from authorities

If an authority requests access to Customer Data, we inform you before disclosing anything unless the law forbids it. We check every request, give no authority direct or unrestricted access, and disclose no more than the request legally requires.

12. International transfers

Customer Data is stored in the European Union. Where a sub-processor processes it outside the European Economic Area, the transfer relies on an adequacy decision, such as the EU-US Data Privacy Framework, or on the European Commission's Standard Contractual Clauses, which we have agreed with that sub-processor. We provide a copy of the relevant safeguards on request.

13. Deletion and return

You can export and delete Customer Data in the Service at any time, which is how Customer Data is returned or erased at your choice. When your account is deleted, we delete Customer Data: uploaded files immediately and permanently, and remaining copies in database backups within 30 days. We keep data longer only where the law requires it. Content in a vault folder cannot be exported or read by us at any time, because only you hold its key.

14. Audits

We make available the information needed to demonstrate compliance, primarily this DPA, our Privacy Policy and written answers to your questions. If that is not sufficient, you may audit us, or have an independent auditor bound by confidentiality do so, at most once every twelve months, on 30 days written notice, during business hours, without disrupting the Service and at your own cost. An audit may not give access to data of other customers.

15. Liability, precedence and changes

The limitations of liability in the Terms of Service apply to this DPA to the extent the law allows. Nothing here limits the rights of data subjects or liability under Article 82 GDPR. Where this DPA and the Terms of Service or Privacy Policy conflict on the processing of Customer Data, this DPA prevails. It is governed by Dutch law, and disputes go to the competent court in the Netherlands.

We may update this DPA when the Service, our sub-processors or the law change. Material changes are announced as described in the Terms of Service, and sub-processor changes as described in section 7.

16. Contact

GuusLab (trading as Nemi)
Emmaweg 46
3603 AN Maarssen, province of Utrecht
The Netherlands
KVK: 95954600
Email: support@nemilab.com

We have not appointed a Data Protection Officer, because our processing does not meet the criteria of Article 37 GDPR.

Annex 1: Details of the processing

ItemDescription
Subject matterProviding the Nemi service for storing, sharing and working on content.
DurationFor as long as your account exists, plus the periods in section 13.
Nature and purposeStorage, transmission, sharing, display, conversion, scanning for malware, collaborative editing, collection of content from others on your behalf, sending and receiving mail, and, where your users ask for it, processing by the assistant in the Service.
Types of personal dataWhatever you and your users put into or collect through the Service: the content of files, documents, photos, mail and messages; names, contact details and usernames; membership of workspaces and organizations; records of sharing, downloads and visits; and technical data about uploads and connections.
Data subjectsYour employees and colleagues, your clients and customers, and anyone who receives, opens, uploads, answers, comments, writes to or is otherwise named in content handled through your account.
FrequencyContinuous, for as long as you use the Service.

Annex 2: Technical and organizational measures

  • Encryption in transit: all traffic uses TLS.
  • Encryption at rest: stored objects are encrypted with AES-256. Content written in the Service, such as documents, messages, mail and AI conversations, is additionally encrypted by the application before it is stored, with a key held outside the database.
  • End-to-end encryption: vault folders are encrypted on the user's device under a key we never hold.
  • Access control: authenticated sign-in, role-based permissions in workspaces and organizations enforced on every request that changes data, and least-privilege access for staff.
  • Credentials: link passwords and access tokens are stored as one-way hashes wherever they do not need to be shown again.
  • Abuse and malware protection: rate limits on sign-in, passwords and other sensitive actions; automated malware scanning of uploaded files on our own infrastructure; content a browser could execute is served as a download or in a sandbox.
  • Data minimization: visitor IP addresses in share analytics are stored only as salted hashes. Direct transfers and meeting media travel between devices and are not received by us.
  • Separation: customer data is separated per account, workspace and organization by application-level access control.
  • Availability: database backups on infrastructure we operate in the Netherlands, replaced within 30 days. Uploaded files are stored as a single copy and are not backed up.
  • Logging: server logs are kept for at most 90 days.
  • Development and incidents: changes are reviewed before release, dependencies are kept up to date, and breaches are handled under section 9.

Annex 3: Sub-processors

Application servers, file conversion, compression, malware scanning and database backups run on infrastructure we operate ourselves in the Netherlands. The following sub-processors are authorized:

Sub-processorWhat forWhere
Wasabi TechnologiesStorage of files, photos and document history, encrypted at rest with AES-256.EU (Amsterdam)
Amazon Web Services (SES, S3, SNS)Email delivery. Sends our account and notification emails, and receives and sends the mail of Nemi Mail addresses and custom mail domains, including spam and virus checks on incoming mail.EU (Frankfurt and Ireland). US company: EU-US Data Privacy Framework, SCCs
StripeSubscription payments and invoicing. Payment details are entered with Stripe and never reach our servers.EU and US: EU-US Data Privacy Framework, SCCs
Google (sign-in, Calendar API, Gmail API)Sign in with Google and, only if you connect them, the calendar and mail of a Google account you link.EU and US: EU-US Data Privacy Framework, SCCs
Microsoft (Microsoft Graph)Only if you connect them: the calendar and mail of an Outlook or Microsoft 365 account you link.EU and US: EU-US Data Privacy Framework, SCCs
OpenRouterRoutes a Nemi AI request to the company that runs the language model. Receives the request in order to pass it on, through its EU gateway, without logging it.EU gateway. US company: SCCs
Google (Vertex AI)Runs the language model behind Nemi AI: Vertex AI in the EU. Requests require zero data retention and forbid training.EU region. US company: EU-US Data Privacy Framework, SCCs
Microsoft (Azure)Backup host for the language model behind Nemi AI, in Azure's EU data zone, on the same terms: zero data retention, no training.EU data zone
Amazon Web Services (Bedrock AgentCore)Runs the isolated code sandbox Nemi AI uses on the plans that include it. Receives the files Nemi AI loads into it at your request.EU (Frankfurt). US company: EU-US Data Privacy Framework, SCCs
LinkupWeb search for Nemi AI. Receives only the search words, sent from our servers, and nothing about you.France. Processing is not guaranteed to stay in the EU
SonioxSpeech to text for live captions in a meeting and for dictation. Receives the audio directly from the browser of the meeting host or of the person dictating, while the feature is on.EU region. US company
Apple, Google, Mozilla and Microsoft (push notification services)Deliver notifications to your phone or browser where you turned them on. Browser notifications are encrypted so the service cannot read them; notifications to the Nemi iPhone apps carry their title and text.EU and US: EU-US Data Privacy Framework where certified, otherwise SCCs

The sub-processors behind Nemi AI receive Customer Data only on plans that include it and only when a user asks it to do something. AI assistants, apps and mail or calendar accounts that your users connect themselves are not our sub-processors: they act under your users' own instructions and their provider's terms.