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 GitHub 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.
GitHub is not the provider of this module. GitHub processes the data in your GitHub account under its own responsibility and its privacy statement.
2. What data the module processes
The module connects through the Nema Crew GitHub App. You connect your GitHub account (sign-in at GitHub), and in an organisation an Admin or Owner installs the app in the GitHub organisation and selects the repositories.
Permissions the GitHub App requests (as configured at GitHub): read and write access to contents (contents, code and files), issues (issues), pull requests (pull_requests), Actions (actions), workflow files (workflows), deployments (deployments), commit statuses (statuses), packages (packages), GitHub Pages (pages), merge queues (merge_queues) and repository webhooks (repository_hooks), administration of repository projects (repository_projects, admin), read and write access to repository administration (administration, used only for deploy keys) and to the SSH keys of your GitHub account (git_ssh_keys, account permission), read access to repository metadata (metadata) and to the members of an organisation (members). These permissions are broader than the module's tools need today (Section 3); the module only uses what is listed there. When you sign in, we also receive your public GitHub profile. GitHub only lets such an app access repositories in which it is installed and to which you yourself have access, plus public information such as public profiles and repositories.
We only receive data that you or your organisation allowed GitHub to give us access to:
- when connecting, your GitHub username, your GitHub ID and the address of your profile picture;
- repositories with name, description, visibility, branches and settings;
- issues and pull requests with number, title, text, status, labels, milestone, times, author and assignees (GitHub usernames), comments and reviews including their authors;
- commits with message, changed files and time, and author and committer (name, email address, GitHub username);
- the content of files in the repositories when an agent reads them, and entire repositories when an agent clones one;
- GitHub Actions workflows and workflow runs with status, jobs and the last lines of their logs (up to 200 lines per job by default);
- SSH keys when an agent lists, adds or removes them: the public keys on your GitHub account and the deploy keys of a repository with ID, title, type, fingerprint, access (read-only or read and write) and times. The module does not accept private keys;
- profiles of GitHub users when an agent fetches or searches for them: username, name, public email address, bio, company, location, website, X username, profile picture, number of followers and public repositories;
- events that GitHub sends to Nema Crew (Section 3), with the full content GitHub includes, such as titles and texts, comments, commits with the names and email addresses of their authors, and the GitHub usernames of the people involved.
Repositories often also contain third parties' data, such as names and email addresses in commits, comments and files. The module sees them to the extent they are in the retrieved content.
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 GitHub:
- reading: show repositories, branches, commits and files, read issues, pull requests and their comments, search repositories, issues and users, read workflows, runs and logs, fetch profiles of GitHub users. When you mention something in the app, Nema Crew suggests repositories and GitHub usernames from your account;
- writing: create repositories (private by default; public only if the agent explicitly specifies it), create and change issues, open, review (including approving or requesting changes) and merge pull requests, write, change and delete comments, create and delete branches, create, change and delete files;
- workflows: start, cancel and re-run GitHub Actions workflows;
- SSH keys: list, add and remove public SSH keys on your GitHub account or as deploy key of a repository (deploy keys read-only by default; write access only if the agent explicitly specifies it);
- cloning: copy a repository into the agent's workspace on our server.
What you have an agent write is visible to everyone with access to the repository, and for public repositories to everyone.
Trigger "Events": GitHub sends Nema Crew events from the repositories in which the app is installed, for example on issues, pull requests, reviews, comments, pushes, branches and tags, releases, workflow runs, deployments, labels, milestones, wiki pages, forks and stars. The events subscribed at GitHub are commit_comment, create, delete, deployment, deployment_protection_rule, deployment_review, deployment_status, deploy_key, fork, gollum, issues, issue_comment, label, merge_group, merge_queue_entry, milestone, page_build, public, pull_request, pull_request_review, pull_request_review_comment, pull_request_review_thread, push, registry_package, release, repository, repository_dispatch, star, status, sub_issues, watch, workflow_dispatch, workflow_job and workflow_run. We assign an event to the Nema Crew users it concerns, for example because they are mentioned, assigned or asked for a review. Your own actions do not trigger anything. An event only starts an agent that you or your organisation have set to that event. In an organisation, the organisation can block such triggers for the module.
Agents' SSH keys: Each agent has its own SSH key so that it can work with Git in its workspace. If you set this up in the app, we use your GitHub connection to add the public part of the key to your GitHub account or as a deploy key of a repository (read-only if you wish). The agent can then access everything the key is allowed to access there. An agent can also add or remove a public key itself through the module's tools; the tool first shows a preview and only writes after confirmation, and what an agent may do is decided in Nema Crew. A key on the account allows everything your GitHub account may do over SSH; a deploy key only applies to one repository.
4. Whom the data goes to
- to the module's service on our server;
- to GitHub, when an agent reads or writes there, and when we or an agent add or remove an SSH key;
- 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 everyone with access to a repository, for what an agent writes there on your behalf, and for public repositories to everyone. Whom GitHub notifies is governed by GitHub;
- 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: GitHub also processes data in the USA; GitHub is certified under the EU-US Data Privacy Framework (Art. 45 GDPR) and also uses standard contractual clauses (Art. 46 GDPR). For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the OAuth tokens and your GitHub username encrypted (AES-GCM) in our database. We renew the tokens regularly at GitHub and store the new ones likewise. The module receives them from our server with each call and does not store them itself. For an installation for an organisation, we store the installation's ID encrypted as well.
- SSH keys: We store the private part of an agent's key encrypted in our database. It only leaves the server for one run of the agent and is deleted again afterwards. We keep a record of where the public part has been added.
- Content: The module does not store content from GitHub. It fetches it anew with each request. When cloning, the agent uses the module's access; the clone is kept in the agent's workshop (its workspace) on our server until it is deleted. Disconnecting the module does not remove it. What an agent makes of the data, 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: Incoming events are kept with their content in our queue until they are processed, and for 7 days afterwards, or 30 days if processing fails. This lets us detect duplicate deliveries.
- Transmission: The connection to GitHub 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, the organisation can hide or replace individual fields with field masks, such as the GitHub usernames of the person who triggered the event and of authors, titles and texts of issues, pull requests and comments, and names and email addresses of commit authors. 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 GitHub account any more. If an Admin or Owner connected GitHub for an organisation, only the organisation can disconnect it. If the organisation removes the module, we delete its credentials and ask GitHub to uninstall the GitHub App from the organisation. If you uninstall the app directly at GitHub, the connection remains in the app but can no longer access the repositories; in that case also disconnect it in the app.
- SSH keys when disconnecting: Agents' SSH keys that were added stay at GitHub when you disconnect, and an agent can still use them to access Git. Remove them in the app at the agent while GitHub is still connected, or at GitHub under Settings → SSH and GPG keys or in the repository's deploy keys. If you delete an agent, we remove its keys at GitHub, as far as the connection still allows.
- Revoking access at GitHub: Under Settings → Applications → Authorized GitHub Apps you can withdraw Nema Crew's access at any time. The tokens stored with us then become invalid. You remove an installation of the app under Settings → Applications → Installed GitHub Apps (in the organisation under Settings → GitHub Apps). We remove them from our database when you disconnect in the app or delete your account. Disconnecting a personal connection in the app does not revoke the authorisation at GitHub. It remains there until you revoke it yourself. We therefore recommend doing both.
- What remains: What an agent has taken over from GitHub into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). What an agent created or changed at GitHub, meaning repositories, issues, pull requests, comments, commits and branches, stays there.
- Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5), and beforehand we try to remove your agents' SSH keys at GitHub. Accounts connected for an organisation remain until the organisation disconnects them or is deleted.
- Backups: The data, including the encrypted tokens and keys, 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 repositories, issues, pull requests, comments, commits and events, such as authors, assignees and other people involved, 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
- GitHub Privacy Statement
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.