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 Sentry 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.
Sentry (Functional Software, Inc.) is not the provider of this module. Sentry processes the data in your Sentry organization under its own responsibility and its privacy policy. If you run Sentry yourself, this applies to your own server.
2. What data the module processes
You connect the module in one of two ways:
- "Nema Crew" app (default): You install the public integration "Nema Crew" in your Sentry organization and confirm its permissions there. Sentry shows you which permission levels the integration requests before you install it; Sentry grants such rights per area (projects, teams, releases, issues and events, organization, members, alerts), at most up to read, write or admin. The module only uses reading the organization, projects, issues and events and changing issues (status, assignment).
- Own token: You enter the token of an Internal Integration of your Sentry organization, or an organization or personal token. You decide its rights in Sentry. Our instructions recommend
Project: Read,Issue & Event: Read(Read & Writefor resolving and assigning) andOrganization: Read. You also enter the short name of the organization, the region (US, EU or the address of a self-hosted Sentry) and, if you like, the Client Secret of the integration, which we use to check the signature of webhooks.
We only receive data that the permissions allow:
- when connecting via the app, the installation identifier, the short name and name of the organization and the address of its region;
- organizations with short name, name, identifier, status and creation date;
- projects with short name, name, identifier, platform, status, date of the first event and of creation;
- issues (grouped errors) with identifier, title, location of the error in the code, severity, status, number of occurrences and of affected users, first and last occurrence, project, assignee (name or email address), link and, in the detail view, the metadata and tags;
- events (single occurrences of an error) with identifier, time, title, message, platform, tags and contexts (such as device, browser, operating system and whatever your software sends), error type and text, the last 10 stack frames with file, function, line and an excerpt of the source code, the last 20 breadcrumbs (recorded steps before the error) and further parts of the event as Sentry stored them, such as the request (address, method, headers, cookies, parameters, body), and the name and version of the Sentry SDK;
- via webhooks, the events Sentry sends (Section 3), with the content Sentry provides for them: issues, error events, comments with their text and the person who commented, triggered alerts, and in each case who made the change.
Sentry stores what your organization's software reports. Depending on your setup in Sentry, events, tags, breadcrumbs and requests can therefore contain personal data of the users of your software, such as user identifiers, email addresses, IP addresses and usernames. The module does not filter them out.
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 rights of the connection:
- reading: check the connection, list organizations and projects, list issues and search them with Sentry's search syntax, read issues, their events and single events; with your own token, show the personal webhook address;
- writing: resolve, reopen or ignore an issue and assign it to a member or team or remove the assignment.
Triggers via webhooks: Sentry sends events of your organization to our server: issues created, resolved, assigned, archived or reopened, comments added, edited or deleted, on the Business and Enterprise plans every new occurrence of an error, and alerts from alert rules that send to "Nema Crew". Via the app this happens automatically; with your own token only if you enter the personal webhook address in Sentry. We use them to start the agents set to this trigger. Changes made by Nema Crew itself do not trigger an agent.
Trigger "New Sentry issues": If you have set an agent to this trigger, we check every five minutes whether there are new unresolved issues from the last 24 hours in your organization (up to 25 per query) and start the agent with them. Without an agent that uses this trigger, the query does not take place. In an organisation, the organisation can block triggers for the module.
4. Whom the data goes to
- to the module's service on our server;
- to Sentry, when an agent reads or writes there, and from Sentry to us for webhooks. With the app, signing in and renewing credentials go to sentry.io, data requests go to your organization's region (sentry.io or de.sentry.io). With your own token, all requests go to the region or the self-hosted server you entered;
- 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);
- to members or teams of your Sentry organization to whom an agent assigns an issue. Whether and how Sentry notifies them is governed by Sentry;
- 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: Sentry (Functional Software, Inc., USA) stores data in the USA or in Germany (Frankfurt), depending on your organization's region, but may also access it from the USA; Functional Software, Inc. is certified under the EU-US Data Privacy Framework (Art. 45 GDPR), and standard contractual clauses also apply (Art. 46 GDPR). The module addresses your organization's region; for a self-hosted Sentry the location depends on where it runs. For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the token, the Client Secret and, for the app, the access and refresh tokens encrypted (AES-GCM) in our database; renewed tokens likewise. Sentry issues the app's tokens for eight hours; we renew them automatically. The module receives the credentials from our server with each call. It additionally keeps renewed app tokens in memory until the module restarts, not on disk.
- Content: The module does not store content from Sentry. 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 event that triggered it, we store like other content (Privacy Policy Sections 4 and 5).
- Caches and state: We put incoming webhooks encrypted into our job queue until they are processed. After that they stay there for 7 days, undeliverable ones for 30 days, so that we recognise duplicate deliveries. For the trigger "New Sentry issues", the module keeps in memory up to when it has already reported issues and the identifiers of the last ones reported. This is lost on a restart.
- Transmission: The connection to Sentry and between your apps and our server is encrypted with TLS. We check webhooks of the app by their signature, and with your own token if you entered the Client Secret.
- 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. Pseudonymisation is recommended for this module because error reports can contain users' data; the organisation can switch it off for the module. It is off by default and has limits (Privacy Policy Section 7). There are no field masks for this module.
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 Sentry organization any more. If an Admin or Owner set up the connection for an organisation, only the organisation can disconnect it.
- Revoking at Sentry: An owner or manager of your Sentry organization can uninstall the "Nema Crew" app at any time under Settings → Integrations. Sentry tells us, and we delete the connections of this installation from our database. Disconnecting in the app does not uninstall the app at Sentry. It stays installed in your Sentry organization until you remove it there, and until then Sentry can keep sending events to our server. We therefore recommend doing both. You revoke your own token in Sentry, where you created it.
- What remains: What an agent has taken over from Sentry into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Status changes and assignments an agent made in Sentry stay there.
- Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5). Connections set up for an organisation remain until the organisation disconnects them or is deleted.
- Backups: The data, including the encrypted credentials, 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 users of your software in error reports and members of your Sentry organization, 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
- Sentry Privacy Policy
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.