1. What this agreement covers
RelaySail is a relay service: we forward your requests to third-party AI providers and return the results to you. We are not those providers and do not represent them. Every request you send is also bound by that provider's own usage policy.
This agreement takes effect together with the Terms of Service. The Terms set out what we provide, how it is billed and how outages are compensated; this agreement sets out what you must not do, and what happens if you do. Where the two differ on the same matter, this agreement prevails.
You must be 18 or older and register with a real email address at which you can be reached. The account is for you alone to use and to keep safe.
Breach = account disabled, no refund
2. Subscriptions and the API relay support Claude Code only
Currently, both subscriptions and the API relay support only Anthropic's official Claude Code client (including its official IDE extensions and official Agent SDK). You can connect through the sail installer and device client we distribute.
You must not send such requests from third-party wrapper clients, reverse-engineered or modified clients, or any tool that forges a client identifier or device fingerprint.
Unofficial clients can lead the provider to judge a Claude subscription account as shared by many people and suspend it. Once an account is suspended, everyone on that account is affected.
If you breach this clause we may disable your account and stop service immediately, and nothing already paid is refunded: not your balance (cash or granted credit), not API credit, not the remaining period of a subscription. If the breach gets a subscription account suspended by the provider, we reserve the right to recover the loss from you.
This clause also applies to requests made with an API Key. Devices using "Use API credit when the limit is reached" or "API credit only" must follow it as well. Metered billing and API Keys do not change the client restriction.
Breach = account disabled, no refund
3. Prohibited content, and no model 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. Also prohibited: fraud, money laundering, phishing, malware and malicious code, intrusion and attack tooling, bulk harassment and engagement farming, and any other use that breaks the laws and regulations of the People's Republic of China or the law where you are.
Model distillation is also prohibited. Do not use output from this service to train, fine-tune, align, benchmark or otherwise replicate any model, including by assembling training data, harvesting question-and-answer pairs in bulk, or extracting model capabilities. The model providers' usage policies prohibit this too.
A breach of this clause means the account is disabled immediately, with no refund. Where a breach may be unlawful, we retain the relevant logs and cooperate with the competent authorities.
4. One account, one person
One RelaySail account and one subscription spot are for one person. Do not resell, sublet or lend credentials, and do not let several people use one spot at the same time. Several people on one spot can lead the provider to judge the subscription account as shared and suspend it.
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 (an API Key or a device) is the holder's responsibility. You can revoke any API Key or device from the console at any time, and revocation takes effect immediately.
In the console you can set, for each API Key and device, a limit on requests per minute and daily and monthly limits on API credit spend. We recommend setting these limits when you create the credential. If a credential without limits leaks, nothing caps what it can spend before you notice.
6. Fair use
On two-person and four-person shared plans, the account's 5-hour and weekly limits are split evenly among the people on that account. Your share is 1/N of the total, shown live in the console. Your share is a hard cap: on a two-person plan each person can use up to half of the 5-hour and weekly limits. On a four-person plan each person can use up to a quarter of both limits. Shares are calculated from the official usage readings, which may lag slightly. Once your share is used up, wait for the limit to reset; you cannot use more even when the others on the account are idle. If you have turned on "Use API credit when the limit is reached" and have API credit, requests continue and are billed from API credit at the official price. This requires an available API credit account to have been assigned to you; while none is available, you still wait for the limit to reset.
The following are treated as a breach: scripting usage to max out the limits; trying to take the share of others on the same account; working around the share cap, rate limits or account protections. We will first contact you about moving to a higher plan; if it continues, the account is suspended.
When the account assigned to you has idle capacity, it may be lent temporarily to other users. Lending may pause when the account's overall usage is high, but we can't guarantee it will pause, or that lending won't affect your available capacity.
7. Compensation and limits of liability
How an outage is determined, how it is compensated and the monthly cap on compensation are set out in clause 4 of the Terms of Service. Compensation is given only as extra service time, never as cash, balance or granted credit. The one exception: if service stops due to force majeure, the monthly subscription fees you have paid convert to API credit at ¥1 = $1, until fully used.
Model output is generated by third-party models, and we make no warranty as to its accuracy, legality or availability. You are responsible for how you use it. Beyond the compensation in clause 4 of the Terms of Service, we are not liable for indirect loss or loss of profit caused by outages, model output, or changes in model providers' policies.
8. Logs and data
For billing, troubleshooting and usage reporting we record metadata for each request, including time, model, the account or provider that handled it, status code, token counts and cost. Online request logs are kept for 30 days by default.
The bodies of requests and responses are archived separately, together with that request's metadata (including account, API Key or device identifiers). For long responses, only the beginning and the end are kept. The archive is used for troubleshooting, abuse investigation and analysis, and there is currently no fixed deletion date. That data is not shared with others.
Your requests are forwarded to the relevant model provider (such as Anthropic), whose own policy governs how it handles that data. Your account email is used only for sign-in, verification codes and service notices.
When we turn on content safety checks, some request content is sent to a third-party moderation service to identify prohibited content. The checks cover only requests handled by the API credit accounts assigned to you. This includes requests that switch to API credit after the limit is reached. Ordinary API relay requests are not checked. Only the text of your latest message in each request is checked. For requests judged likely to be prohibited, we keep a text excerpt of up to 4,000 characters. Requests judged to be prohibited may be refused.
9. Enforcement, appeals and changes
We may suspend an account first and establish the facts afterwards when: clause 2, 3 or 4 appears to have been breached; a model provider restricts or suspends one of our accounts with it 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, contact support to appeal, and we will give you a decision based on the logs.
When this agreement changes, you will be asked to accept the new version the next time you open the console, and you cannot continue using the console until you do. The time, IP address, browser identifier and agreement version of your acceptance are recorded as evidence for both sides.