Every third-party provider that may process customer data on Opsium's behalf, with what it sees, where it is and the legal basis for any transfer. Published, not available on request.
This page exists because “available upon request” is not good enough. GDPR Art. 28(2) lets customers object to a new sub-processor, and you cannot object to a list you have not seen. Our Data Processing Agreement authorises the providers below and nobody else.
It covers both the Opsium platform and this website, in that order, because they sit on different legal footings. The platform list is the one your DPA is about. Each entry says what the provider does, what personal data it can see, where that data is held, and the mechanism that covers any transfer out of the European Economic Area (EEA).
Last verified: 18 October 2026, against the application’s code and configuration.
The Opsium platform
These providers may process data your organisation puts into the product, or data about the people who use it. Opsium is your processor; each provider below is a sub-processor engaged by us.
| Provider | What it does | Personal data it can see | Where the data is | Transfer mechanism |
|---|---|---|---|---|
| Amazon Web Services (AWS) | Application hosting, the product database, file storage, background job queues, transactional email (Amazon SES), the sign-in directory that holds your account credentials (Amazon Cognito), and the server that runs our workflow automation | All customer data held in the product | EU (Frankfurt) | Stored in the EU. AWS’s data processing terms include the EU Standard Contractual Clauses (SCCs) for any access from outside the EEA, and Amazon is certified under the EU-U.S. Data Privacy Framework (DPF) |
| Stripe | Subscription billing, invoices and card payments | Billing contact details, subscription and invoice records. Card numbers go straight to Stripe and never reach Opsium’s servers | EU and US | DPF and SCCs |
| Sentry | Error and performance monitoring, so a fault is diagnosed from evidence rather than guessed at | Diagnostic data captured when something breaks: the failing request, the signed-in user’s identifier and their IP address | EU (Frankfurt data region) | Stored in the EU. Sentry is a US company, so any access from the US is covered by the DPF and SCCs |
| OpenAI | Powers the AI assistant in the report builder, which turns a request written in plain words into a report layout | The request a user types into the assistant, and the names and formulas of the report measures saved in your workspace. Never the figures in your reports, and OpenAI does not use API data to train its models | US | DPF and SCCs |
| Google (Firebase Cloud Messaging) | Delivers push notifications to your browser and devices | The device’s push token and the contents of the notification | US | DPF and SCCs |
| Slack | Alerts the Opsium team inside our own workspace when a support request arrives, a trial starts or ends, or a payment fails | The name and email address of the person concerned, the organisation name, the text of a support request, and invoice amounts. Never the data inside your workspace | US | DPF and SCCs |
| Tally | The in-app support form | What you type into the form, and the email address you give | EU (Belgium) | Not needed: stays in the EEA |
| Google Workspace | Opsium’s company email, where support and account correspondence arrives | The emails you send us and our replies | EU and US | DPF and SCCs |
Two public services are requested directly by your browser while you use the app, rather than engaged by us to process your data, so neither works under a processor contract with Opsium:
- Google Fonts serves the typeface the application is set in. Google receives the IP address and browser details of the device loading the app. Google is certified under the DPF.
- GeoNames supplies the country and city list behind the team location picker. It receives the text typed into that one field and the IP address of the browser making the request. It is based in Switzerland, which the EU recognises as providing adequate protection.
Two exchange-rate services, CurrencyBeacon and Frankfurter, are called for multi-currency figures. A request contains a currency pair and a date and no personal data at all, so neither is a sub-processor. They are named here for completeness rather than because Art. 28 requires it.
Opsium’s workflow automation (n8n), which handles the lead and support forms on
this website and the internal notifications above, is self-hosted by Opsium on
AWS in Frankfurt, not a third-party service. It is covered by the AWS entry.
Integrations you connect yourself
Opsium can exchange data with Jira, Tempo, Clockify, QuickBooks and Google Workspace. These are not sub-processors, and the distinction is a real one rather than a technicality: nothing is sent anywhere until one of your administrators connects the integration, the destination is a system your organisation already controls, and your own agreement with that vendor governs what happens to the data once it arrives. Opsium is acting on your instruction, not engaging a supplier of its own.
| Integration | Connected by | What crosses the boundary |
|---|---|---|
| Atlassian Jira | An admin, via OAuth | Issues, worklogs and the users they belong to |
| Tempo | An admin, via OAuth | Worklogs and the users they belong to |
| Clockify | An admin, via an API key | Time entries and the users they belong to |
| Intuit QuickBooks | An admin, via OAuth | Invoices, bills and customer records |
| Google Workspace (Directory) | An admin, via a service account | Your directory’s user list, to keep team membership in step |
Disconnecting an integration stops the exchange. Data already sent to a system you control stays under your control, and removing it is done there rather than here.
This website
The providers below serve www.opsium.io, the site you are reading, and never touch product data. Here Opsium decides what is collected and why, so we are the controller and these providers are our processors. Strictly speaking they are not sub-processors of your workspace data at all. They are published here anyway, because a reader asking “who does Opsium send data to” should find one answer and not two.
| Provider | What it does | Personal data it can see | Where the data is | Transfer mechanism |
|---|---|---|---|---|
| Amazon Web Services (AWS) | Hosts this website and the content delivery network that serves it, and runs the server that receives our forms | Website requests, including your IP address, and what you submit in a form | EU (Frankfurt) for stored files and form submissions; cached pages are served from the nearest edge location | Stored in the EU; DPF and SCCs |
| Slack | Delivers each form submission to the Opsium team, so a person reads it and replies | What you enter in a demo, contact, free-trial or template form: name, email, company, role, phone, team size, message, and the campaign that brought you, if any | US | DPF and SCCs |
| Google Analytics | Website measurement, only after you accept Analytics cookies | Pages visited, how you arrived, approximate location and device type. No names or email addresses | US and EU | DPF and SCCs |
| PostHog | Website product analytics, only after you accept Analytics cookies | Pages visited, a small set of named events such as a form being submitted, approximate location and device type. No names or email addresses | EU (Frankfurt) | Stored in the EU. PostHog is a US company, so any access from the US is covered by SCCs |
| Cloudflare | After a free-trial signup, the welcome page asks Cloudflare’s public DNS service which email provider your company uses, so it can offer an “open your inbox” button | Only the domain of your email address (for example company.com, never the full address) and your IP address |
Global network | DPF |
| Tally | The feedback and support forms linked from this website’s footer | What you type into those forms | EU (Belgium) | Not needed: stays in the EEA |
| Google Workspace | Opsium’s company email | Correspondence you send us | EU and US | DPF and SCCs |
What none of them may do
Every provider that processes customer data for us is bound by a written agreement that requires the same protection standards this policy commits us to, and specifically:
- They process customer data only on Opsium’s instructions, for the purpose named above, and never for their own purposes.
- They may not sell it, and they may not use it to train their own AI models.
- They may not engage a further sub-processor without our authorisation, and must bind any they do engage to the same terms.
Opsium remains responsible to you for each of them.
We do not sell customer data, and we never will. That is a different and stronger statement than “we share it with nobody”. Delivering a hosted product is not possible without a hosting provider, and any vendor claiming otherwise is describing something other than how software works.
When this list changes
We publish the change here and notify customers by email at least 30 days before the new provider begins processing, so there is time to object. If you object and we cannot offer an equivalent alternative, you may terminate the affected part of the service without penalty, as set out in the Data Processing Agreement.
To be notified directly rather than checking this page, write to legal@opsium.io from the address on your account and ask to be added to the sub-processor notification list.