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 Google 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.
Google is not the provider of this module. Google processes the data in your Google account under its own responsibility and its privacy policy.
2. What data the module processes
Permissions the module requests from Google when connecting:
calendar.events: read, create, change and delete events;calendar.calendarlist.readonly: read the list of your calendars;userinfo.email: read the email address of your Google account.
The module does not create or delete calendars and does not change the sharing or settings of your calendars.
If you connected the module before these permissions applied, you also granted Google the broad calendar access. The module only uses the access listed above. To get rid of the broad access, disconnect the module, revoke access at Google (Section 6) and connect it again.
We only receive data that you allowed Google to give us access to when connecting:
- when connecting, the email address of the connected Google account;
- the list of your calendars with identifier, name, description, time zone, colour, your access level and whether it is your primary calendar;
- events with identifier, title, description, start and end, location, status, organiser (name, email address), attendees (names, email addresses, response to the invitation), link to the event in Google Calendar and the times at which the event was created and last changed.
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 Google:
- reading: show calendars and events, list events in a period, search by text and fetch upcoming events;
- writing: create events, also from a short text such as "Lunch with Anna tomorrow at 12", change and delete events, add attendees, and accept, decline or answer "maybe" to invitations.
Trigger "Upcoming events": If you have set an agent to this trigger, we check every five minutes whether an event in your primary calendar starts within the next 30 minutes (up to 10 events per query). We then start the agent with that event. 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.
We do not use data from Google APIs for advertising, including personalised or interest-based advertising. We do not build profiles from it for other purposes, do not sell it, do not pass it on to data brokers or information resellers and do not use it to determine creditworthiness or for lending purposes.
4. Whom the data goes to
- to the module's service on our server;
- to Google, 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. What they see of it and whether Google notifies them is governed by Google Calendar;
- 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.
Beyond this, we do not pass on data from Google APIs. The module uses no further 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 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 Google Calendar. It fetches it anew with each request. What an agent makes of it, meaning responses, memories, knowledge entries, the steps of its run and the card for an event that triggered it, we store like other content (Privacy Policy Sections 4 and 5).
- Transmission: The connection to Google 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 events that trigger an agent go to the language model pseudonymised, unless the organisation has switched this off for the module. For events 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 Google account any more. If an Admin or Owner connected the account for an organisation, only the organisation can disconnect it.
- Revoking access at Google: At https://myaccount.google.com/permissions you can withdraw Nema Crew's access at any time. 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 Google. 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 stay in your Google Calendar.
- 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 in events, such as attendees and organisers, 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.
8. Requirements of Google
Limited Use: Nema Crew's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
No training of AI models: We do not use data from Google APIs to develop, improve or train generalised AI or ML models, including in anonymised or aggregated form, and do not pass it on so that others can do so. In the Nema runtime, this data is only sent for processing to the operators we specify with each request. Only operators that neither store the requests nor use them for training are permitted (Privacy Policy Section 6.1). If you use the Claude Code or Codex runtimes with your own subscription, data from Google APIs that is in the conversation context also goes to Anthropic or OpenAI. They process it on the basis of your own contract. Whether they use your requests for their models depends on that contract and your settings there (Privacy Policy Section 6.4).
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.