Subprocessors

1.About this list

Remote Desk uses a small set of providers to run the hosted service. They process data on our behalf, only to provide the part of the service described below. This list applies to the hosted service. If your organisation self-hosts, it chooses its own providers and we receive no data. See the data processing addendum for how we treat them.

Some providers are chosen by whoever operates the service. Where that is the case below, it says so. A provider named here is one the service can use; it may not be switched on for every deployment.

2.Hosting and real-time media

Purpose: running the application, the database, the cache and the video and audio server. The media server is LiveKit, which we run ourselves on our own hosting rather than through a third-party media service. Calls are carried in real time and are not stored unless someone records them.

Provider: the cloud or server hosting provider that hosts our infrastructure.

Data: all service data held on the platform, including account details, presence, chat, files and the live media streams passing through the media server.

3.File and recording storage

Purpose: storing uploaded files, avatars, floor backgrounds and finished meeting recordings.

Provider: an S3-compatible object storage service, as configured by the operator. Without one, files are kept on the server's own disk.

Data: files and attachments your organisation uploads, and meeting recordings.

4.Email delivery

Purpose: sending sign-in codes, verification links, invitations, notification emails and, where an organisation owner has set them up, the daily operations report.

Provider: the email (SMTP) delivery provider configured by the operator.

Data: recipient email addresses and the content of the messages sent, which can include names, meeting details and the report.

5.Mobile push notifications

Purpose: delivering push notifications to the Android app.

Provider: Google Firebase Cloud Messaging, used only when push is configured for the deployment.

Data: the device token for your device and the notification text, which can include a sender name and a message preview.

6.Speech to text

Purpose: turning meeting audio into transcripts, and voice dictation in the AI Workspace into text.

Providers: transcription of recorded meetings can run on a transcription service that we operate ourselves, with no third party involved. Where the operator has selected a hosted speech-to-text provider, audio is sent to it instead. ElevenLabs (Scribe) is the provider built into Remote Desk for this, and is the default model for AI minutes and dictation when it has been configured.

Data: the audio of the recording or dictation, and the resulting text.

7.AI models

Purpose: producing meeting minutes, answering questions in the AI Workspace and the Deskly assistant, deep research, image generation, files created by AI, and the work of AI employees.

Providers: the AI model providers an administrator has enabled and added a key for. Remote Desk ships ready to connect to Anthropic, OpenAI, Groq, Google Gemini, DeepSeek, Moonshot, Alibaba Qwen and NVIDIA, and an administrator can add or remove others. Only the providers that have been enabled receive data.

Data: only what is needed for the request being made: your prompt, the files and context you attach or that a feature needs, a meeting transcript when minutes are generated, and the model's reply. Remote Desk does not train AI models on your data.

See the AI usage policy for which features send data to a model.

8.What is not on this list

We do not use advertising or analytics providers in the app or on this website, and we do not sell personal data. See the cookie policy for what is set in your browser.

Staff of the organisation you belong to, and Remote Desk staff who support the service, are not subprocessors. Staff access is limited and audited, as described in the privacy policy.

9.Changes and questions

We will update this page when we add or replace a provider, and aim to do so before the new provider receives customer data. Customers who have signed a data processing addendum can object to a change on reasonable data protection grounds by writing to hello@thehivez.com.