Who processes data on our behalf
The supplier register, why it is a candidate list, and what it does not commit to.
Written By Dustin
Last updated 15 minutes ago
The supplier page on the marketing site records third parties that may process data on TOVIO's behalf, and what each would receive.
No approved subprocessor list is in effect
This is the part to read carefully. TOVIO Cloud is not generally available and is not accepting production customer data under that page. The entries record deployment candidates under security and procurement review. They do not state that a provider has been activated, approved by counsel, or appointed as a subprocessor.
Treat it as disclosure so that nothing arrives as a surprise later — not as a contractual commitment you can rely on today. If your organisation needs a binding list, the honest answer is that one does not exist yet.
What the register covers
Candidates span edge delivery and DNS, payments and billing, public-site analytics, monitoring and status, the feedback portal, the engineering tracker, and identity providers you configure yourself. Each row records the evaluated function and the potential data boundary. The page itself is the authoritative version of the register, and this article does not restate the rows because a copy would rot. Note that the register covers candidate service dependencies; it is not an inventory of every processing relationship the privacy notice describes, and the notice is the wider document.
The feedback loop, specifically
The feedback and help portals are operated by a hosted vendor established in the European Economic Area, with hosting in the EEA. For the AI features that are enabled, the content you post is processed by that vendor's own AI providers, which are named on the register.
Where a post becomes engineering work, an operator pushes a paraphrased title and a link to the engineering tracker. The post body never goes, and neither does portal identity or your email address. That is the whole of what the tracker receives.
The engine itself has no processor
Running TOVIO locally, or against a Forge you operate yourself, involves no processor at all. The register concerns the websites, the portal, and the planned hosted service.
Before production opens
A counsel-approved list must identify each contracted legal entity, the service purpose, the processing location, the transfer mechanism, and the change-notification process. That list will be versioned and linked from the accepted data-processing agreement. Until then, no prelaunch change-notification channel is promised — do not assume a notification exists.
Questions
privacy@tovio.dev.