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 Lexware Office 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.
Lexware Office is not part of this module. Lexware Office is operated by Haufe Service Center GmbH, Freiburg, Germany. It processes the data in your Lexware Office account under your own contract with it and its privacy policy.
2. What data the module processes
Credentials: the API key of the Public API, which you create in Lexware Office under "Erweiterungen → Public API" and enter when setting up. Lexware does not grant individual permissions for it: the key can read and write all sales vouchers and contacts in your account. The module only uses the access listed below. In addition, our server creates a personal webhook address with a token for your connection.
When setting up and for "Test connection", the module retrieves your account's profile: company name, organisation identifier, tax type, small business yes/no, booked features and subscription status.
Further data the module retrieves and passes on to the agent:
- contacts (customers and vendors) with identifier, company name or first and last name, customer and vendor number, email addresses, phone numbers, addresses, VAT ID, tax number, contact persons (name, email address, phone number), note and link;
- vouchers from the voucher list (invoices, quotations, credit notes, order confirmations, delivery notes, down payment invoices and further voucher types such as purchase invoices) with identifier, type, number, status, date, due date, contact name, total amount, open amount, time of last change and link;
- invoices and quotations in detail, additionally with title, recipient (name, postal code, town, country), line items (name, quantity, unit, price, tax rate, amount), net, tax and gross amount, payment terms, introduction and closing text;
- the payment status of a voucher with the open amount and the payments (type, posting date, amount);
- articles with name, number, type, unit, prices and tax rate.
The module does not finalise invoices, does not send vouchers, does not record payments and does not delete anything.
3. What for
Exclusively for the tasks that you or members of your organisation give an agent:
- reading: check the profile, search and read contacts, list vouchers, compile open and overdue invoices, read invoices and quotations, check the payment status, list articles;
- writing, only after confirmation: create contacts (the module first searches for similar contacts), create drafts of invoices and quotations, and set up event subscriptions at Lexware. Without explicit confirmation (
confirm) the module only shows a preview. Finalising and sending stays with a person in Lexware Office.
Trigger "event subscriptions": If an agent sets them up after your confirmation, Lexware Office notifies your personal address on our server when invoices, quotations, credit notes, dunning letters, contacts, payments or vouchers are created or changed. Lexware only sends identifiers (organisation, type of event, identifier of the voucher or contact, time). The agent then retrieves the voucher itself.
Trigger "invoice changes": If you have set an agent to this trigger, we check every ten minutes which invoices were created or changed since the last query (up to 25 per query) and start the agent with the invoice summary. 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 Lexware Office (interface at api.lexware.io) when an agent reads or writes there, and from Lexware to our server if event subscriptions 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 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 its own information, Lexware Office (Haufe Service Center GmbH, Freiburg) processes the data in the EU; only individual service providers (e.g. for support) are located in the USA, on the basis of an adequacy decision or standard contractual clauses (Arts. 45, 46 GDPR). 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.
- Content: The module does not store content from Lexware Office. 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 "invoice changes" trigger, the module keeps in memory up to which point in time it has already reported invoices, and the identifiers of the most recently reported invoices. To stay within two calls per second, it keeps the time of the last call per key, under the last 12 characters of the key. Both are lost when the module restarts. Incoming events from Lexware are kept as jobs in our queue and deleted 7 days after processing, failed ones after 30 days.
- Transmission: The connection to Lexware Office and between your apps and our server is encrypted with TLS. We only accept events that are sent to your personal address and carry Lexware's signature (RSA, checked with Lexware's public key). We reject events without a signature or with a wrong one and do not store them.
- 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 invoice changes, the organisation can hide or replace individual fields with field masks, such as the customer's 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 and the personal webhook address from our database immediately. After that, no agent retrieves data from this account any more, and we no longer process 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 Lexware Office: You revoke the API key in Lexware Office under "Erweiterungen → Public API". Disconnecting in the app only deletes the key with us; at Lexware it stays valid until you revoke it there. The module also does not delete event subscriptions when disconnecting. Until then, Lexware keeps sending identifiers to the old address. We therefore recommend revoking the key at Lexware.
- What remains: What an agent has taken over from Lexware data into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Contacts and drafts an agent created stay in Lexware Office.
- 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, vendors and contact persons in contacts and vouchers, 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 supplements the general privacy policy for this module. In the app you confirm it before connecting.