Updated: [TO BE COMPLETED: date]
This list forms part of the data processing agreement. For each provider it says what it receives, where, and whether it is active, planned (not in service yet) or only if the customer connects it.
The Publisher's providers
| Provider | Role | Data received | Location | Status |
|---|---|---|---|---|
| Contabo [TO BE CHECKED: Contabo GmbH] | server hosting the Service, its database and its nightly backups | all the Service's data (content encrypted per organization) | Europe [TO BE COMPLETED: data centre] | active |
| Scaleway [TO BE CHECKED: Scaleway SAS] | storage of the backup copies off the server; key management service (master key) | database copies, encrypted before sending; requests to encrypt and decrypt organization keys | France (region fr-par) | active since 17 Nov 2026 — status page https://stats.uptimerobot.com/QF8xaIKKPM |
| Google [TO BE CHECKED: Google Ireland Ltd / Google LLC] | user sign-in ("Sign in with Google") | e-mail address, name, profile picture of the person signing in; the fact that they sign in to the Service | [TO BE CHECKED: European Union / United States] | active |
| Microsoft [TO BE CHECKED] | user sign-in with a Microsoft account | e-mail address, name | [TO BE CHECKED] | planned — not available yet |
| Stripe [TO BE CHECKED: Stripe Payments Europe Ltd] | payment of paid plans | billing identity and details, payment method (entered at Stripe) | [TO BE CHECKED] | planned — not in place yet |
| UptimeRobot [TO BE CHECKED] | external availability monitoring, status page | no customer data: it queries the Service's public health address | [TO BE CHECKED] | active since 17 Nov 2026 — status page https://stats.uptimerobot.com/QF8xaIKKPM |
| Discord (operations channel) [TO BE CHECKED: Discord Inc.] | alerts to the Publisher: failed backup or test restore, full disk, burst of errors | no content; a burst of errors names the method and path of the request, which may contain a project or screen name | [TO BE CHECKED: United States] | planned — active once the channel is set |
Services the customer connects itself
These services receive nothing until the customer sets them project by project (Settings → Project). The customer chooses them, sets them and may remove them at any time.
| Service | What it receives | Location |
|---|---|---|
| Discord (the customer's team channel) | the announcement of an opened thread, a reply, a resolved thread or a publication: person's name, screen, excerpt of the comment (300 characters at most), link | [TO BE CHECKED: United States] |
| Slack | the same announcements | [TO BE CHECKED: United States] |
| Microsoft Teams | the same announcements | [TO BE CHECKED] |
| Jira (Atlassian) | the specification of an operation of the designed back end, when a user creates a ticket | per the customer's Jira |
| GitHub | the ticket for a component to build (name, description), when a user asks for it — unavailable today on the hosted Service | [TO BE CHECKED: United States] |
| Artificial intelligence agent | what the agent reads and writes through the MCP server, with a token issued by the organization; recorded in the audit log | per the chosen provider |
[TO BE CONFIRMED: are these services sub-processors of the Publisher, or recipients chosen by the customer? — see the questions for the lawyer.]
What is not a subprocessor
- Let's Encrypt issues the HTTPS certificate: it receives only the domain name.
- GitHub hosts and builds the Service's code and image: no customer data goes through it.
- The Service has no e-mail sending provider, and no audience measurement or advertising tool.