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 Outlook-Calendar 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 under its own responsibility and its privacy statement. If you have a work or school account, your organisation's contracts with Microsoft also apply.
2. What data the module processes
Permissions the module requests from Microsoft when connecting:
Calendars.ReadWrite: read your calendars and events and create, change and delete events in your calendars;User.Read: sign you in and read your Microsoft profile;offline_access: keep access without you having to sign in again for each call.
Until 27 October 2026 the module also requested Calendars.Read. Reading is included in Calendars.ReadWrite, so the module no longer requests it. For older connections it remains registered at Microsoft until you revoke the consent there (Section 6); the module does not use it beyond Calendars.ReadWrite.
Sign-in uses the general Microsoft sign-in, which knows personal Microsoft accounts and work or school accounts (Microsoft 365).
We only receive data that you allowed Microsoft to give us access to when connecting:
- when connecting, your Microsoft profile. The module only takes your sign-in address from it (user name or email address of the account);
- the list of your calendars with identifier, name, colour, whether it is your default calendar and whether you may edit it, and the email address of its owner;
- events with identifier, subject, start and end including time zone, location, organiser (name, email address), attendees (names, email addresses, response to the invitation), a text preview, your own response and whether it is an online meeting and whether the event was cancelled. If an agent fetches a single event, the full text of the event, the link to the online meeting and the recurrence rule are added;
- the availability of people whose email addresses an agent provides, including people other than you: a free/busy overview in 30-minute steps and the entries in that period with status, start, end and subject. What Microsoft discloses of this depends on the sharing settings of these people or their organisation.
The module does not create or delete calendars and does not change the sharing or settings of your calendars. It does not fetch attachments of events.
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 calendars, list events in a period, fetch single events, fetch open invitations and check the availability of people;
- writing: create events (with subject, time, time zone, text, location and attendees), change subject, time, text and location, delete events, and accept or decline invitations, with a comment if requested. Microsoft sends the response to an invitation to the organiser.
Trigger "New invitations": If you have set an agent to this trigger, we check every five minutes whether your calendar has invitations to events that have not ended yet and that you have not answered (up to 20 per query). We start the agent once with each invitation. It is reported again only if the invitation changes at Microsoft, for example because the organiser moves the time or place. 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 events;
- 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 people whom an agent adds as attendees of an event on your behalf, and to the organiser when an agent answers an invitation. What they see of it and which messages Microsoft sends them is governed by Outlook;
- to other members and agents in the 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 Outlook. It fetches it anew with each request. So that an invitation starts the trigger only once, our server remembers, for each reported invitation, its identifier and change key at Microsoft (no content) for 90 days. What an agent makes of it, meaning responses, memories, knowledge entries, the steps of its run and the card for an invitation 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 invitations that trigger an agent go to the language model pseudonymised, unless the organisation has switched this off for the module. For invitations that trigger an agent, the organisation can hide or replace individual fields with field masks, such as the names and email addresses of the organiser and attendees. 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. 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 calendar data into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Events an agent created or changed, and responses to invitations, stay in Outlook.
- 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 attendees and organisers of events and people whose availability an agent checks, 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.