Provider
Leonardo Antonio Carta (Nema)Controller
c/o Emperon Studio GmbH, Sachsenring 51a, 50677 Köln, Deutschland
This notice supplements the Nema Crew privacy policy for the Gmail module. It does not repeat what applies there to all modules. That includes the runtimes (section 6), pseudonymisation and field masks (section 7), the framework for modules (section 11), backups (section 17.6) and your rights (section 18).
1. Provider and controller
This module is offered and operated by Leonardo Antonio Carta (sole proprietor), c/o Emperon Studio GmbH, Sachsenring 51a, 50677 Cologne, Germany, support@nema.im. It runs as a separate service on our server in Germany. We are the controller. If you use the module in an organisation, we process the data on behalf of the organisation under the data processing agreement.
Google is not the provider of this module. Google processes the data in your Gmail or Google Workspace account under its own responsibility and its privacy policy.
2. What data the module processes
Access: You connect the module with your email address and an app password that you create at Google for "Nema Crew". With it, the module signs in to Gmail like an email program, using the email protocols IMAP (imap.gmail.com) and SMTP (smtp.gmail.com). The module uses no Google interface (Google API) and no sign-in via Google. We never receive your regular Google password.
When you connect and when the connection is tested, the module signs in to IMAP and SMTP once and counts your folders. It retrieves no other data in doing so.
When an agent carries out a task with Gmail, the module processes:
- details of emails: sender, recipients (To, Cc), reply-to address, subject, date, the ids of the email and the conversation (including the Message-ID and references to earlier emails), labels and folders, whether the email is read or starred, its size and whether it has attachments;
- the text of an email when an agent reads it (the text version, otherwise the HTML version converted to text). It may contain names, email addresses, phone numbers and anything else senders write;
- for attachments, only name, file type and size. The module does not download the content of attachments;
- folders and labels with their names and, on request, the number of emails and unread emails;
- what an agent writes: recipients (including Bcc), subject and text of drafts, replies and emails it creates or sends;
- search terms an agent uses to search Gmail.
The module only sees what Gmail offers over IMAP. It does not use other Google services such as Calendar, Drive or Contacts.
3. Purpose
Solely for the Nema Crew functions you use and for the tasks that you or members of your organisation give an agent. The agent acts on your behalf:
- read: list emails in the inbox, Sent, Drafts, labels and All Mail, search with Gmail search, read single emails and whole conversations, list labels;
- write: create drafts and reply drafts in the Drafts folder, send and reply to emails, mark as read or unread, archive, add and remove labels (missing labels are created) and move emails to spam or the trash.
Sending only after a preview: Before an agent sends or replies to an email, it shows the recipients, subject and text as a preview. It only sends once you agree. It also asks before moving emails to the trash.
Trigger "New email": If you have set an agent to this trigger, we check your inbox every five minutes for emails that have arrived since the last check (up to 20 per check). We then start the agent with the sender, recipients, subject and text of the email. Only emails that arrive after the trigger was turned on are reported. The check changes nothing in your mailbox, not even the read status. Without an agent with this trigger, the check does not take place. In an organisation, the organisation can block such triggers for the module.
4. Who receives the data
- the module's service on our server;
- Google, when an agent reads, searches, organises, drafts or sends emails;
- the language model of the runtime you have chosen, as a result or event, to the extent an agent needs the data for the task (privacy policy section 6). In the Nema runtime, these are the service providers we specify with each request, as our processors (sections 6.1, 15 and 16). In the Claude Code and Codex runtimes, it is Anthropic or OpenAI under your own contract (sections 6.2 to 6.4);
- the recipients of an email that an agent sends or replies to after you agree. Gmail delivers it and keeps it in Sent;
- other members and agents in the channel in which an agent uses the data;
- Apple's or Google's push service, to the extent the data appears in the first 180 characters of a message we send you as a notification (section 12);
- the data centre operator on whose hardware our server runs and where our backups are stored, as our processor (sections 17.6 and 20);
- authorities only if we are legally obliged to.
The module uses no other service providers.
Countries outside the EU: For users in the European Economic Area and Switzerland, Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) is responsible for the Google account; for Google Workspace accounts, your organisation's contract with Google also applies. Google also processes data in the USA; Google LLC is certified under the EU-US Data Privacy Framework (Art. 45 GDPR), supplemented by standard contractual clauses. For the service providers of the runtimes, section 16 of the privacy policy applies.
5. Storage and protection
- Credentials: We store the email address and app password encrypted (AES-GCM) in our database. The module receives them from our server with each call and does not store them itself. The app password only leaves our server to sign in to Gmail.
- Content: The module does not store any content from Gmail. It fetches it again with each request and only keeps it in memory while the request runs. What an agent makes of it, i.e. replies, reminders, knowledge entries, the steps of its run and the card for an email that triggered it, we store like other content (privacy policy sections 4 and 5).
- Trigger: For "New email", we remember for each connection up to which email in the inbox has been checked (a sequence number assigned by Gmail). So that the same email starts an agent only once, we also store the ids of reported emails for 90 days. We do not store the subject, sender or text for this.
- Transmission: The connection to Gmail (IMAP and SMTP) and between your apps and our server is encrypted with TLS.
- Pseudonymisation: In organisations that have turned on pseudonymisation, results of the module and emails that trigger an agent go to the language model pseudonymised, unless the organisation has turned this off for the module. For emails that trigger an agent, it can hide or replace individual fields with field masks, such as the sender and recipients. Both are off by default, and pseudonymisation has limits (privacy policy section 7).
6. Retention, disconnecting, revocation
- Disconnect: If you disconnect the module in the app, we immediately delete the email address and app password from our database. After that, no agent retrieves data from this mailbox any more. If an admin or owner connected the account for an organisation, only the organisation can disconnect it. The remembered ids for the trigger expire after 90 days.
- Revocation at Google: At https://myaccount.google.com/apppasswords you can delete the app password "Nema Crew" at any time. After that, nobody can sign in to Gmail with it any more, not even with the copy we hold. Disconnecting in the app does not delete the app password at Google. It remains there until you delete it yourself. We therefore recommend doing both.
- What remains: What an agent has taken from emails into messages, reminders or knowledge entries remains stored after disconnecting until you delete it (privacy policy section 17.1). Emails, drafts and labels that an agent has sent, created or changed remain in your Gmail account.
- Deleting your account: With your account, we immediately delete your credentials and content (privacy policy section 17.5). Accounts connected for an organisation remain until the organisation disconnects them or is deleted.
- Backups: The data, including the encrypted credentials, remains in our backups for up to about 6 months (privacy policy section 17.6).
7. Legal basis
Art. 6(1)(b) GDPR, because the module carries out the connection you set up. For third-party data in emails, such as senders and recipients, Art. 6(1)(f) GDPR applies, limited to the task you give the agent. In organisations, we process on behalf of the organisation (privacy policy section 2). Your confirmation of this notice is not consent. Anyone who wants to end the processing disconnects the module.
Documents
- This notice
- Data processing agreement
- Google privacy policy
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.