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 Drive 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:
drive.file: access only to files that Nema Crew created itself or that you explicitly opened or selected for Nema Crew;userinfo.email: read the email address of your Google account.
Nema Crew currently offers no way to select existing files for Nema Crew. Only files and folders that Nema Crew created are therefore accessible, including copies an agent makes. Nema Crew has no access to any other file in your Drive.
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;
- for each file Nema Crew may see: identifier, name, type, size, description, folder, link, whether it is shared, whether it is in the trash, the times of creation and last change, and the owners and last editor (names, email addresses);
- the people and groups a file is shared with (names, email addresses, domain, role), when an agent asks for them;
- the content of a file when an agent reads it: Google Docs and presentations as text, spreadsheets as CSV (first sheet) or in another format the agent chooses, other files up to 5 MB, text up to 200,000 characters.
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: list the files Nema Crew may see, search them by name and content, fetch the most recently changed ones, get details of a file, read files and export them to another format, show who has access;
- writing: create files and folders, also as a Google Doc, spreadsheet or presentation, upload files up to 5 MB, rename files, change their description or content, copy, move and move them to the trash;
- sharing: share a file with a person with read, comment or edit rights, or with anyone who has the link. When a file is shared with a person, Google sends that person a notification by default, with a message from the agent if requested.
The module has no triggers. An agent only accesses Google Drive when a task requires it.
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 files;
- as a result 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 with whom an agent shares a file on your behalf and, for sharing by link, to anyone who knows the link. What they see is governed by Google Drive;
- 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 any files or content from Google Drive. It fetches them anew with each request. What an agent makes of it, meaning responses, memories, knowledge entries and the steps of its run, 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 go to the language model pseudonymised, unless the organisation has switched this off for the module. This is off by default, and pseudonymisation has limits (Privacy Policy Section 7). There are no field masks for this module because it delivers no events.
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 files into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Files an agent created or changed in your Drive stay there, as do shares it granted. After disconnecting, Nema Crew no longer has access to these files.
- 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 files and shares, such as owners, editors and people with access, 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.