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 Notion 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.
Notion is not the provider of this module. Notion processes the data in your workspace under its own responsibility and its privacy policy.
2. What data the module processes
Permissions: Notion has no individual scopes. What the "Nema Crew" integration may do is set at Notion for the integration:
- read content: search and read pages and databases, receive notifications about changes;
- update content: change page titles, move pages to the trash;
- insert content: create pages and database entries, append content to pages;
- read comments: receive notifications about comments;
- read user information: show the names of the workspace members.
This is how the integration's guide describes them. The capabilities are set at Notion, not in the module's code; the module uses at most those listed. Depending on the user information setting, Notion also returns email addresses for people. When listing members, the module does not pass on email addresses; they may be contained in properties of pages and database entries (see below).
Which pages: When connecting, you choose in Notion the workspace and the pages Nema Crew may access. Nema Crew only sees these pages with their sub-pages and the databases in them. Nema Crew has no access to any other page in your workspace. You can change the selection in Notion at any time.
We only receive data that you allowed Notion to give us access to when connecting:
- when connecting, the identifier and name of the workspace and the identifier of your Notion user. Notion also sends further details of your Notion account; we do not store them;
- for pages and database entries: identifier, title, link, times of creation and last change, whether they are in the trash, and all properties as Notion delivers them. These can include people (such as assignees, creators or last editors, with names and, where applicable, email addresses) and anything that is in your databases;
- the content of a page when an agent reads it: the blocks with identifier, type and text, up to 100 blocks per retrieval;
- for databases: identifier, title, link, time of creation and the structure (names and types of the columns);
- the members of the workspace: identifier, name, type (person or bot) and link to the profile picture;
- events from Notion (Section 3): type of event, time, identifier and name of the workspace, identifier of the affected page, database, data source or comment, of the parent page and the identifiers of the people who made the change or have access. The events do not contain the text of a comment or a page.
The module cannot read or write comments. It only reports that a comment was written, changed or deleted.
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 Notion:
- reading: search pages and databases, read pages with their properties and their content, list databases, read their structure and retrieve their entries, list the members of the workspace;
- writing: create pages, also with text, change page titles, move pages to the trash, append text to a page, create entries in a database.
When you select a page or database in the app to refer to it, the module searches the titles in Notion for this.
Trigger "Events from Notion": Notion notifies our server when pages, databases or data sources are created, changed, moved, locked, unlocked, deleted or restored, and when a comment is written, changed or deleted. By the workspace identifier we find the accounts in Nema Crew that have connected this workspace. For each of these accounts the module asks Notion, with that account's access token, whether the connection may see the affected page, database or data source (for comments: the page the comment belongs to). Only then do we assign the event to the account. If Notion says no or does not answer, the event does not go to that account. This way an event about a page that only another account has shared does not reach your agents. If an assigned account has set an agent to this event, we start the agent with the event. We skip events that you triggered yourself. Without an agent that uses this trigger, nothing happens. 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 Notion, when an agent reads or writes there;
- 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 who have access to the pages in the workspace, when an agent creates or changes something there. Who sees what is governed by Notion;
- 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: Notion (Notion Labs, Inc., USA) processes data in the USA and other countries on the basis of standard contractual clauses (Art. 46 GDPR); Notion Labs, Inc. is also listed as a participant in the EU-US Data Privacy Framework (Art. 45 GDPR). For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the Notion access token encrypted (AES-GCM) in our database, together with the identifier and name of the workspace and the identifier of your Notion user. The module receives the token from our server with each call and does not store it itself.
- Content: The module does not store content from Notion. 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).
- Caches and state: We put incoming events into a queue on our server. We delete processed events there after 7 days, and those that could not be processed after 30 days. By the event's identifier we recognise when Notion sends the same event again. Notion's answer as to whether an account may see a page (Section 3) we keep as yes or no together with your account, the workspace identifier and the identifier of the page, database or data source: a yes for 5 minutes, a no for 1 minute. We do not store any content in doing so.
- Transmission: The connection to Notion and between your apps and our server is encrypted with TLS. We only accept events that demonstrably come from Notion (Notion's signature or a secret, personal address).
- 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, the organisation can hide or replace individual fields with field masks, such as the authors' identifiers and the workspace name. 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 workspace any more, and we no longer assign events from Notion to your account. If an Admin or Owner connected the workspace for an organisation, only the organisation can disconnect it.
- Revoking access at Notion: In Notion under Settings → Connections you can withdraw Nema Crew's access at any time or change the shared pages. The token stored with us then becomes invalid. We remove it from our database when you disconnect in the app or delete your account. Disconnecting in the app does not revoke the access at Notion. It remains there until you revoke it yourself. We therefore recommend doing both.
- What remains: What an agent has taken over from Notion into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Pages and entries an agent created or changed in Notion stay there.
- Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5). Workspaces connected for an organisation remain connected until the organisation disconnects them or is deleted.
- Backups: The data, including the encrypted token, 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 workspace members and people in pages and databases, 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
- Notion Privacy Policy
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.