On October 28, a Chinese-language post on X offered 18 rules for keeping your Claude account alive.
It claimed that Linux costs you points. That upgrading to Max too early is risky. That signing in on multiple devices hurts your account, while using Claude on mobile or enabling memory can help it.
The explanation behind all of this was a hidden score. According to the post, Anthropic assigns points to accounts, adjusts them as people use the product, and suspends accounts that fall below a threshold.
I understand why that caught on. If Claude Code is part of your workday, losing access halfway through a feature can be expensive. A list of 18 rules seems more useful than a policy page.
The post does not provide a leaked document, an observable score, or a reproducible experiment. I reviewed the claims against Anthropic's published documentation and its account-enforcement statistics. The suspensions are real. The specific points system is not publicly verified.
What Anthropic actually says about account bans
Anthropic's Transparency Hub says its Safeguards Team uses detection and monitoring systems to enforce policies. It can issue warnings, suspend accounts, or terminate access.
That establishes that enforcement exists. It does not tell us whether consumer accounts have a persistent numerical score, whether Linux has a negative weight, or whether a Max upgrade triggers an observation period.
Its safeguards and appeals documentation lists possible reasons for account bans, including repeated Usage Policy violations, account creation from an unsupported location, and violations of its Terms of Service.
A separate identity-verification article, dated August 11, 2026, confirms that some users may be asked to verify their identity or business for platform-integrity, safety, or compliance purposes. A verification prompt alone is not proof that an account is about to be banned.
Anthropic’s published enforcement numbers
For January through June 2026, Anthropic reported:
| Measure | Count |
|---|---|
| Banned accounts | 11.4 million |
| Appeals | 398,000 |
| Appeal overturns | 42,000 |
Source: Anthropic, System Trust and Reporting, last updated July 23, 2026.
The overturn count divided by the appeal count is about 10.6%. That is a ratio of two published numbers, not a measured false-positive rate.
We don't know how many people with erroneous bans never appealed, how enforcement categories are distributed, or whether every figure maps cleanly to unique individuals. The statistics show the scale of enforcement and the appeal process. They cannot establish the viral post's alleged scoring formula.
Checking the 18 claims against public documentation
Rather than publish the alleged point values as instructions, I grouped the 18 claims by what they ask users to change.
| Claim group | Evidence check |
|---|---|
| Starting score, thresholds, observation periods, forced logouts | Unverified. No published consumer score table or thresholds. |
| Email provider, IP quality, account age, payment method | Unverified weights. Account and region policies do not establish these bonuses or penalties. |
| Delay Pro; Max upgrades trigger monitoring | Unverified. No official evidence of a fixed upgrade penalty. |
| Mobile, desktop, memory, prepaid credits add points | Unverified. No documented rewards for these actions. |
| Multiple devices or Linux subtract points | Unverified. Claude Code officially supports Linux. |
| Concurrency, repeated prompts, network changes cause deductions | Unverified specifics. Exact triggers and weights are undisclosed. |
| Time zone, language, nationality have little effect | Unverified. Claims that variables are ignored also need evidence. |
| Heavy Claude Fable use subtracts points | Unverified. No public evidence of a product-specific deduction. |
This is an evidence check, not a claim that the underlying system works differently. Anthropic may use internal fraud or abuse signals that it does not publish. We simply cannot infer this particular formula from the available evidence.
The Linux claim is a good reality check
The post says Linux usage subtracts points. Anthropic's own Claude Code setup documentation provides Linux installation instructions, including Debian/Ubuntu and Alpine-specific guidance.
Official support does not prove that operating-system data could never be used in any safety system. It does mean there is no basis for telling developers to abandon a supported OS to protect an undocumented score.
I would not change my development environment based on that claim.
The Max story confuses sequence with cause
The post suggests that buying Max quickly, or upgrading to it, puts an account under observation.
Imagine a developer subscribes to Max and gets suspended the following day. That gives us an order of events, not an explanation. The account may have had an unrelated policy issue; the timing may be coincidental. Without a comparison group and evidence of the actual decision, assigning the cause to the upgrade is speculation.
That distinction matters when a thread recommends changing payment or subscription habits. A confident workaround is useless if the proposed trigger was never established.
IP changes and identity verification need separate treatment
Anthropic explicitly names unsupported-location account creation as a potential enforcement reason. You should verify whether your location and intended use are eligible under its Supported Regions Policy. As of this review, the linked page displays a version effective November 12, 2026, so check which policy version applies when you use the service.
That does not demonstrate a fixed penalty for switching between home Wi-Fi and mobile data, using a second computer, or going through an ordinary identity check. The list's advice about a particular proxy configuration is unsupported as account-safety guidance.
One useful detail from Anthropic's API documentation
There is a documented enforcement status in Anthropic's developer platform.
For businesses that attribute API requests to their own end customers, the User Profiles API documentation describes an enforcement_status field with these values:
unrestricted
restricted
banned
It also documents enforcement reasons such as unsupported_region, fraud_or_abuse, and usage_policy_violation.
These fields describe enforcement on API end-customer profiles. They are not evidence that your personal Claude account has a numerical score, and they do not expose any score or weights.
The public API shows how one kind of enforcement outcome is represented. It does not reveal the internal model that produced the outcome.
How I would assess a claim like this
A credible explanation of the purported scoring rules would need more than suspended-account screenshots and stories about what happened right before a ban.
At minimum, I would look for authenticated documentation, a clear official statement, or independently reproducible data with a defined sample. A credible study would have to separate subscription type from region, account age, actual policy violations, and other confounding factors. A convenience sample of people reporting bans online cannot establish the effect of one OS or subscription plan.
Nor should anyone intentionally trigger policy violations just to reverse-engineer enforcement.
What developers can do today
A disputed account rule is a poor reason to rebuild your workflow. There are a few precautions that pay off even if the viral thread turns out to be entirely wrong.
Keep the work in your repository. Commit code, configuration, and architecture decisions. Keep prompts or agent instructions that you need to reuse as versioned files. If a useful decision exists only in a chat transcript, write it down.
Keep verification independent of the assistant. For a .NET project, that may be as straightforward as a documented dotnet test command in CI, a reproducible build, and a short runbook for local setup. A teammate should be able to verify the project without signing into your AI account.
Export conversations when they matter. Anthropic documents Settings → Privacy → Export data for personal Free, Pro, and Max users on web or desktop. Its export guide also says you cannot import that export into a different personal Claude account. It is an archive, not a one-click migration tool.
Know the official appeal route. Anthropic directs banned users to sign in to Claude and submit the appeal form. Some export data may remain available after a ban, subject to restrictions described by Anthropic. The appeal form is more useful than changing operating systems in response to a rumor.
What I'd like Anthropic to explain
The transparency report is helpful, but developers still have questions. How often are suspensions later overturned? How quickly do users receive a review? How does the company identify and correct false positives? What information can it share about enforcement without making its safeguards easier to evade?
Those are reasonable requests even if the secret-score story turns out to be fiction.
If access to Claude vanished tomorrow, I would want my code, tests, build instructions, and project decisions ready to use elsewhere. I would spend time on that before following an 18-point account-survival ritual that nobody has verified.
Research note (October 29, 2026): The original X post is in Chinese; its 18 claims were cross-checked against a contemporaneous reproduction of the text and Anthropic's public documentation. Anthropic has not publicly confirmed the specific scoring mechanism alleged in the thread. The illustrations are conceptual, not screenshots of Anthropic's internal systems.
Top comments (0)