Claude account suspended? Appeal, export your data, and plan your next step

Choose your situation

1. You received a personal suspension or termination notice

Open Anthropic’s safeguards guide, sign in with the affected account and follow its appeal link. Explain the facts you want reviewed. Keep the submission confirmation, if provided.

2. Your organization is on hold

If your personal account still works, use Request a review beside the affected organization on the restricted screen. This is a separate route from a personal-account appeal. See organization holds.

3. You cannot log in at all

Open the official Help Center, use its lower-right message control and choose I can't login. Explain which login step fails. The documented logged-out assistance covers exports, deletion and subscription issues; do not treat it as a verified substitute for the appeal form.

If you cannot reach that form, say so explicitly and ask which contact route applies. A drafted message is not a submitted appeal.

4. You received a warning, not a ban

Use the contact under Warnings in the safeguards guide. Describe the disputed warning. API warnings may concern account-wide activity; do not assume the last prompt caused it.

5. Identity verification failed

Follow the identity-verification instructions. Check that your original ID is valid, readable and undamaged, and retry within the verification flow if attempts remain. If they are exhausted, use the help form linked there. A subsequent ban is a different issue: consult the appeal guidance.

Do not send identification to Cue, a public forum or an unofficial “recovery agent.” Start any verification from the official product or help page, not an unsolicited message. Failed verification alone does not establish why an account was later restricted.

6. The mobile app reports an incorrect age

The mobile age-restriction article covers app-store age information, including a staged rollout in certain US states. For incorrect information, it directs iOS users to Apple Support and Android users to Google Play Support. Follow that correction route; do not invent a birth date or treat these instructions as applying to every access restriction worldwide.

7. Claude Code or an API request stopped working

Record the product, authentication method, organization, exact error and time zone. For API requests, retain the request ID—not the API key. The API error reference distinguishes authentication, permission, rate-limit and server errors. An HTTP error by itself is not evidence of a suspended account.

Check the official status page for incidents affecting the service you use. A green status page does not resolve an individual account restriction. If your notice explicitly identifies a suspension or organization hold, return to that route above.

Before retrying an interrupted coding task, inspect the repository diff, test results and any external actions already performed. Do not replay a deployment, payment or message merely because the client lost its connection. This is a workflow precaution, not an Anthropic recovery procedure.

8. You paid before losing access

Treat account review, cancellation and refund eligibility as separate requests. Find the purchase platform and receipt, then use the billing section below. Paying for a plan is not proof that a restriction must be reversed.

9. You submitted a request but have no reply

Keep the timestamp and case reference. Check the original support conversation and account email. Anthropic advises using the existing conversation rather than opening duplicate support requests. See support follow-ups.

We found no universally guaranteed time limit for an appeal response or decision in the reviewed guidance. If a channel permits replies, add genuinely new information there. Do not invent a deadline or pay someone claiming a guaranteed faster decision.

10. Your appeal was rejected

Read the decision for any specific next step. We did not establish a universally available second-appeal process. If you have new evidence and an existing channel accepts replies, ask whether it can be considered. That is an editorial suggestion, not a promise of reopening. Keep export, billing and work-continuity questions separate from the review outcome.

11. You need your conversations or files back

For banned Free, Pro and Max accounts, the safeguards guide describes export options after sign-in, but accessible data can be restricted. Check what your account actually offers; do not assume a complete archive.

For ordinary personal-account exports, use Settings → Privacy → Export data on the web or Claude Desktop, not the mobile apps. The emailed download requires sign-in and expires after 24 hours; an expired link can be requested again. Team and Enterprise exports require the organization’s Primary Owner. See export instructions.

After downloading, open the archive locally and check the specific conversations and attachments you need. Note missing items instead of claiming a successful full migration. An export request, an email and a verified usable archive are three different states. Store sensitive material securely and retain only what you are authorized to keep.

Prepare your request

This is our suggested preparation checklist, not a list of mandatory official form fields:

• Product and affected account; organization and your role if relevant.
• Exact notice and the date, time and time zone it appeared.
• What you were actually doing, without speculation about detection systems.
• Specific facts that you believe need reconsideration.
• Existing case reference and whether you can sign in.
• The outcome you are requesting: review, clarification, export assistance or billing help.

Remove passwords, API keys, session tokens, unrelated conversations and other people’s information. Provide payment identifiers or identity documents only when the official process requests them. Do not upload the preparation checklist to this page or to an AI tool if it contains private account details.

Before submitting, replace every bracketed field, remove claims you cannot support and verify the destination. Only report “submitted” after the official interface confirms submission. Save the confirmation privately. We have not tested these routes using a suspended account.

Copy a template

Use accurate facts, not persuasive inventions. These templates are not official wording and do not guarantee a particular outcome.

English: request a review

Subject: Request to review an account restriction — [case reference, if any]

