How to read this register
Inference providers process customer requests; other services support Zrelay’s own website, billing and communications. Routes vary by tier and availability. Inference-supplier identities are commercially confidential and are not published here. Information required by applicable law is provided through the appropriate restricted channel. This register is not an executed DPA or proof of complete contractual coverage.
Current register
| Provider | Purpose and data | Processing role | Region / status |
|---|---|---|---|
| Inference upstreams | 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 support and privacy mail, including sender details and content. | Support mailbox service. | In use. Processing locations, mail-content retention and transfer terms require verification. |
| Resend | Recipient address and transactional security, recovery or purchase message. Purchase addresses remain separate from optional recovery addresses. | Transactional email delivery. | Selected; activation and a real delivery test remain pending. |
| 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 are operator-managed; their software projects do not receive data merely because Zrelay uses the software. The operator's own hosts are in Spain. That location does not extend to external providers or inference processing. Databases, backups and payment systems still process customer information.
Bitcoin creates public-network records; the network is not a contracted subprocessor. Stripe checkout is implemented but not currently offered. If enabled, Stripe processes billing, contact, payment, optional tax and transaction data for payment, tax and fraud controls. Zrelay remains seller. Selected integrations do not imply active use.
G2G is seller and merchant of record for its marketplace transactions, not a Zrelay subprocessor. Its checkout and privacy terms govern those transactions. Development software providers are not listed solely because their tools are used.
Supplier information and changes
For customer-instructed personal-data processing, the relevant agreement needs a restricted annex identifying the actual chain: legal entities, functions, countries, onward transfers, safeguards and change procedure. Binding supplier duties must address instructions, retention, independent use, deletion and assistance. Confidentiality does not replace required customer information or authorization.
Request route-specific details through support@zrelay.net. Content storage alone is not prohibited, and no retention does not mean no processing. This register promises neither EU-only processing, no training nor completed transfer safeguards. Supplier contracts and applicable change notices require verification before contractual reliance.