This policy explains what Relayvia collects, how it is used and how long it is kept.
1. Who we are
Relayvia is operated by Robi, LLC (2810 N Church St STE 91865, Wilmington, DE 19802, USA). Privacy questions: service@relayvia.dev.
2. Account data
Your email (your sign-in name), nickname and account name; passwords are stored only as irreversible hashes. The IP address and email domain used to sign up, to prevent mass registrations. Sign-in sessions (device, browser, IP, time), which you can review and end on the Security page.
3. We do not store request content
Prompts, model responses and uploaded images or files are not stored; they exist only in memory while being forwarded. Results of asynchronous jobs such as images and videos are kept for 24 hours for download, then deleted.
4. Usage records and retention
Each request records the model, token counts, amount charged, duration, status and request ID; the client IP is recorded only if your account turns it on. Usage records stay in the database for 90 days and are then archived, for 400 days in total. Hourly aggregates (counts, tokens, amounts and latency, no request content) are kept for 13 months. The wallet ledger is kept permanently (13 months in the database, then archived), and so are audit logs. Support tickets (subject, description and replies) are deleted 400 days after they are created; attached screenshots are kept for 90 days. Export files you create in the console are kept for 72 hours, can be downloaded only by you, and are then deleted. Invoices are kept permanently, including the billing details you entered (name, email, address, tax ID); they are accounting records and are kept even after the account is deleted. Error records keep only structured fields and masked summaries, never request or response bodies, URL parameters or keys.
5. API keys
For each API key we store a lookup hash, the last 4 characters and the full key in encrypted form, which our servers decrypt. In the console, only the key's creator and account admins with API key management permission can view it. The full key never appears in logs. Older keys without an encrypted copy cannot be viewed and must be recreated.
6. Model developers
To produce a response, request content is sent to the developer of the model you call, under the data terms of that developer's API.
7. Processors
We use the following vendors to process data, only to run the service: ・Cloud hosting and database services: store accounts, usage records and the ledger. ・Cloudflare: network and security (website delivery and protection, bot checks with Turnstile) and sending email. ・Stripe: payment processing (United States), for your payment details when you top up online. ・Third-party sign-in (Google, GitHub, Telegram): only when you choose to sign in with them, to receive your account identifier and email. ・Model developers and API suppliers: receive request content to produce responses, see Model developers. We do not sell personal data or use it for advertising.
8. International transfers
Our servers and vendors may be located outside your country or region, including in the United States and Singapore, so your data is transferred across borders. We work only with vendors that offer appropriate safeguards.
9. Email
We send account emails: email verification, password resets, password-changed notices, team member invitations and credit notices.
11. Your rights
You can view and edit your profile, export usage records and disable API keys in the console. You can also contact service@relayvia.dev to access, correct, delete or export your personal data; we reply within 30 days. After an account is deleted, the wallet ledger, audit logs and invoices are kept as required by law and accounting obligations and are not used for anything else.
12. Children
The service is not offered to anyone under 18, and we do not knowingly collect data from minors; if we find such data, we delete it.