platform_acknowledged: true). See methodology.
PA-2026-0018 covers two enforcement events against the same work Instagram account (myelitetrader.com_, Elite Scope Traders). Event 1 (prior to April 13, 2026): account disabled for Community Standards on account integrity; reporter submitted government ID; account restored April 13 with Meta explicitly acknowledging error ('We're sorry we got this wrong'). Event 2 (May 29, 2026): same account disabled again under the same policy, with no further review possible. @KeBranny (Brian Michael G) publicly reports the second disable on May 30, 2026, noting the prior disable and restoration as context.
Sources
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
Are you the subject of this record? Request erasure
Two-event enforcement record against the same work Instagram account (myelitetrader.com_, Elite Scope Traders), a financial trading content account. Event 1 (prior April 13, 2026): account disabled for Community Standards on account integrity. Reporter submitted government ID as part of verification. Account restored April 13, 2026 — the first documented account restoration in the dataset. Meta's restoration email explicitly acknowledges error: 'We're sorry we got this wrong and that you weren't able to use Instagram for a while.' This is also the first case in the dataset where identity verification (government ID) produced a restoration outcome, in contrast to all other identity-verification records (PA-2026-0006, -0014, -0015, -0016, -0017) where verification produced no restoration. Event 2 (May 29, 2026): the same account was disabled again under the identical policy (Community Standards on account integrity), with no further review possible. The April 13 restoration and the May 29 re-disable are separated by approximately 46 days, making this a weeks-scale re-enforcement pattern — distinct from the minutes-scale re-enforcement documented in PA-2026-0007 (Cholatak: restored → re-suspended within ~5 minutes). The re-enforcement under the same policy after an explicit Meta apology raises a structural question: if Meta reviewed the account in April and found it compliant ('the activity on it does follow our Community Standards on account integrity'), what changed between April 13 and May 29 to trigger another disable under the same policy? Possibilities include: new activity that re-triggered detection, a persistent signal that the April review did not fully clear, or an inconsistency between the review subsystem that restored the account and the detection subsystem that re-flagged it. platform_acknowledged set to true: Meta's April 13 restoration email constitutes an explicit platform acknowledgment of enforcement error. First record in the dataset with confirmed platform_acknowledged: true. Other cascade notes: personal Instagram (branny_ke) not disabled in either event; Facebook (Brian Michael) shows as Locked; Threads (branny_ke) and second Instagram (branny.2) show as Deactivated in May 29 Profiles panel — enforcement vs self-deactivation ambiguous. Screenshots and archive captured by @vhsdev on 2026-05-30, curator: @vhsdev.