Back to home

Privacy Policy

Last updated: November 19, 2026

1. About this policy

This Privacy Policy explains how GuusLab (trading as Nemi) ("Nemi", "we", "us") handles personal data when you use nemilab.com, the Nemi apps and everything offered through them (the "Service"). It applies to account holders and to people who use the Service without an account, such as somebody who opens a share link, uploads through an upload link, answers a form, joins a meeting or adds a photo through a booth.

We process personal data in line with the General Data Protection Regulation (GDPR) and other applicable data protection law. We do not sell personal data, we do not show advertising, and we do not use your content to train artificial intelligence models.

2. Who is responsible

The controller of the personal data described in this policy is:

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. Questions about data protection go to the address above.

2.1 When we act as a processor

The content you store in Nemi is yours. When that content contains personal data about other people (client files, form answers, a mailbox, a shared photo library) you decide why and how it is processed, and we process it only on your behalf. For business use that relationship is governed by our Data Processing Agreement, which is part of our Terms of Service and applies automatically. If somebody shared content with you through Nemi and you have a question about it, the person or organization that shared it is your first point of contact.

3. The personal data we process

3.1 Account data

Your name, email address, optional username and profile photo; how you sign in (Google, an email code or a passkey, of which we store only the public key); your plan and settings; your time zone; the devices and sessions you are signed in on; the workspaces and organizations you belong to and your role in them; your contacts and connections; and your choices about notifications and email.

3.2 Billing data

Your plan, subscription status and invoices. Payment details are entered directly with our payment provider and never reach our servers; we store only the identifiers that link your account to your subscription.

3.3 Content

Everything you put into or create in the Service: files and folders, documents, spreadsheets, canvases and forms, form answers, photos, calendar events and tasks, mail, messages in rooms and meetings, comments, review decisions, your public page, and your conversations with Nemi AI. This includes the names you give things and the information contained in what you upload, such as the capture details a camera writes into a photograph.

3.4 Usage and technical data

IP address, browser and device type, the approximate location derived from an IP address (looked up on our own servers, never sent to a location service), timestamps, and records of actions needed to run and secure the Service, such as uploads, downloads, sign-ins and changes made in a shared workspace. We keep counts of what your plan meters, such as storage, conversions and Nemi AI use.

3.5 Communication data

Messages you send us, your email preferences, and notes our staff make when they help you, together with a record of actions staff take on your account. We do not measure whether you open or click the emails we send you.

3.6 People without an account

If you use the Service without signing in, we process only what that interaction needs:

  • Opening or downloading a share link: the time, and a salted, shortened hash of your IP address. Your IP address itself is not stored for this. The sender sees counts and times. If the sender chose to be told, an email carrying their link also reports when it was opened and when its button was pressed.
  • Uploading, answering a form, commenting or approving: what you submit, and a name or email address if you give one. It goes to the person who asked for it.
  • Joining a meeting or a room: the name you enter, when you joined and left, and what you write.
  • Writing to or receiving mail from a Nemi Mail address: the message itself, as with any email provider.

3.7 Accounts you connect

If you connect a calendar or mail account from another provider, we store the credentials that connection needs, encrypted, and a copy of the calendars or mail you chose to sync, so the Service can show and update them. You can disconnect an account at any time, which removes that copy.

3.8 Where the data comes from, and whether you must provide it

Most of this data comes from you. Some comes from others: from Google when you sign in with Google, from a provider whose account you connect, and from account holders who share with you, invite you, write to you or store content that mentions you. If we hold data about you that you did not give us, the account holder who provided it is its source.

You are not legally required to give us personal data. An email address and a name are needed to create an account, and payment details are needed for a paid plan; without them we cannot provide those. Everything else is optional.

4. Features that work differently

Most of the Service stores what you give it and shows it to the people you choose. The following work in a way that is worth knowing before you use them.

  • Vault folders are end-to-end encrypted. Their contents are encrypted on your device with a key we never hold. We cannot read them, recover them or hand them over in readable form.
  • Some things never reach our servers. A direct Glide transfer, and the audio, video and screens of a meeting, travel between the devices involved. Where a relay is needed it forwards encrypted data it cannot read. The devices in a direct connection can see each other's network address.
  • Some processing happens on your device. Photos are compressed in your browser before upload and the original file is not kept. Search by what is in a photo is computed on your device, and we store only the resulting numbers. Offline copies stay on your device and are outside our control.
  • Photo details. We read the capture date, camera settings and location from a photo and store them with it. You can have the location removed on your device before upload. The location is always removed from photos added by guests.
  • Captions and dictation send audio to a speech service. When a meeting host turns on live captions, or you dictate, the audio goes from the browser directly to our speech-to-text provider in the EU. It does not pass through our servers and we do not store it.
  • Meetings are not recorded by us. A participant can record on their own device; that recording is their file and their responsibility.
  • Trace. A sender can switch on detailed analytics for a link. It then records, for each visitor, a hashed network identifier, approximate location, device type and how long each part of a file was viewed. The sender decides to use it, is responsible for informing recipients where the law requires it, and is the only one who sees it.
  • Presence. The people you work with can see whether you are online, away or busy. We store only your latest status, never a history, and you can switch it off.
  • Nemi AI. When you ask Nemi AI something, your message, the conversation and the content it needs to answer are sent to the AI providers listed in section 6. Every request requires zero data retention and forbids training. A file you attach is kept for 24 hours unless you save it. Where a form uses Nemi AI to interview a respondent, the respondent's answers are processed the same way. Data from a Google account you connected is never sent to an AI model. If you add a connector, which is a service run by another company that Nemi AI can use for you, Nemi AI sends that service what it needs to carry out what you asked. Its provider handles that data under its own privacy policy, which we show you before you add the connector, and you can remove a connector at any time.
  • Assistants and apps you connect. You can connect your own AI assistant or sign in to an app built by somebody else. They receive only what you approve on the consent screen, limited to your own role in each workspace, and you can remove them at any time. What they do with that data is governed by their provider's terms, not ours.
  • Nemi Mail. Mail is stored encrypted. To let you search it we keep keyed fingerprints of the words in it, usable only for your own mailbox. Remote images are fetched by our servers so the sender does not learn your address. If you choose to track whether a message you sent was opened, you are responsible for doing so lawfully.

