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 Stripe 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.
Stripe is not the provider of this module. Stripe processes the data in your Stripe account under your contract with Stripe and its privacy policy.
2. What data the module processes
Credentials you enter when setting up: a restricted API key (rk_live_… or rk_test_…) from your Stripe Dashboard; for trying it out the module also accepts a test key (sk_test_…). It refuses live keys with full access (sk_live_…). You set the key's permissions in Stripe. The setup guide recommends:
- Read: Customers, PaymentIntents, Charges, Refunds, Subscriptions, Invoices, Products, Prices, Payment Links, Disputes, Payouts, Balance, Events, to read customers, payments, subscriptions, invoices, catalogue, disputes, payouts, balance and events;
- Write on Customers, Products, Prices, Payment Links and Invoices, only if agents are to create customers, payment links and invoices;
- Write on Webhook Endpoints, only for instant events;
- optionally Read on Connect → Account, to show the account name.
When checking the connection, the module retrieves the details of your Stripe account (identifier, name, country, default currency, the account's email address, whether charges and payouts are enabled), or otherwise the balance.
We only receive data your key is allowed to read. The module passes on to the agent:
- customers with identifier, name, email address, phone number, address, description, creation date, currency, balance, delinquency and metadata; for a single customer also their latest subscriptions, invoices and payments;
- payments with amount, status, customer, description, receipt email address, payment method types (the type, not the card details), the reason for declined payments, refunds, receipt link, invoice and metadata; refunds with amount, status and reason;
- subscriptions with status, customer, prices, quantities, period, cancellation, trial and metadata;
- invoices with number, status, customer name and email address, amounts, due date, description, links to the payment page and the PDF, subscription and payment attempts, on request with the line items;
- products, prices and payment links;
- disputes (chargebacks) with amount, status, reason and the deadline for evidence;
- payouts to your bank account with amount, status, arrival date, method, statement description and failure reason, and your balance;
- events from Stripe (type, time, affected object, customer, amount, status, description, changed fields).
Events via the webhook go to the agent as Stripe sends them: with the complete object and all fields Stripe includes, for example the customer details of a checkout (name, email address, phone number, address) and the billing details and payment method details of a payment.
The module never refunds, never pays out, does not cancel subscriptions and does not delete anything in Stripe.
3. What for
Exclusively for the tasks that you or members of your organisation give an agent. The agent acts with the permissions of your key:
- reading: check the account and balance; list, search and read customers; list or read payments, refunds, subscriptions, invoices, products, prices, payment links, disputes, payouts and events;
- writing, each only after a preview and only when the agent explicitly confirms (
confirm: true): create a customer (with email address, name, phone, description, language); create a payment link, with a product and price if needed; create a draft invoice; finalise an invoice; email an invoice to the customer (Stripe sends it); set up or change the webhook in Stripe.
Triggers:
- Instant events (webhook): If an agent has set up the webhook, Stripe sends the selected events to your personal address with us: payment succeeded or failed, checkout completed, payment refunded, dispute opened or closed, early fraud warning, new customer, subscription started, changed, ended or trial ending soon, invoice paid, payment failed, overdue or upcoming, payout arrived or failed.
- Regular query "New Stripe activity": If you have set an agent to this trigger, we check every five minutes whether there are new events of these types in Stripe (up to 25 per query) and start the agent with each new event. 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 Stripe (api.stripe.com) when an agent reads or creates something; from Stripe to our server if you have set up the webhook;
- 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 your customers when an agent sends an invoice or passes on a payment link on your behalf. Stripe sends the invoice;
- to other members and agents in the channel in which an agent uses the data;
- 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).
The module uses no further service providers.
Countries outside the EU: According to Stripe, the contracting party for Stripe accounts in the EEA is Stripe Payments Europe, Limited (Ireland). Stripe also processes data in the USA and India; Stripe is certified under the EU-US Data Privacy Framework (Art. 45 GDPR) and also uses standard contractual clauses (Art. 46 GDPR). As an independent controller, Stripe, according to its privacy policy, also uses data to train machine learning models, for example for fraud prevention; what applies to this and which choices you have are governed by Stripe's own terms and its privacy policy. For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the API key encrypted (AES-GCM) in our database. The module receives it from our server with each call and does not store it itself. For the webhook, each connection gets a personal address with its own token; we neither need nor store Stripe's signing secret.
- Content: The module does not store content from Stripe. It fetches it anew with each request. Events that trigger an agent and what an agent makes of them, meaning responses, memories, knowledge entries, the steps of its run and the card for the event, we store like other content (Privacy Policy Sections 4 and 5).
- Caches and state: For the regular query, the module keeps in memory, per connection, up to which point in time it has already reported events and the identifiers of the reported events. This is lost when the module restarts; the query then starts again from "now". Events Stripe sends via the webhook are kept as jobs in our queue and deleted 7 days after processing, failed ones after 30 days.
- Transmission: The connection to Stripe 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 customers' names, email addresses, phone numbers and addresses, billing details and receipt email addresses. 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 key and the personal webhook address from our database immediately. After that, no agent accesses your Stripe account any more, and we no longer accept events sent to the old address. If an Admin or Owner set up the module for an organisation, only the organisation can disconnect it.
- Revoking at Stripe: You manage the key yourself in the Stripe Dashboard (Developers → API keys). Disconnecting in the app only deletes it with us; at Stripe it stays valid until you delete or roll it there. The module also does not remove a webhook endpoint it set up when you disconnect; delete it in the Stripe Dashboard under Developers → Webhooks. We recommend doing both.
- What remains: What an agent has taken over from Stripe data into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Customers, payment links, products, prices, invoices and webhooks an agent created stay in your Stripe account. The module marks customers, payment links, products, prices and invoices there with
created_by: nema. - Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5). Modules set up for an organisation remain until the organisation disconnects them or is deleted.
- Backups: The data, including the encrypted key, 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 your customers' data in customer records, payments and invoices, 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
- Stripe Privacy Policy
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.