Legal
Sub-processors
Last updated 10 September 2026
The third parties that process customer data on our behalf — and, just as usefully, the processing we keep on our own servers instead.
Draft. The list itself was compiled from the source code and is accurate as of the date above. The legal framing has not been reviewed by a lawyer.
What this page is
A sub-processor is a third party that processes customer data on our behalf in order for us to provide Oprex. This page lists every one of them.
It is short, and that is the point. Most of what a workspace suite normally hands to other companies — transcription, search, call media, mail — runs on our own infrastructure here.
To be told when this list changes, write to privacy@oprex.net and we will add you. We will give notice before adding a sub-processor that processes customer content.
Groq, Inc.
Purpose: generating replies in the Askini assistant.
Data received: the text of an Askini conversation — what the person typed and the earlier turns of that same conversation. Nothing else from the workspace is sent: not your chats, documents, projects or mail.
Location: United States.
This is the only place where content written by your people leaves our servers to reach an AI provider. If your organisation would rather it did not, ask us and we will disable Askini for your workspace; everything else continues to work.
Google LLC — Firebase Cloud Messaging
Purpose: delivering push notifications to mobile devices, so that a phone rings for an incoming call or a mention when the app is closed.
Data received: the device token, and enough of the notification to display it — who is calling or messaging, and which conversation it belongs to.
Location: United States.
Push is how a call reaches somebody who is not at their desk. A workspace that never used the mobile app would not generate this traffic.
Hosting
Purpose: running the application, the database and file storage.
Data received: all workspace data, at rest and in transit, as an unavoidable consequence of hosting.
Provider and region: Hostinger International Limited, in Paris, France.
Each workspace has a database of its own, kept separate from other customers.
What we deliberately do not send anywhere
These are the ones a comparable product would usually outsource. Each of them runs on our own servers, and each is therefore a sub-processor we do not have:
- Voice-note transcription — a Whisper model on our own infrastructure, not a speech-to-text API
- Search and the assistant’s retrieval index — embeddings generated locally, not sent to an embeddings provider
- Call audio and video — our own media server, not a third-party conferencing vendor, so no copy of your meeting sits with anyone else
- Mail — read and sent directly against the mail server you already own
Payments
Oprex does not currently take card payments in the product, so there is no payment processor to list. When checkout goes live, the processor will be added here before it handles its first transaction.
We do not now, and will not then, store card numbers ourselves.