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-0011 Meta Account disable Source confirmed Draft

@JoshCGames publicly reports that Meta permanently disabled their Facebook account on approximately May 29, 2026, reportedly for violating Terms of Service on 'who can use Facebook,' with no prior warning and no specific offending action identified. The reporter states the account had been active since 2009. The disable notice confirms a review was conducted and upheld with no further review possible. The reporter's Instagram account was also disabled as a result of the same enforcement action.

REPORTED_BY
@JoshCGames
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
May 29, 2026
VERIFICATION_LEVEL
SOURCE_CONFIRMED
Enforcement notification screenshot present in source
PLATFORM_ACKNOWLEDGED
false
CONFIDENCE_SCORE
4 / 5
Rubric: enforcement notification + archive confirmed
SCHEMA_VERSION
1
CREATED_AT
May 29, 2026

Sources

Curator commentary

First 'Terms of Service on who can use Facebook' citation in the dataset — distinct from all prior Community Standards citations. Meta's ToS on 'who can use Facebook' covers identity, age, and account authenticity requirements (e.g. one personal account per person, real identity, minimum age). This is a more identity-focused policy category than behavioral or content-based Community Standards citations. The notice format ('We reviewed your account and found that it still doesn't follow') is the review-denied-then-permanent-disable variant also seen in PA-2026-0010, suggesting a prior suspension with a review stage before this final notice. The reporter states no prior warning or Facebook Jail period preceded the permanent disable, and that no specific offending action was ever identified. Account since 2009 (~17 years) with no prior history of enforcement adds to the misclassification signal. Confirmed Facebook→Instagram cascade: full post text reads 'Not just my FB. But my Instagram as well? Sheesh.' — second Facebook-primary cascade to Instagram in the dataset, following PA-2026-0005. Both cascades originate from Facebook enforcement propagating to a linked Instagram account. See [[finding___cross-platform-cascade-enforcement]]. No separate Instagram enforcement notice was captured. Source credibility: 12 X followers and a gaming-specific handle (@JoshCGames) suggest X is not the reporter's primary platform; identity corroborated by Facebook notice naming the user as Josh, consistent with reporter display name 'Josh C.' Follow-up observation: reporter subsequently noted 'I had a couple backups' — suggesting they had created backup accounts prior to or following enforcement. This is noteworthy because Meta's 'Terms of Service on who can use Facebook' (the policy cited in this record) explicitly prohibits multiple personal accounts. If the enforcement was triggered in part by backup account creation, this would represent a feedback loop: enforcement paranoia drives backup account behavior, which triggers the classifier that enforces the policy. This pattern — users adapting to enforcement risk by creating backups, inadvertently satisfying the detection criteria — warrants tracking across records as a potential behavioral finding.

Research patterns

All findings →

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