1. What this agreement covers
RelaySail is a relay: we forward your requests to third-party AI providers and hand the results back unchanged. We are not those providers and do not represent them. Every request you send is also bound by the provider's own usage policy.
This agreement takes effect alongside the Terms of Service. The Terms say what we sell, how billing works, and how outages are compensated; this agreement says what you may not do, and what happens if you do it. Where the two conflict on the same point, this agreement governs.
You must be 18 or older and register with a real, reachable email address. The account is yours to use and to keep safe.
Breach = account disabled, no refund
2. Subscription lines accept Claude Code only
Requests sent over a Claude subscription line — a shared monthly seat or subscription allowance — may come only from Anthropic's official Claude Code client (including its official IDE extensions and official Agent SDK), or from the sail installer and device client we distribute ourselves.
Third-party wrappers, reverse-engineered or patched clients, and any tool that forges a client identifier or device fingerprint are not allowed on the subscription lines.
This is not a preference, it is how the accounts survive. Unofficial clients send forged device fingerprints upstream; the provider reads that as one account shared by many people and revokes it outright. It has already happened here: a subscription account was killed 90 minutes and 227 requests after it went live. When one account dies, everyone sharing it stops working.
If you breach this clause we may disable the account and stop service immediately, and nothing already paid is refunded — not the CNY balance, not gift credit, not USD allowance, not the remainder of a monthly seat. If it gets one of our upstream accounts banned, we reserve the right to recover the loss.
The metered API relay — billed in USD allowance at the vendor's list price — does not restrict clients. Use whatever tooling you like there. Every other clause of this agreement still applies.
Breach = account disabled, no refund
3. Content limits, and no distillation
Do not use this service to generate, process, distribute or assist with: sexual services or pornography; gambling; drugs and other controlled substances; or the solicitation, traffic funnelling and payment channels behind any of them. The same applies to fraud, money laundering, phishing, malware, intrusion and attack tooling, bulk harassment and engagement farming, and to any other use that breaks the law where you are.
Model distillation is likewise prohibited. Do not use output from this service to train, fine-tune, align, benchmark or otherwise replicate any model — including by assembling training data or harvesting question-and-answer pairs in bulk. This is not only our rule: the upstream providers forbid it too, and the account that gets banned first is ours.
A breach of this clause means the account is disabled immediately, with no refund. Where a breach may be criminal, we retain the relevant logs and cooperate with the authorities.
4. One account, one person
One account and one subscription seat serve one person. Do not resell, sublet, or lend credentials, and do not have several people on one seat at once — it eats into the share other customers on that tier have paid for, and on the subscription lines it trips the provider's account-sharing detection.
Do not build another relay on top of this service and offer it to others, whether or not you charge for it.
5. Your credentials are yours to guard
Usage from a leaked credential is the holder's to pay. You can revoke any key or any device from the console at any time, and revocation takes effect immediately.
The console lets you set a per-minute request rate and daily or monthly spend caps on every key. Set them when you create the key: until a leak is noticed, there is no ceiling on what an uncapped key can spend.
6. Fair use
An upstream account's quota window is shared by everyone on that tier, so your share is 1/N of the total, visible live in the console. Going over your share is not rate-limited today — when nobody else on the tier is using it, that headroom is yours to use.
But scripting a window to saturation, deliberately crowding out others over time, or working around our rate limits and account protections is treated as a breach: first a conversation about moving up a tier, then suspension if it continues.
7. What we make good, and what we don't
How an outage is counted, how it is compensated and the monthly ceiling on that compensation are in clause 4 of the Terms of Service. Compensation is paid as extra service time only — never as cash, balance or gift credit.
Model output comes from a third-party model, and we make no warranty as to its accuracy, legality or availability. What you do with that output is on you. Beyond the compensation in clause 4 of the Terms, we are not liable for indirect or consequential loss arising from outages, model output, or changes to upstream policy.
8. Logs and data
We record metadata for each request — time, model, upstream, status code, token counts and cost — for billing, troubleshooting and usage reporting. Request logs are kept 30 days by default.
To diagnose faults and investigate abuse we may retain samples of request bodies for a limited period. That data is used for those purposes only; it is not shared and it is not used to train any model.
Your requests are forwarded to the relevant upstream provider, whose own policy governs their handling of that data. Your account email is used only for sign-in, verification codes and service notices.
9. Enforcement, appeals and changes
We may suspend an account first and establish the facts afterwards when: clauses 2, 3 or 4 appear to have been breached; an upstream provider flags or bans one of our accounts because of your usage; or we have reason to believe your credentials have leaked.
An account disabled for a breach is not refunded. If you think a decision was wrong, reply to any notification email we have sent you — it reaches the same inbox — and we will give you an answer based on the logs.
When this agreement changes you will be asked to confirm the new version the next time you sign in to the console, and the console stays closed until you do. The time, IP address and version of your acceptance are recorded as the record for both sides.