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-0029 Meta Account suspend Source confirmed Draft

@gerardvanschip (Gérard van Schip, 🇳🇱🇯🇵), publicly reports that their Facebook account (Gérard) has been suspended for approximately two months as of June 3, 2026. An appeal was submitted on April 27, 2026 and remains pending over five weeks later despite Meta's stated review time of 'just over a day.' No policy is cited. The reporter also reports receiving scam phishing emails targeting them during the suspension, exploiting the account's vulnerable state.

REPORTED_BY
@gerardvanschip
PLATFORM
Meta
ENFORCEMENT_ACTION_TYPE
account-suspend
Account access restricted, not permanently removed
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
Apr 1, 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 3, 2026

Sources

Curator commentary

Suspension date approximate: reporter states 'going into month 2' as of June 3, 2026 with appeal submitted April 27, placing the suspension start in approximately early April 2026. date_from set to 2026-04-01 as a floor — exact date unknown. Null policy citation: appeal pending screen cites no policy, consistent with [[finding___enforcement-notice-policy-opacity]]. Appeal timing failure: appeal submitted April 27, still pending June 3 — 37+ days despite Meta's stated 'usually just over a day' review time. This is the most extreme appeal delay documented in the dataset and is consistent with [[finding___appeal-access-failure-patterns]]. Secondary harm documented: reporter describes receiving 'endless offers to restore access for cash (impossible) and hack attacks from dozens of fake Facebook emails that match my X name but not my actual Facebook name.' The phishing emails using the X name rather than the Facebook name confirms the reporter's identity linkage and demonstrates that suspended account holders are targeted by social engineering actors exploiting the enforcement gap. This predatory secondary harm is not captured in the current schema but warrants documentation. European account (Dutch-Japanese flags 🇳🇱🇯🇵) — a Dutch-based account would be subject to GDPR, under which enforcement without a stated legal basis and without timely appeal response may raise compliance questions. This is noted as analytical context, not a legal finding. 2 X views — lowest reach post in the dataset. Name consistency: 'Gérard' in the Facebook appeal notice, 'Gérard van Schip' as X display name — the reporter explicitly discloses the X/Facebook name difference as a phishing detection signal, confirming the Facebook name is 'Gérard' (surname not visible). Check passes. Screenshots and archive captured by @vhsdev on 2026-06-03, curator: @vhsdev.

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