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

@marcelodesignx (Marcelo Design X, Marcelo Cedeño), verified X account, publicly reports that their Instagram account (marcelodesignx) was permanently disabled on August 17, 2025 as a cascade from a Facebook account that allegedly didn't follow the rules. No policy was cited. Support told the reporter to create a new account and start from zero. The account, which was a major income source, had been active for five years with no reported TOS violations. The reporter explicitly connects the enforcement to 'the first wave of Meta pushing AI into everything.'

REPORTED_BY
@marcelodesignx
PLATFORM
Meta
ENFORCEMENT_ACTION_TYPE
account-disable
Terminal state — platform offered no further review
PLATFORM_POLICY_CITED
Bare citation; no specific policy domain named
AI_SYSTEM_INVOLVEMENT
DETECTION
Curator inference, not verified fact — see basis below
DATE_FROM / DATE_TO
Aug 17, 2025
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 2, 2026

Sources

Curator commentary

Oldest incident in the dataset by a significant margin — August 17, 2025 predates all other records by more than 8 months. This is a pre-wave record: the reporter attributes the enforcement to 'the first wave of Meta pushing AI into everything,' placing this incident at the beginning of an observable enforcement pattern rather than within the May–June 2026 concentration. Facebook→Instagram cascade with null policy: the Instagram notice identifies 'Marcelo Cedeño / Facebook / Doesn't follow the rules' as the cause but cites no specific policy. Consistent with [[finding___enforcement-notice-policy-opacity]]. Permanent disable: 'We've disabled your account' — no Appeal button visible, only Log out and Download your information. The 'How we made this decision' link (shield icon) is present in the notice, same UI element as PA-2026-0013 (AprilHunter); expanding it may reveal the 'our technology took action' language documented in that record. Appeal access confirmed lost: support explicitly told the reporter they 'couldn't do anything' and to create a new account — the most direct documented instance of Meta support declining to assist in the dataset. Five-year account, 0 TOS violations, major income source — harm profile similar to PA-2026-0013 (AprilHunter) and PA-2026-0024 (@korn). Source is a reply post made in June 2026 to an existing PA record source — the first documented instance of a reporter entering the dataset via engagement with another dataset subject's post. Confirmed quote tweet of PA-2026-0024 (@kornbuilds) — visible in the tweet context. Screenshots and archive captured by @vhsdev on 2026-06-02, curator: @vhsdev.

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