Service providers

Last updated:

What this is about

This page names the providers we use to run ucando and supplements the "Recipients and processors" section of the privacy notice. For each provider it states the company and its registered office, the task and the data, the place of processing and — where data leaves the European Union — the basis for that. We keep it up to date; the date of the last change is shown above.

Processors

These providers process data on our behalf and on our instructions (Art. 28 GDPR).

Microsoft (Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland) runs, on Microsoft Azure, the application, the database, file storage, the search index — long-term memory included —, telemetry, and the AI models and text recognition in uploaded documents. This covers all data that arises in the application: account data, your inputs and the models' responses, documents, memory entries and operational data. Place of processing: data centres in the European Union (Azure region Sweden Central); the AI models run in Azure's EU data zone. No transfer to a third country is involved. Abuse monitoring: Microsoft checks inputs to and responses from the AI models automatically for misuse; this check stores nothing. Where misuse is suspected, selected content may be stored and viewed by authorised Microsoft staff in the European Economic Area; Microsoft states no maximum retention period for this. Microsoft does not state expressly in which role it carries out abuse monitoring; under its contract, Microsoft generally acts as a processor. Microsoft's list of sub-processors: https://aka.ms/subprocessor.

Google Cloud (Vertex AI; contracting party: Google Cloud EMEA Limited, Velasco, Clanwilliam Place, Dublin 2, Ireland) processes, through its EU endpoint, requests to the Anthropic (Claude) and Google (Gemini) models when you select one of them in the model selector. A Google model there also turns text into vector representations for search — your questions, uploaded documents, memory entries and passages of conversations. The data processed is your inputs, the conversation context, files and the models' responses. Place of processing: European Union. No transfer to a third country is involved. Abuse monitoring: Google also checks for abuse. Depending on the model and the contractual terms, suspicious inputs and responses — or, for individual models, all of them — may be stored regionally for up to 90 days and reviewed by Google staff. Google does not state expressly in which role it acts in doing so. Google Cloud's list of sub-processors: https://cloud.google.com/terms/subprocessors.

If an AI model fails, a model from the other of these two providers may step in. We use no substitute provider outside this list.

ZITADEL (CAOS Ltd., Lerchenfeldstrasse 3, 9014 St. Gallen, Switzerland) runs our identity provider on an EU instance and processes your identifier, email address, name and sign-in metadata. Place of processing: European Union. For the registered office in Switzerland there is an adequacy decision of the European Commission (Art. 45 GDPR). ZITADEL's list of sub-processors: https://zitadel.com/docs/legal/subprocessors.

Email. Our own emails are sent on our behalf by Brevo (Brevo SAS, Paris, France): confirmations about your contract, withdrawal and cancellation, our identity provider's sign-in emails and — depending on your settings — notifications from the application's inbox, for example about your account or replies to your requests. The data processed is your email address, your name and the content of the email, by Brevo's account on servers in the European Union. We send news and announcements with promotional content only if you have switched them on in the settings and confirmed your email address through the link in a confirmation email (double opt-in). The legal basis for them is your consent under Art. 6(1)(a) GDPR and § 25(1) of the German Telecommunications Digital Services Data Protection Act (TDDDG); you can withdraw it at any time in the settings or through the unsubscribe link in every such email. For all other emails the legal basis is Art. 6(1)(b) GDPR. All our emails contain a counting pixel and redirected links from Brevo. With them, Brevo counts for us how often our emails are opened and which links in them are clicked — as totals only: Brevo links opens and clicks neither to you nor to your email address. We use these figures to check that our emails arrive and to improve them; the legal basis for this is our legitimate interest under Art. 6(1)(f) GDPR. Brevo's list of sub-processors: https://www.brevo.com/legal/termsofuse/#annex-2-list-of-sub-processors.

Providers for our own billing and website

We use these providers for our own billing and for our public websites. They do not receive the content you work with in the application.

Stripe (Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin 2, Ireland) handles payments, subscriptions and invoices, and sends payment receipts. The data processed is your name, email address, billing address, VAT identification number where applicable, and payment data. Place of processing: European Union and United States (Stripe, Inc.). We base the transfer on the adequacy decision of the European Commission where Stripe is certified under it, and additionally on standard contractual clauses pursuant to Art. 46(2)(c) GDPR. Stripe is an independent controller for its own legal obligations, such as identity verification and anti-money-laundering checks. Stripe's list of service providers: https://stripe.com/legal/service-providers.

Audience measurement. Visits to our public websites are counted by Pirsch Analytics (Emvi Software GmbH, Nickelstraße 1b, Rheda-Wiedenbrück, Germany) on our behalf, on servers in Germany. Nothing is measured in the application behind the sign-in. Details are in the "Audience measurement on our websites" section of the privacy notice. Pirsch publishes no list of its own sub-processors; they are named in its data processing agreement.

Independent controllers — not data processing on our behalf

We send data to these parties only when you use the function concerned. They process the data under their own responsibility and their own terms.

Web search. When you use web search, we send the search query the model formulates from your input, together with technical parameters, to the “Grounding with Bing Search” service of Microsoft Corporation (One Microsoft Way, Redmond, WA 98052, USA); we do not send a user identifier. The query may contain personal data where your input does. Microsoft is an independent controller for this service; the Grounding with Bing terms of use and Microsoft's privacy statement apply. The query may be processed in the United States. The legal basis is Art. 6(1)(b) GDPR, as you use web search as part of the service. In a company account, the administrators can switch web search off.

Term explanations. When you have a term from a response explained, our server queries Wikipedia (Wikimedia Foundation, Inc., San Francisco, USA). Only the term looked up is sent; we send neither a user identifier nor your IP address. The term may be personal data, for example where it is a name. The Wikimedia Foundation is an independent controller for Wikipedia; its privacy policy applies. The query may be processed in the United States. The legal basis is Art. 6(1)(b) GDPR, as you use the term explanation as part of the service.

Software in use without access to your data

Not data processing on our behalf: the chat interface is built on the CopilotKit library (Tawkit, Inc., USA). Its licence check is carried out by our server, which contacts CopilotKit at regular intervals and sends only our licence key and our server's technical address — no data about you, from your browser or from your conversations. Your browser does not connect to CopilotKit, and the library's usage statistics are switched off.

Changes to this list

Further services exist in the application but are not in operation in the shipped configuration — alternative search providers and additional image generators, for instance. Before we switch one of them on or replace a provider, we add it to this list. We provide earlier versions of this list on request.