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 Shopify 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.
Shopify is not the provider of this module. Shopify processes your store's data under its own responsibility, its privacy policy and your contract with Shopify.
2. What data the module processes
Credentials you enter when setting up:
- your store address (my-store.myshopify.com);
- the client ID and client secret of your own app in the Shopify Dev Dashboard. With them the module obtains an access token from Shopify that is valid for 24 hours;
- or, only for older custom apps created in the store admin, their Admin API access token (
shpat_…).
You set the permissions yourself in your app at Shopify. The module is built for these:
read_orders,read_customers,read_products,read_inventory: read orders, customers, products and stock;write_orders,write_customers,write_products: append notes to orders and add tags;- optionally
read_all_orders(orders older than 60 days) andread_shopify_payments_disputes(chargebacks); - for customers' names and email addresses, additionally access to protected customer data. Without it, the module returns orders without this information.
The module only uses the access its functions below need. If you grant your app further permissions, the module does not use them.
We only receive data that your app is enabled for at Shopify:
- store: name, myshopify address, address of the online store, currency, time zone and plan;
- orders: identifier and number, times, payment and fulfilment status, amounts (total, subtotal, shipping, taxes, refunds), tags, sales channel, test flag, cancellation and reason, internal note, link to the customer's status page, the customer's email address and name, shipping address (name, company, street, postal code, town, country, phone number), line items (title, variant, SKU, quantity, price) and fulfilments with carrier, tracking number and link;
- customers: identifier, name, email address, phone number, address (company, street, postal code, town, country), number of orders, amount spent, state of the customer account, tags, internal note, time of creation and the five latest orders;
- products and stock: title, description, status, vendor, type, prices, tags, links, variants with SKU, barcode and stock;
- events (if you set up webhooks): the data Shopify sends about a new, paid, cancelled or fulfilled order, a refund, a new customer or a chargeback. Shopify sends this message in full; it contains, for example, the whole order with customer data and addresses, or for chargebacks the amount, reason and deadline for evidence.
The module does not issue refunds or cancellations and does not change prices or stock.
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:
- reading: check the store; list, search and retrieve orders; add up sales for a period; list, search and retrieve customers; list and retrieve products; find items with low stock;
- writing, each only after a preview and with explicit confirmation (
confirm): append an internal note to an order (existing notes stay; only your team sees the note, not the customer), add tags to orders, customers or products, and set up webhooks at Shopify that send events to your personal Nema address.
Triggers:
- Webhooks: If an agent has set up the webhooks, Shopify immediately sends a message to our server for new, paid, cancelled and fulfilled orders, refunds, new customers and chargebacks. We then start the agent that is set to this event.
- "New orders": If you have set an agent to this trigger, we ask Shopify every five minutes for the orders received since the last query (up to 25 per query) and start the agent for each order.
Without an agent that uses a trigger, no query takes place. 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 Shopify (your store's admin interface at my-store.myshopify.com) when an agent reads or writes, and from Shopify to our server if webhooks are set up;
- 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 store team, who see notes and tags an agent created in the Shopify admin;
- to other members and agents in the channel in which an agent uses the data, and to the people an agent replies to on your behalf;
- 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).
The module uses no further service providers.
Countries outside the EU: According to Shopify's privacy policy, the contracting party for merchants in Europe is Shopify International Limited (Dublin, Ireland). Shopify also processes data in Canada and the USA on the basis of Shopify's binding corporate rules (Art. 47 GDPR) and, for service providers, standard contractual clauses (Art. 46 GDPR); an adequacy decision applies to Canada (Art. 45 GDPR). Shopify is not certified under the EU-US Data Privacy Framework. For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the store address, client ID, client secret or access token encrypted (AES-GCM) in our database. Next to them is the personal identifier of your webhook address, a random value we use to match incoming messages from Shopify to your connection. The module receives the credentials from our server with each call. It keeps the access token obtained from Shopify in memory for up to 24 hours, not on disk.
- Content: The module does not store content from Shopify. 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: For the "New orders" trigger, the module keeps in memory, per user, the time of the last reported order and its identifiers; this is lost when the module restarts. Incoming webhook messages are kept with their content in our job queue and deleted 7 days after processing, those that cannot be processed after 30 days.
- Transmission: The connection to Shopify 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 customer's name, email address and phone number, recipient and shipping address, order notes and the reason for a chargeback. 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 and the identifier of your webhook address from our database immediately. After that, no agent retrieves data from this store any more, and we no longer accept webhook messages to the old address. If an Admin or Owner connected the store for an organisation, only the organisation can disconnect it.
- Revoking at Shopify: Disconnecting in the app does not delete the webhook subscriptions at Shopify and does not uninstall your app. Both remain until you do it yourself: uninstall the app in the Shopify admin or regenerate the client secret in the Dev Dashboard. We therefore recommend doing both.
- What remains: What an agent has taken over from store data into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Notes and tags an agent created stay in your store.
- Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5). Stores connected 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 your customers' data, such as names, contact details, addresses and orders, 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
- Shopify Privacy Policy
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.