Usage policy · the condition for post-sales cover

Hold to these three ground rules and your account stays stable, your cover stays in force

No reselling on, one person per account with no sharing, a dedicated static residential line plus rule-based routing and TUN. Run your own network environment lawfully, lower the risk of account controls, and keep ccrelay's post-sales cover genuinely in force.

Read the first ground rule Go straight to the setup guide
  1. Do not resell it on Do not use tools such as sub2api to wrap your account into an API for others. Ground rule
  2. One person per account, no sharing No lending it out, no forwarding credentials, no concurrent sign-ins from several places. Ground rule
  3. A dedicated static residential line A residential exit plus rule-based routing plus a TUN virtual adapter — all three, none optional. Ground rule

Ground rule 01 · no reselling on

Do not resell your account or usage environment on, wrap it into an API for others, or redistribute it

You already have a dedicated access environment for using Claude stably and compliantly. Keep it for your own use: do not layer another tool on top of it to resell the account on, wrap it into an API for others, or redistribute or hand it on to anyone else.

Why

Tools of the sub2api kind turn a web signed-in state into API calls in bulk, which produces requests far more frequent and concurrent than ordinary human use and makes the account's access pattern plainly abnormal. It is the most classic trigger for risk controls there is.

What to do instead

Use Claude directly through your dedicated access environment — conversations, file uploads and tools, just as you would officially. If you need a command line, use the Claude Code CLI and follow the setup guide so that it takes the same residential egress.

If you break this

A ban or rate limit caused by reselling on, wrapping into an API for others or redistributing falls outside ccrelay's no-ban assistance and compensation and is yours to bear; ccrelay may also suspend the account concerned.

This is the most important one

If you resell the account on, wrap it into an API for others or redistribute it to anyone, ccrelay may suspend the account, and any ban or rate limit that follows counts towards no cover at all.

Ground rule 02 · one person per account

Your account, used only on your own device

The signed-in state of one Claude account should exist on exactly one clean device. Do not lend it out, do not forward credentials, and above all do not have several people, places or devices signed in to the same account at once.

Why

Concurrent sign-ins from several places make one account show access from different locations and different egresses within a short time, so the pattern plainly contradicts itself. It is one of the easiest behaviours to flag as abnormal.

What to do instead

Account, device and egress line up one to one: one person, one device, one dedicated residential egress. When the person or the device has to change, first clear what is left on the old device as the setup guide describes, and only then sign in on the new one.

If you break this

A ban or rate limit caused by sharing, lending out or concurrent use from several places is not within ccrelay's no-ban assistance and compensation and is yours to bear.

Before changing person or device

Always clear the signed-in state and cache on the old device first, as the setup guide describes, so that two devices never hold a session for the same account at the same time. See clean up the local environment.

Ground rule 03 · one fixed, dedicated egress

A dedicated static residential line + rule-based routing + TUN — all three, none optional

All traffic that reaches Claude must leave through the one residential egress allocated to you, and it must do so every single time. Get all three pieces in place and the browser and the command line take the same fixed egress; the routing is whitelist-shaped, so domestic traffic keeps going direct and is unaffected.

Why

An egress IP that keeps jumping about (residential today, a datacentre tomorrow, another city the day after), or a browser on the residential line while the command line goes out on a bare IP, makes the access pattern flicker. That is far riskier than staying on one residential IP.

What to do instead

Use the dedicated static residential line as the last hop of the chain; the one-click script's whitelist-shaped routing sends all traffic reaching Claude through it by default (anything not named falls through to the residential line, so newly added official domains leak nothing); then turn on the TUN virtual adapter so it takes over the command line and git. All three are required — how to set them up is in the setup guide.

If you break this

A ban or rate limit caused by mixing a datacentre IP with the residential line, or by an inconsistent egress, is not within ccrelay's no-ban assistance and compensation and is yours to bear.

How to set it up

The full steps and self-check commands for the chained proxy (residential exit) plus rule-based routing plus the TUN virtual adapter are in set up the chained proxy.

Post-sales and cover

What is covered and what is not

Covered (compliant use)
  • Holding to the three ground rules: no reselling on, one person per account, a dedicated static residential line plus rule-based routing plus TUN.
  • Always going out through the same residential egress allocated to you, with the egress fixed and consistent.
  • Using it at an ordinary human pace, and when something looks wrong, stopping first and then investigating against this policy or contacting us.
Not covered
  • Using tools such as sub2api to resell the account on, wrap it into an API for others or redistribute it.
  • Sharing or lending out the account, or signing in to it concurrently from several places or devices.
  • Mixing a datacentre IP with the residential line, or changing the egress often so that it is inconsistent.
  • Scripted high-frequency requests, heavy concurrency in a short time and other abnormal bulk activity.
  • Force majeure such as upstream policy changes or changes in account policy.

Replacement accounts and compensation in a particular case follow your plan and the service agreement; see Services.

Compliance self-check

Run through it before you start, and the account holds steadier

All seven ticked means you are running your own network environment lawfully, keeping the risk of account controls as low as it goes — and post-sales cover is in force with it.

# Look up the public egress IP and who it belongs to (org / ISP should be a residential line, not a datacentre ASN)curl https://ipinfo.io# Or just the IPcurl ifconfig.me# On PowerShell, if curl is missing, use:# (Invoke-RestMethod https://ipinfo.io).ip   or   curl.exe ifconfig.me

FAQ

Common questions about the usage policy

Why is the policy this strict?

The aim of all this is for your account to be used the way an ordinary residential user uses one: one fixed egress, no switching between networks, no mixing environments, no abnormal bulk activity. The steadier and more predictable the access pattern, the lower the chance of the account meeting risk controls — and that is also what post-sales cover rests on.

Can I lend it to a colleague once in a while?

We advise against it. Even letting one other person sign in on another device briefly makes the same account show two egresses and two behaviour patterns at once — exactly the classic trigger for risk controls. If someone else needs it, have them use their own account and their own egress.

Does it have to be a static residential line? Would a datacentre IP do?

Please use a dedicated static residential line. The ASN a datacentre IP belongs to is easily recognised as non-residential, and such IPs are often shared by a great many accounts, so the risk is markedly higher. One fixed residential egress is the core of this policy.

If a breach gets the account banned, can it be replaced?

A ban or rate limit caused by reselling on, wrapping into an API for others or redistributing, by sharing, lending out or concurrent use from several places, by mixing a datacentre IP with the residential line, or by scripted bulk activity is not within ccrelay's no-ban assistance and compensation and is yours to bear. What is covered when you use the Service compliantly follows your plan and the service agreement.

How do I confirm I am compliant?

Go through the seven items in the "Compliance self-check" on this page one by one: no reselling on or wrapping into an API for others, one person per account, a dedicated static residential line in use, rule-based routing plus TUN configured, the browser and the command line on the same egress, and what was left on the old device cleared before you switched. The setup steps themselves are in the setup guide.

Language versions

This page is published in English and in Chinese. In the event of any inconsistency between the two versions, the English version prevails.

Hold to all three

Hold to the three ground rules and the account holds steadier

Go to the setup guide Contact us