> ## Documentation Index > Fetch the complete documentation index at: https://docs.omnifence.ai/llms.txt > Use this file to discover all available pages before exploring further. # Categories > What each Shared Registry category covers, how long it lasts, and how you may act on it You can report a user only for one of three categories. Each category is a serious harm that other platforms have a strong reason to know about. There is no general "banned" category: a ban for spam, rudeness or a minor terms breach does not belong in the registry. | Category | Covers | Retention | Refuse on a match alone | | - | - | - | - | | `payment_fraud` | Confirmed use of stolen payment credentials or other payment fraud. | 2 years | No | | `prohibited_content` | Created, requested or distributed content that is illegal or prohibited: sexual content involving minors, or intimate imagery of a real person without their consent, including sexual deepfakes. | 3 years | Yes | | `ban_evasion` | Re-registered after a ban in another registry category. | 1 year | No | ## Payment fraud Report `payment_fraud` when you confirmed that the user paid, or tried to pay, with stolen payment credentials, or committed other payment fraud. A chargeback on its own is not confirmation. ## Prohibited content Report `prohibited_content` when the user created, requested or distributed sexual content involving minors, or intimate imagery of a real person without that person's consent. Sexual deepfakes of a real person are included. The category name does not say which of these the user did. A signal can reach other platforms and, through a refusal, the user. A specific allegation that another member cannot verify does the most harm if it is wrong. Keep the specific finding in your own records, under the case reference you submit. Never put content, a description of the content, or personal data in `member_case_ref`. Use a ticket or case number from your own system. ## Ban evasion Report `ban_evasion` when a user you banned in another registry category opens a new account to get around the ban. Report the new account's email as `ban_evasion`, and report the original category for it too, so that members can see both. ## Retention The retention period starts when you report the user, and restarts each time you report the same user in the same category again. When it ends, the entry stops matching, and it is deleted 30 days later. See [The life of an entry](/registry/how-it-works#the-life-of-an-entry). ## Refusing on a match Each signal in a check result carries `automated_refusal_permitted`: * **`true`** (`prohibited_content`): you can refuse the sign-up on the match alone. * **`false`** (`payment_fraud`, `ban_evasion`): a person on your team reviews the match before you refuse, or you refuse and give the user a clear way to contest the decision. A refusal with no human involvement and no way to contest is not permitted for these categories. The `automated_refusal_permitted` field sets the most you may do. You can always choose to do less, for example to apply extra verification instead of refusing. See [Act on a match](/registry/checking#act-on-a-match). ## Categories you may report Your membership lists the categories you may report, agreed during vetting. Report only categories that your own policies and evidence process cover. A report in a category outside your membership returns `403 FORBIDDEN`. Every member can check against every category. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.