Sub-processors
Last updated: 25 October 2026
AgoraBot ("we", "us"), operated by Nikita Zotov, Individual Entrepreneur (Republic of Armenia), uses the sub-processors below to provide the Service. We keep this list current and will notify administrators of material changes.
Independent controllers (not sub-processors)
The party below is not our sub-processor. It determines its own purposes and means for the data it handles and acts as an independent (separate) controller under its own terms and privacy policy; it does not process personal data on our behalf or on our documented instructions.
| Party | Role | Data | Location |
|---|---|---|---|
| Discord (Discord Inc.) | The platform the Service runs on and the source of activity and identifier data; Discord independently controls the underlying platform data under its own privacy policy | Discord user/guild/role/channel IDs, activity events | United States (own safeguards / SCCs) |
Because Discord is an independent controller, disclosures to it are not onward sub-processor transfers under our DPA; it relies on its own safeguards (see the DPA §1 and the Privacy Policy).
Sub-processors
These parties process personal data on our behalf and on our instructions under Art. 28 GDPR terms consistent with our DPA:
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Hetzner Online GmbH | Application and database hosting | All processed data at rest | European Economic Area (Germany) |
| Scaleway SAS | Offsite storage of age-encrypted database backups and erasure-log sidecars. Scaleway receives ciphertext only; the decryption key is not held by Scaleway or by the production host. | Encrypted backup files containing all database data and erasure-log sidecars, as ciphertext | European Economic Area (France / selected Scaleway Object Storage region) |
| Zoho (Zoho Corporation B.V.) | Email hosting for support and privacy contact addresses ([email protected], [email protected]); processes correspondence you send us | Email address, message content and any personal data you include when contacting us | Stored in the European Economic Area (Zoho EU data centre, zoho.eu). Under Zoho's data processing addendum, Zoho group entities in India may access it for support and debugging, and Zoho's own sub-processors may process it outside the EEA; Zoho is responsible for the transfer basis |
| Cloudflare, Inc. | CDN, reverse proxy, TLS termination and DDoS protection in front of our public hostnames. Every request to the website and the dashboard passes through Cloudflare, which decrypts it in transit in order to forward it to our origin server. Nothing is stored by us at Cloudflare; it is a transit processor. | Request data in transit — IP address, request metadata, and the content of the request itself, including authenticated dashboard traffic | Global. Cloudflare operates an anycast network and routing is determined by that network; a request may be handled at an edge location inside or outside the EEA. Governed by the Cloudflare Data Processing Addendum, which incorporates the EU Standard Contractual Clauses |
We do not sell personal data. Where a sub-processor processes data outside the EEA, we rely on appropriate safeguards such as Standard Contractual Clauses.
Processor for our own billing data (outside the DPA)
The party below processes personal data on our behalf, but only data for which we are the controller: the payment and billing data of the person who buys a plan. It receives no community activity data, so it is not a sub-processor under the DPA and the DPA §6 notice does not apply to it.
| Processor | Purpose | Data processed | Location |
|---|---|---|---|
| Freemius, Inc. | Payments, tax and invoicing as our Merchant of Record and reseller | Buyer's name, email address, billing address, payment details, and the purchase and subscription records | United States. Freemius's Data Processing Agreement incorporates the EU Standard Contractual Clauses (Module Two) and the UK International Data Transfer Addendum |
Infrastructure services that do not process personal data
The services below are part of our deployed stack but receive no personal data, so they are not sub-processors and no Art. 28 instrument applies to them. We list them for completeness, because our sub-processor list is meant to match what is actually deployed.
| Service | Purpose | What it receives |
|---|---|---|
| healthchecks.io | Dead-man's-switch monitoring for our backup and maintenance timers | A timestamp, an exit status, and — on failure — the tail of the failing unit's system journal. Operational data only; no member data, no user identifiers. |
Changes to this list
Before we add or replace a sub-processor we email each server's controller at the contact address given when accepting the DPA, and publish the change here, in the changelog below, at least 30 days before the change takes effect (DPA §6). The changelog is the public record of every notice. Administrators may object on reasonable data-protection grounds by emailing [email protected] within those 30 days.
| Date published | Effective | Change |
|---|---|---|
| 19 August 2026 | At launch | Initial list. |
| 22 August 2026 | At launch | Cloudflare, Inc. added as a sub-processor (CDN, reverse proxy and TLS termination in front of the public hostnames). Disclosed before launch; no change to an existing deployment. |
| 24 August 2026 | At launch | Contabo GmbH removed before ever being engaged. It was listed as the offsite backup-storage provider; Contabo has since made object storage conditional on ordering a VPS alongside it, so no contract was concluded and it never held any data of ours. The replacement is listed in the Scaleway row below before any backup leaves our server. |
| 24 August 2026 | At launch | Brevo (Sendinblue SAS) added as a sub-processor for outbound transactional email. EU consumer law requires us to confirm a withdrawal from a paid plan on a durable medium without delay, which a web page is not; Brevo delivers that notice. Disclosed before launch; no change to an existing deployment. |
| 24 August 2026 | At launch | Scaleway SAS added as the offsite backup-storage provider for age-encrypted database dumps and erasure-log sidecars. Disclosed before launch; no change to an existing deployment. |
| 17 September 2026 | At launch | Brevo (Sendinblue SAS) removed before launch. Its relay converted our plain-text withdrawal confirmations into tracked HTML with an unsubscribe link, which is not acceptable for a notice we are legally required to send, and it could not be configured otherwise on our plan. It only ever delivered test messages to our own address. Withdrawal confirmations are sent from our Zoho mailbox instead, which is already listed. |
| 17 September 2026 | At launch | Anthropic, PBC removed before launch. It was listed for an optional AI-assisted setup feature that was never switched on in production and has now been withdrawn from the Service, so Anthropic never received any data from us. If we offer an AI feature again, its provider will be added here with 30 days' notice first. |
| 6 October 2026 | Correction | Zoho: location corrected. We previously said Zoho's processing stays in the EEA. Zoho's data processing addendum allows its group entities in India to access mailbox data for support and debugging, and its own sub-processors to process it outside the EEA, so the row above now says so. No sub-processor was added or replaced. |
| 7 October 2026 | At launch | Paddle removed before launch; it never processed any data of ours. Freemius, Inc. listed as our Merchant of Record, as a processor of billing data only, outside the DPA. No community data reaches it, so no sub-processor was added under the DPA. |