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

@DylanOFM publicly reports that Meta permanently disabled their Instagram account @dylanofm, reportedly in approximately March 2026, citing bare "Community Standards" with no specific policy identified. Reporter states the account had 40,000 followers and was their primary business income source, with over $500,000 spent on Meta advertising. No email notification, no in-app appeal option, and no review form were provided. Meta support agents reportedly promised manual escalation and an appeal option — neither materialized. Meta subsequently reinstated multiple linked accounts following identity verification, telling the reporter the original action was an error, but @dylanofm remains disabled with no appeal path. Reporter raises the Meta AI/support exploit as a possible cause.

REPORTED_BY
@DylanOFM
PLATFORM
Meta
ENFORCEMENT_ACTION_TYPE
account-disable
Terminal state — platform offered no further review
PLATFORM_POLICY_CITED
Community Standards
AI_SYSTEM_INVOLVEMENT
DETECTION
Curator inference, not verified fact — see basis below
DATE_FROM / DATE_TO
Mar 26, 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
Jun 26, 2026

Sources

Curator commentary

One of the most analytically significant records in the dataset for two reasons. First, Meta support agents have partially acknowledged the enforcement was an error — reinstating linked accounts and telling the reporter "We're sorry we got this wrong" — yet the primary account @dylanofm remains disabled with no appeal path. This is the clearest documented case in the dataset of Meta internally confirming error while simultaneously failing to remediate it, creating a durable false-positive outcome. Second, the reporter explicitly raises the Meta AI/support exploit as a possible cause — the absence of a disable notification email is consistent with account access being changed via support-side flows before the disable. Curator cannot confirm the exploit was the mechanism, but the symptom pattern (no email, no prior warning, support agents unable to locate what triggered the action) is consistent with it. A $500K+ Meta advertiser with 40K followers receiving a terminal disable with no appeal path and no notification is also a strong data point for the systematic appeal access failure pattern in this dataset. The bare "Community Standards" citation with no section is consistent with the enforcement notice opacity pattern. The no-notification pattern is one of the clearest no-warning statements in the dataset — reporter explicitly states "No email. No in-app appeal option. No review form."

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