How to read this register
This register distinguishes inference providers from services used for Zrelay’s own website, billing and support operations. Inference routes can vary by tier and availability. Full upstream names and contracts are not published here. Business-customer supplier details and DPA coverage require further verification; this register does not claim complete GDPR contractual coverage.
Current register
| Provider | Purpose and data | Processing role | Region / status |
|---|---|---|---|
| Primary inference upstream | Routes model-inference requests supplied through Zrelay. Receives customer request content, which may include prompts, images or files, and generated output while requests are processed. | Inference service provider used by Zrelay for customer requests. | In use. |
| Oracle Cloud Infrastructure | Hosts public ingress and the primary gateway compute path. Processes network connection information, requests and responses passing through hosted infrastructure. | Infrastructure provider for the public ingress and gateway compute path. | In use. |
| Cloudflare | DNS and retained fallback infrastructure. When a fallback Worker or proxy route is used, it processes connection metadata and request/response content. DNS use alone does not carry inference bodies. | DNS service; infrastructure processor when the fallback traffic path is activated. | DNS in use; proxy/Worker fallback available. |
| Purelymail support email | Processes messages sent to the support and privacy mailbox, including sender details and message content. | Email service for Zrelay's own support operations. | In use. Processing locations, mail-content retention and transfer terms require verification. |
| Telegram | Customer-initiated support and automatic operational alerts. Purchase notifications include invoice IDs, amounts, methods, timestamps and shortened transaction/receipt references; support includes information the customer sends. | Support and operational messaging dependency for Zrelay’s own operations. | In use. |
| Google Fonts | Delivers website typefaces through browser requests, which disclose connection information such as IP addresses and request headers. | External website font-delivery service. Does not receive inference requests through this integration. | In use. |
Self-hosted components and exclusions
PostgreSQL and BTCPay Server run as operator-managed infrastructure in the repository. Their software projects are not separate recipients merely because the software is used. Database, backup and payment infrastructure still process customer information; the operator must document where those systems run and who can access them.
Bitcoin payments also create records on the Bitcoin network. The public network is not a contracted Zrelay subprocessor. Stripe is not integrated or an active payment processor for this service. Source-control and software-package providers are not listed solely because they are used for development.
G2G is described in the legal documents as the seller and merchant of record for purchases completed in its marketplace. It is not listed here as a Zrelay subprocessor. Its marketplace privacy, checkout and refund terms govern that transaction; Zrelay’s separate API service remains subject to these policies.
Supplier information and changes
Business customers can request supplier and data-processing details through support@zrelay.net. Full supplier identities and DPA terms must be verified before contractual reliance. Material route changes can be raised through the support channel.