Sub-processors
Who else can touch data in the hosted edition, who cannot, and which relationships are yours rather than ours.
Updated
What a sub-processor is
A sub-processor is a company we engage that can process your personal data while we provide the service to you. Where we engage one, we stay responsible to you for what it does.
This page lists them. It is short, and that is the point rather than an accident: the fewer companies stand between you and your data, the fewer answers you need before you can approve anything.
Which edition this applies to
This page applies to Boreon Cloud, the edition we operate for you.
On Boreon Server there is nothing to list. The software runs in infrastructure you control, your content never reaches us, and we engage nobody to process it. The providers involved are your own, chosen and contracted by you.
The current list
- Hosting infrastructure
- Infomaniak, Switzerland. Boreon Cloud runs on dedicated Infomaniak infrastructure in Geneva, behind a web application firewall. This is where the service and its data live.
- Everything else
- Nothing else reaches the data inside Boreon Cloud. Correspondence you send us, and the paperwork around a subscription, are handled on ordinary business systems that hold no access to your deployment. If you are assessing us and need those named as well, ask at privacy@boreon.com and we will tell you which ones and where they sit.
This list is short because the service is built to keep it short. A page like this is only worth reading if it is complete, so if you find something that can reach your data and is not named here, tell us and we will correct the page.
Who is not our sub-processor
Three companies can end up touching your data through Boreon without being engaged by us at all, because in each case the relationship is yours.
- Your model provider
- AI is optional and runs on the key you supply, with the provider you chose, under the contract you hold with them. Boreon supplies no key and keeps no shared pool. Anthropic, OpenAI and Azure OpenAI are your providers, not our sub-processors, and pointing the key at your own endpoint removes the question entirely.
- Your warehouse
- Salesforce Data 360, Snowflake Horizon Catalog and Databricks Unity Catalog are your systems, reached read-only with a credential you issue. Your data stays where it is. We read from it under your own role.
- Your Tableau environment
- Your Tableau Cloud site or Server is yours, and you sign in with your own token so your own permissions apply. We inherit them and never widen them.
Naming these companies anywhere on this site describes what Boreon connects to. It never means they endorse, resell, sponsor or have reviewed the product.
Nothing here trains a model
Boreon does not train or fine-tune models, on your content or on anything else, and does not use your content to improve the product.
What your chosen provider does with a prompt is governed by the contract you hold with them. That is one more reason the key is yours: the terms that apply to your data are the terms you negotiated, not the terms we did.
When this list changes
Adding a company that can reach your data is a decision you deserve to hear about before it happens, not after.
How much notice is given, how you are told, and how you may object are set out in the data processing addendum your organisation signs. The list itself lives on this page, and it changes here when the list changes.
The date at the top of this document is the date the list last changed.
Asking about this list
If your review needs detail this page does not carry, ask for it at privacy@boreon.com. We would rather answer a due-diligence questionnaire honestly than publish a page that anticipates it and gets a row wrong.
The data processing addendum sets out the terms that govern any sub-processor we engage.