1. What you are buying
A subscription is the right to use one official Claude subscription account, billed monthly. Solo means the whole account is assigned to you alone; two-person and four-person shared plans mean several people share one account, and you buy one share. 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. You stay on the same assigned account long-term (prompt caches and signed thinking blocks are bound to the account).
The API relay currently supports Claude Code only. It bills each call from your API credit at the vendor's official price and is separate from subscriptions. API credit is bought with yuan cash and cannot be refunded once converted. While your subscription is active, requests handled by your subscription account are included in the monthly fee and do not use API credit; models your subscription does not include are refused and are never switched to API credit automatically. The two never offset or substitute for each other.
2. Billing
Subscriptions are billed in 30-day periods, each deducted in one payment from the cash part of your yuan balance. There is no auto-renewal: renew before expiry yourself, and we email reminders 7 days, 3 days and 1 day before expiry, plus one at expiry. API calls do not spend yuan: convert cash into API credit, and each call is billed from that credit at the model's official price.
The yuan balance has two parts: cash and granted credit. Granted credit comes from campaigns and coupons; it cannot be withdrawn, cannot buy a subscription, and cannot be converted into API credit, and it is reclaimed when it expires. Subscriptions and API credit conversions accept cash only. API credit is a service right bought with cash, cannot be converted back, and expires; each new conversion extends the expiry of all your API 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.
Price changes never affect a subscription already running; they apply from your next renewal.
3. Start, expiry and cancellation
Renew before expiry to keep your current account. At expiry, your spot is released immediately; if you renew later, you are assigned an account from the spots available at that time.
A temporarily borrowed spot does not end automatically when the original subscriber's plan expires or is cancelled. It continues until we reclaim it or convert it into a regular spot.
Cancelling this subscription releases its spot immediately. Expiry and cancellation are handled separately.
4. Service commitment and compensation
What we commit to is available time: while your subscription is active, the account assigned to you can handle your requests. If that account is disabled or deleted, you are moved to another account automatically when the plan you bought still has a free spot on another account; if none is free, service is interrupted and your service period is extended by the length of the outage. If authorization fails, your assignment stays on that account and requests fail until it is authorized again; the outage extends your service period the same way. If the account is paused after repeated errors or is rate-limited, you are not moved automatically; you can continue once it recovers. Reaching a usage limit does not move you to another account; just wait for the limit to reset.
When the account assigned to you cannot handle requests for more than 15 minutes in a row, that counts as an interruption. Requests fail with an error during it, and they are not charged against the monthly fee or your API credit.
Once service is back, contact support (support@relaysail.com) to have your period extended by the time actually lost, granted after review; for every 24 hours unavailable at most 4 extra hours. Compensation is capped at 7 days per calendar month; once the cap is reached, contact support for a refund or a different subscription.
Compensation is always service time, never cash, balance, or granted credit.
5. Usage limits and fair use
On shared plans, the account's usage limits (the 5-hour and weekly limits) are split evenly among the people on that account, and your share is 1/N of the total. Your console shows in real time what you have used and what your share is.
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, a quarter on a four-person plan. 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.
6. Account and acceptable use
One subscription is for one person. Do not resell it, sublet it, or let several people use the same spot at once; that can lead the provider to judge the subscription account as shared and suspend it. Keep your credentials safe; usage from a leaked credential is the holder's responsibility, and you can revoke any device or API Key from the console at any time.
Do not use the service for anything unlawful where you are, or in breach of the upstream provider's own policies. If an upstream provider restricts or disables an account over such a breach, that interruption is not covered by clause 4.
7. Upstream dependencies
This service is built on third-party AI providers. Their prices, models, quotas and policies are outside our control; when they change, we adjust our accounts as quickly as we can and notify affected users.
When an account becomes unusable for provider-side reasons, clause 4 governs whether you are moved automatically and how you are compensated. If a plan cannot be delivered for a sustained period, we will contact you to arrange a refund or a move to another plan.
8. 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). There is currently no fixed deletion date for the archive. For long responses, only the beginning and the end are kept.
Your requests are forwarded to the relevant upstream provider, whose own policies govern their handling of that data. When we turn on content safety checks, the text of your latest message is sent to a third-party moderation service. The checks cover requests in API credit mode, including requests that switch to API credit once the subscription limit is reached. Ordinary API relay requests are not checked. Requests judged to be prohibited may be refused. Your account email is used only for sign-in, verification codes, and status notifications for this service.
9. Changes to these terms
When the User Agreement changes, you will be asked to accept it again the next time you open the console. If these terms change, continuing to use the service means you accept the change. Adjustments to price or to the service commitment apply to a running subscription from its next billing period.
If you have a question about these terms, or believe a recorded interruption does not match what you experienced, please contact support (support@relaysail.com).