Post-Disable Identity-Level Enforcement

Post-Disable Identity-Level Enforcement

Evidence

• PA-2026-0040 (@discovenus_ / @discovenus) — instant new-account suspension after terminal disable: Reporter states: "every new account I create gets instantly suspended." Context: Instagram account @discovenus was terminally disabled May 29, 2026 after two prior appeal grants were overridden. The instant suspension of newly created accounts implies enforcement signals are propagated beyond the account identifier (username, account ID) to something persistent across account creation — device fingerprint, IP address, phone number used for verification, email address, or a combination. The report is verbal (stated in the X post); no screenshots of the new-account suspensions were provided. Confidence in this specific feature is lower than for the primary terminal disable, which is screenshot-confirmed.
• PA-2026-0049 (@ThaisEscufon) — second reported case, recurring over a longer period: Reporter states in a video that her Instagram account was disabled (~January 2026) and that she has been unable to create a new account under her own name or likeness since, describing roughly a dozen separate enforcement actions against her accounts over time. Same evidentiary structure as PA-2026-0040: the terminal disable itself is screenshot-confirmed, but the repeat-blocking claim is reporter-stated only, with no screenshots of the subsequent new-account suspensions. This is a second independent account reporting the same failure mode (inability to re-register under one's own identity after a terminal disable), which is the specific condition this finding's "Notes for Future Records" flagged for monitoring — worth weighing in any confidence-level review, though the underlying evidentiary gap (no corroborating screenshots) is identical to the first case.

Context

• Meta's account-level enforcement architecture — suspend, review, disable, appeal — is designed to act on specific accounts. The account is the unit of enforcement; the suspension or disable notice names the account; the appeal process is accessed through the account's credentials. PA-2026-0040 introduces a reported failure mode that operates above this layer: after a terminal account disable, new accounts created by the same user are reportedly being instantly suspended. This suggests the enforcement system is applying a persistent signal at the device, network, or identity level that flags any new account creation by that user for immediate enforcement — before any content or account-level behavior has occurred.
• This failure mode has no documented appeal path within Meta's standard enforcement UI. A terminal disable forecloses account-level review; identity-level enforcement against newly created accounts would face the same terminal-disable mechanism with no higher authority to appeal to. The practical consequence is that a user subject to identity-level enforcement cannot create a new account and use the platform — they are effectively permanently excluded regardless of account identity.
• Post-disable identity-level enforcement, if confirmed, represents a qualitative escalation from account-level enforcement. Account-level enforcement can be escaped — imperfectly — by creating a new account; identity-level enforcement cannot. The enforcement systems known to operate at above-account levels include:
• Device fingerprinting: Browser/app fingerprints used to associate new accounts with a previously enforced device. Meta's devices API and app-level device identifiers can persist across account creation.
• Phone number enforcement: Meta requires phone verification for new accounts; a phone number previously associated with a disabled account may be flagged for immediate suspension of any new account registered to it.
• IP-range enforcement: IP addresses or ranges associated with prior enforcement may be monitored for new account creation. Less precise than device fingerprinting and would affect other users on shared IP ranges.
• Name/identity matching: New accounts using the same name, email, or other identity signals as a previously disabled account may trigger automated detection before any content is posted.
• None of these mechanisms are documented in Meta's public policies as part of the standard enforcement framework. The standard enforcement notice and appeal architecture addresses account-level actions only. There is no publicly documented appeal mechanism for identity-level enforcement.
• The instant suspension timing — "gets instantly suspended" — is consistent with automated detection executing on account creation signals rather than post-creation behavior. This is analogous to the pre-content detection documented in PA-2026-0010 (@heybrosai, Facebook Business Ad Account disabled before any advertisement was published), but applied to personal accounts post-terminal-disable.
• Low. The primary terminal disable (PA-2026-0040) is SOURCE_CONFIRMED (enforcement screenshot present). The new-account instant suspension is reported verbally in the X post without supplementary screenshots. It has not been independently corroborated. The finding is flagged for documentation at low confidence. Confidence should be upgraded if: (a) screenshots of new-account suspension notices are obtained from the reporter; (b) the reporter describes the mechanism in more detail (which identity signal — phone, email, device — triggers the instant suspension); or (c) additional records document the same pattern.
• Flag any report of new-account instant suspension following a prior terminal disable. Key data points: which identity signal appears to be the trigger (phone number, email, device, IP); whether the new-account suspension notice cites the same policy as the original disable; whether the reporter has access to an appeal mechanism for the new account. Cross-reference with re enforcement after successful adjudication for cases where the same enforcement mechanism targets the same account across multiple cycles.

Significance

• If confirmed at scale, post-disable identity-level enforcement would represent the most severe account-access failure mode in the dataset. All other documented failure modes operate within the account-level enforcement architecture and leave open — at least nominally — the creation of a new account. Identity-level enforcement removes that option. For accountability research, this matters because: (1) no due process mechanism is documented for identity-level enforcement; (2) the mechanism is not disclosed in Meta's public enforcement policies; (3) it would make terminal disables practically irreversible regardless of whether the underlying enforcement was accurate. The finding warrants monitoring for additional cases before conclusions about prevalence or policy basis can be drawn.