My [product/account] received [exact notice] on [date, time and time zone].
My actual use was [accurate, concise description].
I am requesting a review because [specific facts or evidence].
My existing case reference is [reference, or “none”].
I [can/cannot] sign in. [Describe any obstacle to opening the review form.]

Please review this decision and tell me what further information is needed.
If access cannot be restored, please explain the applicable data-export
and subscription-support options.

中文：申请复核

主题：账号限制复核申请 — [已有工单号，如有]

我的[产品/账号]于[日期、时间及时区]收到[准确通知]。
实际用途是[简明、真实的用途]。
我希望复核的依据是[具体事实或证据]。
已有工单号为[编号或“无”]。
目前我[可以/无法]登录。[如无法打开复核表，请准确描述障碍。]

请复核此决定，并说明还需要哪些补充材料。
如暂不能恢复，请告知适用的数据导出和订阅处理途径。

English: add new evidence to an existing case

Regarding case [reference], I have the following new information:
[New fact, date and supporting material available through an approved channel.]
It is relevant because [explain the connection to the original issue].
Please let me know whether this information can be considered and whether
you need anything further. I understand that this does not guarantee reopening.

中文：补充新材料

关于工单[编号]，我补充以下新信息：
[新增事实、日期，以及可通过官方认可渠道提供的证明材料。]
它与原问题的关系是[具体说明]。
请告知是否可以纳入复核、是否还需其他材料。
我理解提交补充材料不代表工单必然重开或恢复账号。

For an organization hold, add the organization and your actual role; do not speak for teammates’ unknown activity. For a login obstacle, request directions rather than claiming an appeal was filed. For billing, specify the purchase channel and request eligibility review without inventing an order number.

Check billing separately

For web or desktop purchases, open Get help → Send us a message → Accept → Claude Refund Request and follow the eligibility prompts. If account access is unavailable, use official support. For iOS purchases, Apple handles refunds through Report a Problem. For Android purchases, Claude support checks eligibility; keep the Google Play receipt available. These are request routes, not refund guarantees. See Claude’s refund guidance.

For cancellation, use the platform where you subscribed. Web/desktop subscriptions use Settings → Billing → Cancel; mobile subscriptions use the relevant store’s subscription controls. Anthropic advises cancelling at least 24 hours before renewal. Verify the cancellation confirmation and next billing status. Do not assume an appeal or an app uninstall has cancelled renewal. See cancellation instructions.

Protect unfinished work

While you wait, make a small handoff note from material you already possess and are authorized to use. Do not bypass account restrictions to obtain unavailable data. Keep the full export private; copy only the minimum necessary context into another approved tool.

Goal:
Authorized source material and dates:
Verified facts:
Actions already completed and their results:
Unknown or missing information:
Next requested step:
Output format:
Human checks before using the result:
Actions that must not be performed:

A fictional practice task

Input—use this non-sensitive example, not an actual account notice:

Goal: Draft a short project update for human review.
Source: My fictional Cedar project note, October 3, 2026.
Facts: 12 of 20 invited testers completed product onboarding. Eight did not.
Maya will review the permission wording on October 6, 2026.
Unknown: Why all eight did not finish; whether the wording change will help.
Completed actions: None beyond writing this note.
Next step: Draft an update under 100 words, with one open question.
Do not send it, invent causes, or describe the planned change as successful.

Expected example—written by the editor, not a Cue or Claude execution result:

Twelve of 20 invited testers completed product onboarding; eight did not. Maya will review the permission wording on October 6, 2026. We have not established why all eight did not finish or whether a wording change will improve completion. Open question: What additional feedback should we collect before deciding on a change?

Check the counts, date, owner and distinction between facts and unknowns. Reject any invented cause or claim that the update was sent. If the draft is wrong, correct the source note and request a revision before using it.

Cue is one possible workspace for a separate, authorized task—not an account-recovery service. Choosing a hosted model inside Cue and connecting an external Claude Code agent are different paths. Check the models, plan and permissions shown in your installed app; an external agent may have separate authentication and billing. Neither path restores a suspended Anthropic account or automatically transfers its history.

Related reading: Claude Fable 5.1 in Cue · Cue and Claude: compare the workflows.

Our view: safeguards need meaningful recourse

Cue editorial opinion: We oppose mistaken suspensions and unexplained work interruptions without effective review. Anthropic should give users clear, trackable ways to challenge decisions, understand what can be disclosed, recover eligible data and resolve subscriptions. Safety enforcement should not make meaningful recourse an afterthought.

Anthropic already documents appeals and conditional exports; our criticism does not imply those channels are absent. Its Transparency Hub, updated July 23, 2026, reports 11,400,000 banned accounts, 398,000 appeals and 42,000 decisions overturned on appeal for January–June 2026. Those figures do not establish an October suspension wave, a false-ban rate or your chance of recovery. We do not use unverified community reports as proof of any individual decision’s cause or fairness.