Who processes your information
Zrelay operates the customer-facing API service. For account administration, billing, fraud prevention, capacity-partner enquiries and support, Zrelay determines the purposes of processing. For personal data that a business customer submits for inference under its instructions, Zrelay acts as processor or service provider; see the data processing addendum.
Account administration and delivery support the service relationship; security and proportionate abuse prevention protect the service; accounting and other records are retained where required by law. Customers are responsible for establishing their own lawful basis for content submitted to the API.
Account, billing and operational records
Paid accounts use a generated account code. The account and Bitcoin checkout flow do not require an email address or personal name. The database records internal account IDs, hashed account-code lookups and verifiers, API-key hashes and metadata, key labels, model-family permissions, spending limits, status and timestamps. Plaintext customer API keys and account codes are shown when issued and are not retained in the account records for later recovery.
Billing records include invoice and receipt identifiers, purchased and remaining credit, amounts paid, discounts, referrals, settlement timestamps and refund-coverage dates. Checkout consent records include a session ID, the selected tier and currency, consent timestamp and wording, terms and application versions. The self-hosted payment system also processes payment addresses, transaction references, amounts and confirmation status.
G2G redemption is not available yet. If marketplace sales begin, G2G will control its checkout and buyer records; Zrelay may receive order and delivery references needed for its service. An account ID alone cannot recover an account or credit.
API usage records include account, key and reservation IDs; requested or reported model identifiers; input, output, reasoning and cache token counts; usage cost; request size and path; whether client instructions were present; and timestamps. Reservation records track authorization, completion and release states. These records support metering, spending controls and troubleshooting.
Prompts, outputs and upstream processing
The gateway reads and forwards request content to an independent inference upstream, and processes responses while delivering and metering them. Content may include text, images, file content or other personal data that you submit through supported request formats. Normal inference prompt and output bodies are not retained as conversation history in Zrelay’s application database.
There is a diagnostic exception: trial-upstream authentication failures can retain a bounded upstream error-response excerpt, HTTP status and upstream request ID. Error excerpts are limited to 4,096 characters and receive credential redaction, but the gateway cannot guarantee that an upstream error never echoes request information. Do not interpret the absence of conversation-history storage as zero retention across the entire request path.
Trial abuse checks retain a one-way signature derived from request content and selected protocol headers, together with request size, model, output limit, sequence and issuance timing. They do not retain the raw prompt or those raw headers in the behavioral record. Upstream providers may apply their own processing and retention rules.
Network information and service logs
Hosting, reverse proxies and any activated edge service process connection information, including IP addresses. The account portal uses source IP addresses in memory to limit repeated login failures. Its thresholds use recent 15- and 30-minute windows; these are decision windows, not a guaranteed deletion schedule for every map entry.
The gateway removes common client-IP and forwarding headers before sending requests upstream. This reduces disclosure through those headers; it does not remove information you include in request content. Application logs record operational errors and identifiers. Web-server, ingress and platform logs may include network information and requested URLs according to the active infrastructure configuration.
Support, partner enquiries and notifications
Privacy and support requests sent to support@zrelay.net are processed through a support-email provider. The provider's contractual role, processing locations, retention for mail content and international transfers still require verification. Customers may also choose Telegram. Automated operational notifications send limited purchase information to Telegram, including invoice IDs, amounts, payment methods, timestamps and shortened transaction and receipt references. Those notifications do not intentionally include account recovery codes, API keys or prompt bodies.
The capacity-partner enquiry form collects an email address, the proposed provider and available capacity amount, with submission dates. These details are stored to review and respond to enquiries. This form is separate from customer account registration.
Cookies and browser storage
The account portal uses a necessary zr_session cookie with a 12-hour lifetime. It is marked Secure, HttpOnly and SameSite=Strict. Its server-side record stores a hash of the session token. Logging out removes that session.
The website uses local storage to remember dismissed promotional campaigns and session storage to remember a dismissed service banner. You can remove these preferences using your browser’s storage controls. No advertising or website analytics integration was identified in the website source reviewed. Infrastructure-level metrics and logs are separate from browser analytics.
Pages load typefaces from Google Fonts. Your browser connects to Google’s font servers, disclosing connection information such as your IP address and request headers to that service. This external font delivery is separate from inference processing.
Retention and deletion
Zrelay retains account, transaction, consent, usage and support records as needed to provide the service, address disputes and meet applicable obligations. Retention periods differ by record type and remain under review; contact support about a specific record. Purchased credit and accounts do not expire merely because a documentary retention period ends.
Ordinary inference content is not stored as a conversation archive in the application database. Operational diagnostics and infrastructure backups can retain limited information for separate periods.
Requests and your rights
Depending on applicable law, you may request access, correction, erasure, restriction, portability or object to processing; where processing relies on consent, you may withdraw that consent. You may also complain to your competent data-protection authority. For Spain, that authority is the AEPD.
Send requests to support@zrelay.net. Provide a non-secret account ID or invoice reference so support can establish an appropriate verification method; do not send credentials. Some records may need to be retained for legal duties or claims. For content submitted on behalf of a business, contact that business as controller; Zrelay will assist it as applicable.