Privacy Policy
How Relay Station handles accounts, API metering and upstream processing.
Last updated: 2026-10-18
Stored information
We store email addresses, sessions, account profiles, orders, pass expiry, customer keys and API usage records. Customer keys and stored upstream credentials are encrypted with the server configuration key. Key hashes are stored separately for authentication. Sign-in codes and delivery notices may be retained in the encrypted mail queue.
API records include the public model group, status, input and output token counts, duration and timestamps. Operational records may also include the selected upstream identifier, target model and request ID. The metering ledger does not store full prompts or responses. Do not put keys or sensitive prompts in support tickets.
Upstream and third-party processing
Request content is forwarded to the configured Magpie or other upstream and then to model providers. Their logging and retention policies may differ. We do not promise zero retention by third parties. Ask support about the active upstream before sending sensitive information.
Configured email and payment providers process messages and transactions. We retain payment references and status, not full card numbers. Sessions, language and theme preferences may use cookies. Analytics or support integrations load only when configured on this site.
Access and requests
Account settings let you view and edit profile information. For a data copy, account deletion or retention questions, sign in and submit a support ticket. One-click export and deletion are not currently available. An administrator will verify your identity and explain any order, security or backup records that must be retained and the outcome of your request.
Use the support entry in the user center for privacy questions. This page does not promise automatic deletion deadlines or unimplemented self-service tools.