A seven-part evidence model
This framework is designed to make a complex account restriction easier to review. Not every category applies to every case, and more documents do not automatically create a stronger response.
| Evidence class | Question answered | Representative material |
|---|---|---|
| 1. Notice | What exactly did the platform state? | Complete notice, enforcement date, affected feature and stated deadline. |
| 2. Ownership | Who controls the account? | Identity, company authorization, account identifiers and verification requests. |
| 3. Timeline | What happened and in what order? | Dated account events, transactions, communications and previous submissions. |
| 4. Operations | What process or control existed? | Fulfilment, quality, security, moderation or compliance procedures. |
| 5. Transaction | What commercial activity is relevant? | Orders, payouts, invoices, source-of-funds records and affected transaction details. |
| 6. Correction | What changed after the issue was identified? | Corrective action, new controls, removed access, updated records and monitoring. |
| 7. Route | Where should the response be submitted? | Available appeal, verification, support or escalation channel and follow-up record. |
How to use the framework
Begin with the complete notice. Select only categories that answer the stated concern. Remove passwords, authentication codes, private keys and full payment-card data. The framework organizes a case; it does not override a platform’s rules or guarantee a decision.
Citation
Account Suspension Editorial Team. “The Account Suspension Evidence Framework,” version 1.0, July 29, 2026.