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 DHL 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.
DHL is not the provider of this module. DHL processes the data of your requests under its own responsibility, under the terms of your account in the DHL developer portal and its privacy notice.
2. What data the module processes
Credentials you enter when setting up:
- the API key (consumer key) of your own app in the DHL developer portal (developer.dhl.com), subscribed to "Shipment Tracking – Unified" and "Location Finder – Unified"; both interfaces only allow reading;
- optionally a second key for the Location Finder, if it runs under a different app;
- optionally a default country (country code).
The module does not retrieve anything from DHL when it is set up.
Shipment tracking: The module sends DHL the tracking number and, if an agent provides them, the recipient's postal code, the origin and requester country, the language and the DHL service. It receives and passes on to the agent: tracking number, DHL service, status with time and place, estimated delivery, origin and destination (street, postal code, town and country, as far as DHL returns them), product, weight, number of pieces, the shipment's references, the link to the proof of delivery, the return flag, links to the shipment page and to rerouting, and the shipment's history (time, status, description, place, remark, piece numbers).
Location search: The module sends DHL the address (country, postal code, town, street) or the coordinates around which an agent searches, with search radius and filters, or the identifier of a location. It receives public information about DHL locations: name, type, identifiers, address, coordinates, distance, opening hours, closure periods, services offered, usual capacity and link.
The module does not create shipments or labels and does not change anything at DHL. It does not pass names of recipients or senders on to the agent.
3. What for
Exclusively for the tasks that you or members of your organisation give an agent, for example to answer a customer's "Where is my parcel?":
- reading: track a shipment; find service points, Packstations, post offices and parcel shops near an address or coordinate; retrieve the details of a location.
The module does not write anything.
The module has no triggers. An agent only accesses it when a task requires it.
4. Whom the data goes to
- to the module's service on our server;
- to DHL (interfaces at api-eu.dhl.com and api.dhl.com) when an agent tracks a shipment or searches for a location. DHL attributes the requests to your API key and thus to your account in the DHL developer portal;
- as a result 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, and to the people an agent replies to on your behalf;
- 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, the DHL Group processes the data in the EU; DHL passes data to third countries only in specific cases (e.g. international shipments), then on the basis of binding corporate rules or standard contractual clauses (Arts. 46, 47 GDPR). DHL does not state exactly where it processes requests to these interfaces. For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the API keys and the default country encrypted (AES-GCM) in our database. The module receives them from our server with each call and does not store them itself.
- Content: The module does not store data from DHL. It fetches it anew with each request. What an agent makes of it, meaning responses, memories, knowledge entries and the steps of its run, we store like other content (Privacy Policy Sections 4 and 5).
- Transmission: The connection to DHL and between your apps and our server is encrypted with TLS.
- Pseudonymisation: In organisations that have switched on pseudonymisation, the module's results go to the language model pseudonymised, unless the organisation has switched this off for the module. There are no field masks for this module because it has no triggers. 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 queries DHL with your key any more. If an Admin or Owner set up the module for an organisation, only the organisation can disconnect it.
- Revoking at DHL: You manage the API key yourself in the DHL developer portal (https://developer.dhl.com/user/apps). Disconnecting in the app only deletes the key with us; at DHL it stays valid until you delete the app there or regenerate the key.
- What remains: What an agent has taken over from shipment data into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1).
- 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 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, such as your customers' tracking numbers, postal codes and places of delivery, 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.