Provider
Leonardo Antonio Carta (Nema)Controller
c/o Emperon Studio GmbH, Sachsenring 51a, 50677 Köln, Deutschland
This notice supplements the Privacy Policy for Nema Crew for the Microsoft Teams module. It does not repeat what the policy says for 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 provided 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.
Microsoft is not the provider of this module. Microsoft processes the data in your Microsoft account and in Teams under its own responsibility and its privacy statement.
2. What data the module processes
Permissions the module requests from Microsoft when connecting:
User.Read: read your own profile (the module uses your identifier, your name and the identifier of your organisation at Microsoft from it);Chat.ReadWrite: read your chats (one-on-one and group chats) and their messages, write messages in chats and mark chats as read;ChannelMessage.Send: write messages in channels of teams you are a member of;Team.ReadBasic.All: read the names and descriptions of your teams;Channel.ReadBasic.All: read the names and descriptions of the channels in your teams;User.ReadBasic.All: read the basic profile of other people in your organisation (identifier, name, first name and surname, email address);offline_access: renew access without you having to sign in again each time.
The module has requested these permissions unchanged since it started.
We only receive data that you allowed Microsoft to give us access to when connecting:
- teams with identifier, name and description;
- channels with identifier, name, description, type of channel (such as private or shared) and link in Teams;
- chats with identifier, type (one-on-one or group chat), topic, time of creation and the names of the members;
- messages from chats with identifier, sender (name, identifier), content, format, time and type of message;
- people in your organisation with identifier, name, first name and surname and email address (only this basic profile, no job title, no office location, no phone numbers);
- your own identifier and name at Microsoft, so that the trigger recognises your own messages, and the identifier of your organisation (tenant) at Microsoft, which Teams requires to mark a chat as read. The module reads the tenant identifier from the access token or, if it is missing there, from Microsoft.
When connecting, the module does not retrieve any further details about you. Only the credentials are stored (Section 5).
The module does not create teams, channels or chats, does not read messages from channels, does not delete messages and does not change memberships or settings.
3. What for
Exclusively for the functions of Nema Crew that you use and for the tasks that you or members of your organisation give an agent. The agent acts on your behalf with the permissions you granted Microsoft:
- reading: show teams and channels, list chats, read messages from chats, fetch the basic profile of a person and search for people by the beginning of their name or email address (up to 20 results);
- writing: send messages to a chat or a channel and mark chats as read;
- references: If you type a reference to a team, a channel (
#) or a person (@) in Nema Crew, the module asks Microsoft at that moment for matching entries (names, for people also the email address) and shows them for selection.
Trigger "New chat messages": If you have set an agent to this trigger, we check your 10 most recently active chats every five minutes and fetch the 5 newest messages from each. We leave out your own messages, system messages and messages older than two days. We start the agent once with each remaining message; the same message does not trigger a second run. Afterwards we mark the chat as read in Teams. This only works for work or school accounts; with a personal Microsoft account, or if Microsoft refuses it for a chat, the chat stays unread and we record the error in the module's log. Without an agent that uses this trigger, the query does not take place. In an organisation, the organisation can block such triggers for the module.
4. Whom the data goes to
- to the module's service on our server;
- to Microsoft, when an agent reads or writes in Teams;
- as a result or event to the language model of the runtime you chose, 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 these are Anthropic or OpenAI under your own contract (Sections 6.2 to 6.4);
- to the members of the chat or channel in which an agent writes a message on your behalf. They see the message under your name. Whether and how Microsoft notifies them is governed by Teams;
- to other members and agents in the Nema Crew channel in which an agent uses the data;
- to Apple's or Google's push service, to the extent the data is in the first 180 characters of a message we send you as a notification (Section 12);
- to the data centre operator on whose hardware our server runs and where our backups are kept, as our processor (Sections 17.6 and 20);
- to authorities only if we are legally obliged to.
The module uses no further service providers.
Countries outside the EU: For personal Microsoft accounts, Microsoft Ireland Operations Limited (Dublin, Ireland) is responsible; for work or school accounts, Microsoft processes the data as your organisation's processor under its contract with Microsoft. Microsoft also processes data in the USA; Microsoft Corporation is certified under the EU-US Data Privacy Framework (Art. 45 GDPR), supplemented by standard contractual clauses. For work or school accounts of organisations from the EU or EFTA, Microsoft generally stores and processes the data within the EU Data Boundary, with the exceptions Microsoft lists. For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the OAuth tokens encrypted (AES-GCM) in our database; renewed tokens likewise. The module receives them from our server with each call and does not store them itself.
- Content: The module does not store content from Teams, including the results for references. It fetches it anew with each request. So that a message starts the trigger only once, our server remembers the identifier of each reported message (identifiers of chat and message, no content) for 7 days. What an agent makes of it, meaning responses, memories, knowledge entries, the steps of its run and the card for a message that triggered it, we store like other content (Privacy Policy Sections 4 and 5).
- Transmission: The connection to Microsoft and between your apps and our server is encrypted with TLS.
- Pseudonymisation: In organisations that have switched on pseudonymisation, the module's results and the messages that trigger an agent go to the language model pseudonymised, unless the organisation has switched this off for the module. For messages that trigger an agent, the organisation can hide or replace individual fields with field masks, namely the sender (name and identifier), chat topic and message text. Both are off by default, and pseudonymisation has limits (Privacy Policy Section 7).
6. Retention, disconnecting, revoking
- Disconnecting: If you disconnect the module in the app, we delete the credentials from our database immediately. After that, no agent retrieves data from this Microsoft account any more. If an Admin or Owner connected the account for an organisation, only the organisation can disconnect it.
- Revoking access at Microsoft: For a personal Microsoft account you can withdraw Nema Crew's access at any time at https://account.live.com/consent/Manage, for a work or school account at https://myapps.microsoft.com or through your organisation's administration. If an administrator granted the authorisation for the whole organisation, only the administration can revoke it. The tokens stored with us then become invalid. We remove them from our database when you disconnect in the app or delete your account. Disconnecting in the app does not revoke the authorisation at Microsoft. It remains there until you revoke it yourself. We therefore recommend doing both.
- What remains: What an agent has taken over from Teams data into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Messages an agent wrote in Teams stay in Teams.
- 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 tokens, 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 parties' data, such as messages, names and contact details of colleagues and other chat participants, Art. 6(1)(f) GDPR applies, limited to the task you give the agent. In organisations we process on their behalf (Privacy Policy Section 2). Your confirmation of this notice is not consent. To end the processing, disconnect the module.
Documents
- This notice
- Data Processing Agreement
- Microsoft Privacy Statement
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.