Ask the data

← All incidents

Why “reports”: this record captures what the affected person publicly said happened and what the platform’s own enforcement notice showed. The source is archived below. The platform has not acknowledged this action ( platform_acknowledged: false). See methodology.
PA-2026-0059 Meta Account disable Source confirmed Draft

@jamesbyrne_180 publicly reports that Meta permanently disabled their Facebook account of 18 years on June 12, 2026, reportedly citing 'Terms of Service on who can use Facebook' with no specific behavior identified, no prior warning, and no explanation. Reporter states the underlying issue was a problem with their email address which has since been resolved, and that no content in violation of Facebook's standards was posted. The enforcement notice confirms at least one prior review cycle occurred ('still doesn't follow') before terminal closure. No further review is available.

REPORTED_BY
@jamesbyrne_180
PLATFORM
Meta
ENFORCEMENT_ACTION_TYPE
account-disable
Terminal state — platform offered no further review
PLATFORM_POLICY_CITED
Terms of Service on who can use Facebook
AI_SYSTEM_INVOLVEMENT
DETECTION
Curator inference, not verified fact — see basis below
DATE_FROM / DATE_TO
Jun 12, 2026
VERIFICATION_LEVEL
SOURCE_CONFIRMED
Enforcement notification screenshot present in source
PLATFORM_ACKNOWLEDGED
false
CONFIDENCE_SCORE
4 / 5
Rubric: enforcement notification + archive confirmed
ENFORCEMENT_SCREENSHOT
Enforcement notification screenshot ↗
SCHEMA_VERSION
1
CREATED_AT
Jun 26, 2026

Sources

Source 1 https://x.com/jamesbyrne_180/status/2070280438065602857 Archive https://archive.ph/2026.06.26-131028/https://x.com/jamesbyrne_180/status/2070280438065602857
Curator commentary

Third record in the dataset citing 'Terms of Service on who can use Facebook' (after PA-2026-0011 and PA-2026-0012), adding to [[finding___enforcement-notice-policy-opacity]]. The terminal disable follows at least one prior review cycle — confirmed by the 'still doesn't follow' template language — without the reporter being informed what conduct was at issue at any stage. Reporter attributes the cause to an email problem that was subsequently resolved, suggesting an account authentication or verification trigger rather than a content violation. The reporter's explicit AI attribution ('When you take humans out & replace them with AI that is fcuking up repeatedly') is one of the cleaner direct AI attribution statements in the dataset, alongside the 'If a human checked they would realise the error' framing. An 18-year Facebook account receiving a terminal disable with no explanation and no surviving appeal path, with the reporter confirming the underlying issue was resolved, is a strong false-positive indicator. Adds to [[finding___appeal-access-failure-patterns]] (Mode 6 — terminal disable forecloses review) and [[finding___no-suspension-notification]] (reporter states no warning was received before the action).

Research patterns

All findings →
This record contributes evidence to the following cross-incident findings.
  • Appeal Access Failure Patterns high confidence

    Meta's automated enforcement actions are frequently followed by appeal processes that fail to provide meaningful review — through inaction, access barriers, or structural lockout.

  • Enforcement Notice Policy Opacity high confidence

    Platform enforcement notices frequently omit specific policy citations or use policy language too broad to identify the triggering behavior — leaving affected users without an actionable basis for understanding or appealing the enforcement decision.

  • No Suspension Notification high confidence

    In at least one documented case, Meta terminally disabled an account without sending any notification — no email, no in-app message received outside the disable screen itself. The affected user had no knowledge the action had occurred until encountering the enforcement screen directly. The absence of notification is structurally distinct from the absence of a specific policy citation: a user who receives no notification cannot begin an appeal, cannot preserve data in time, and cannot know to seek help. In a terminal disable context — where appeal is already structurally foreclosed — the notification failure compounds the harm by removing the only remaining avenue for the user to understand what happened and when.

Experienced something similar? See Resources for escalation paths by jurisdiction—EU/DSA, India, Turkey, and more. For US-based cases, Signal Flare covers the full stack: state Attorneys General, the FTC, and congressional offices.

This record is published under GDPR Art 89 public interest exemption. Data policy

Are you the subject of this record? Request erasure