Sub-processors of Discord Tickets (revamped)
Which companies process personal data for Discord Tickets (revamped), and who receives data from it for their own purposes.
These are the rows of our sub-processor list that apply to Discord Tickets (revamped). The whole list also shows who we have removed and how a change is announced. Where this page and the processing annex of Discord Tickets (revamped) differ, the annex wins.
Sub-processors
| Company | What it does | Where | Services | Transfers |
|---|---|---|---|---|
| IONOS SE, Elgendorfer Straße 57, 56410 Montabaur | Server hosting, including the virtual server on which our own mail server runs. | Germany | Every hosted service | No third country |
| Cloudflare, Inc. | DNS hosting for our domains and nothing else. It answers which address belongs to a name. None of our services' pages, mail, files or other traffic passes through it, and no content of a service reaches it. | United States | Every hosted service | The EU-US Data Privacy Framework where Cloudflare is certified under it, otherwise standard contractual clauses |
| Sentry (Functional Software, Inc.) | Error reports, received on its EU data region from the services named here and from no others. What each service sends is set out in that service's annex, and for GOpenCSR, which has no annex, in its privacy notice. | United States, EU data region | GAdvisory, GAnalytics, GOpenCDR, GOpenCNR, GOpenCSR, Contribution Checker, Discord Tickets | The EU-US Data Privacy Framework (Functional Software, Inc. is certified) |
Receive data, but are not sub-processors
These receive personal data for their own purposes, because somebody asked for it, and not to process it on our behalf or yours.
| Recipient | What reaches it, and why | Services |
|---|---|---|
| Discord Inc. (United States) | It is the source of the data, which exists in Discord because the members of your server put it there, under Discord's terms with them. | DAnalytics, Discord Tickets, YAGPDB |