5. Why we process personal data

PurposeLegal basis
Providing the Service: your account, storing and sharing your content, the features you use, supportPerformance of our contract with you (Art. 6(1)(b) GDPR)
Payments, invoices and plan limitsPerformance of contract (Art. 6(1)(b) GDPR)
Service emails such as sign-in codes, receipts and security noticesPerformance of contract (Art. 6(1)(b) GDPR)
Security, malware scanning, abuse prevention and enforcing our TermsLegitimate interest (Art. 6(1)(f) GDPR): keeping the Service and the people who use it safe
Analytics shown to a sender about their own links, and presence shown to the people you work withLegitimate interest (Art. 6(1)(f) GDPR): letting people see what happened to what they sent and whether a colleague is available. For Trace, the legitimate interest of the sender, who decides to use it
Data about people who correspond with, share with or are invited by an account holderLegitimate interest of the account holder and of us in delivering what was sent (Art. 6(1)(f) GDPR)
Improving the Service, using aggregated usage dataLegitimate interest (Art. 6(1)(f) GDPR): understanding how the Service is used so we can maintain and improve it
Optional features you switch on, such as notifications on a deviceConsent (Art. 6(1)(a) GDPR), which you can withdraw at any time in your settings
News about Nemi sent to existing customersLegitimate interest (Art. 6(1)(f) GDPR) in informing customers about the service they use, within the rules for existing customers. You can unsubscribe at any time
Tax, accounting and lawful requests from authoritiesLegal obligation (Art. 6(1)(c) GDPR)

Where we rely on legitimate interest we have weighed it against your rights. You can ask us about that assessment or object to the processing at any time.

5.1 What we do not do

  • We do not sell personal data and we do not show or enable advertising.
  • We do not use your content, in any form, to create, train or improve AI or machine learning models, and we require the same of the AI providers we use.
  • We do not analyze or profile the content of your files, documents, mail or photos for purposes of our own.
  • We do not make decisions based solely on automated processing that have legal or similarly significant effects on you. Files are scanned automatically for malware and incoming mail is filtered for spam; you can ask for a human review of either.

5.2 Sensitive data

The Service is not designed for special categories of personal data under Article 9 GDPR (such as health data), data about criminal convictions, or data subject to sector rules such as HIPAA, the Dutch Wgbo or NEN 7510, and our Terms of Service prohibit storing it. We never ask for such data. If it reaches us anyway we protect it like all other data, use it for nothing, and delete it on request.

6. Who receives personal data

6.1 Our service providers

We use the following providers to run the Service. Each receives only what its task requires and is bound by a data processing agreement. Our application servers, file conversion, compression, malware scanning and database backups run on infrastructure we operate ourselves in the Netherlands.

ProviderWhat 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
GitHubHosts the installer of the Nemi desktop app. Receives the IP address of whoever downloads it.US: EU-US Data Privacy Framework, SCCs
ISRG (Let's Encrypt)Issues the TLS certificate for a custom domain you connect. Receives the hostname only.US. No personal data beyond the hostname

The providers behind Nemi AI receive data only on plans that include Nemi AI and only when it is used. A provider of a calendar or mail account you connect, or of a connector you add to Nemi AI, acts under its own agreement with you.

Within Nemi, only staff who need it to provide support, keep the Service secure or meet a legal duty can access account data, and they are bound by confidentiality. We do not look at the content you store unless you ask us to for a support request, or where security or the law requires it.

6.2 People you share with

Content you share is visible to the people you share it with, together with your name, profile photo and, where you have them, your username and verification badge. Members of a workspace can see what is in that workspace, the names and roles of its members, and which plan it runs on. People who receive a link or an email from you see what you sent them.

6.3 Google API data

Nemi's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data received from Google Workspace APIs (calendar and mail of an account you connect) is used only to provide the features you asked for and is shown only to you. It is never sold, never used for advertising, never used to train or improve any AI or machine learning model, never transferred to an AI service, and not read by people except with your consent for a support request, for security, or where the law requires it.

6.4 Legal requests

We disclose personal data to authorities only where the law requires it. We check each request, disclose no more than it requires and, where the law allows, tell the person concerned.

6.5 Transfers outside the EEA

We store your content in the European Union. Where a provider processes personal data outside the European Economic Area, the transfer is covered by an adequacy decision, such as the EU-US Data Privacy Framework, or by the European Commission's Standard Contractual Clauses. You can ask us for a copy of the safeguards that apply to a transfer.

6.6 If Nemi changes hands

If the Service or the company behind it is transferred to another company, personal data may be transferred with it, under this policy. We would tell you before that happens.

7. How long we keep personal data

We keep personal data only as long as the purpose requires. In practice:

DataKept
Your account and its contentUntil you delete the content or your account. Deleting your account removes it at once; remaining copies in database backups are gone within 30 days.
Files on the free planDeleted 30 days after upload, or 30 days after a paid plan ended, whichever is later. We email you before files are deleted after a plan ends.
Photos in GalleryUntil you delete them. Deleted photos stay in the trash for 30 days.
Data tied to a link, a room, a meeting or a reviewDeleted together with the thing it belongs to. This includes download records and Trace data.
MailUntil you delete it or your account.
Nemi AI conversations and attachmentsConversations until you delete them, or for the period you choose in settings. Attached files for 24 hours.
Support messages, notes by our staff, and your email preferencesFor as long as your account exists.
Short-lived codes and sign-in requestsMinutes to days, then deleted automatically.
Server logsAt most 90 days.
Invoices and billing recordsSeven years, as Dutch tax law requires.

Uploaded files are not backed up: file storage holds one copy and deletion is permanent. Copies kept on your own device, such as offline files, are not deleted by us.

8. Cookies and device storage

We use only the cookies and browser storage the Service needs. We use no advertising or cross-site tracking cookies, so there is no cookie banner to accept.

KindWhat forKept for
Strictly necessaryKeeping you signed in, protecting forms against forged requests, remembering that you unlocked a protected link or may edit a shared document, recognizing your device in your list of sessions, and completing a connection to another account.From the session up to 400 days
PreferencesYour theme, accessibility settings, time zone, active workspace and the order of your apps, so pages arrive the way you set them.Up to one year
Storage on your deviceInterface choices and, if you turn it on, offline copies of your content. This stays on your device.Until you clear it

9. Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you and receive a copy;
  • have inaccurate data corrected;
  • have your data erased;
  • restrict or object to processing, including processing based on legitimate interest and marketing;
  • receive your data in a portable format;
  • withdraw consent where processing is based on it, without affecting what was done before;
  • not be subject to a decision based solely on automated processing that significantly affects you.

You can exercise most of these yourself in your account settings: export your data, correct your details, delete content or delete your account. For anything else, email support@nemilab.com. We answer within one month, free of charge, and may ask you to confirm your identity first. In complex cases the law allows us to take up to two further months, and we tell you if we need them.

You can lodge a complaint with a data protection authority, in particular in the country where you live. In the Netherlands that is the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl). In the United Kingdom these rights apply under the UK GDPR and the authority is the Information Commissioner's Office. Wherever you live, we apply the protections in this policy and honor the rights your local law gives you.

10. Security

We protect personal data with technical and organizational measures appropriate to the risk, including:

  • encryption in transit (TLS) and at rest (AES-256);
  • additional encryption of what you write, such as documents, messages, mail and AI conversations, before it is stored in our database;
  • end-to-end encryption for vault folders;
  • storing passwords and access tokens as one-way hashes wherever they do not need to be shown again;
  • role-based access control in workspaces and least-privilege access for our staff;
  • automated malware scanning of uploaded files, and isolation of anything a browser could execute;
  • rate limits on sign-in attempts, link passwords and other sensitive actions.

Our servers hold the keys needed to provide the Service, so encryption at rest protects copies of the data rather than hiding your content from us. Only a vault does that. If a personal data breach puts your rights at risk, we notify the supervisory authority within 72 hours and inform you without undue delay.

11. Children

The Service is not directed at children under 16 and we do not knowingly collect their personal data. If we learn that we hold data of a child under 16 without parental consent, we delete it.

12. Email from us

We send service emails that are part of the Service, such as sign-in codes, receipts and security notices, and these cannot be switched off. We also send news about Nemi to existing customers. Every such email has an unsubscribe link.

13. Changes to this policy

We update this policy when the way we handle personal data changes or when the law requires it. The date at the top shows the current version. If a change is material, we tell you through a notice in the Service and, where appropriate, by email before it takes effect.

14. Contact

For questions about this policy or your personal data, email support@nemilab.com or write to GuusLab (trading as Nemi), Emmaweg 46, 3603 AN Maarssen, province of Utrecht, The Netherlands.