DIGITAL IDENTITY · THREE ROUTES · UPDATED 22 SEPTEMBER 2026

Connected incidents. Separate proof. One controlled preservation route.

The record is divided by event, source and system. Functional proximity supports preservation and comparison; it does not establish common authorship, a single controller, shared knowledge, causation or criminal responsibility.

2019

SUN PARK customer-facing Gmail account

A message sent under the name SUN PARK and a Google recovery clue compatible with the acostamatos.com domain. Native account attribution remains open; the exact account is retained on the dedicated source page.

Open the 2019 dossier →

2021–2022

Lourdes / MYND Business Profile requests

Three Google notices associated requests concerning Sun Park with Lourdes / MYND labels and one requester account. All three documented requests were rejected; later profile-state causation is unresolved.

Open the 2021–2022 dossier →

2019–2026 · GOOGLE

Evidence-preservation and cooperation brief

A recipient-first reconstruction separating Business Profile / Maps from Google Account / Gmail security and identifying the finite native records required for attribution.

Open the Google cooperation brief →

How to read the record.

The 2019 customer-facing identity, the 2021–2022 management requests, later closure/change notices and 2026 security alerts are connected only at the level stated in each source. Each incident retains its own evidential burden. Google security events are not attributed to the persons or entities named in the Business Profile dossiers.

Open letter to Lourdes Castillejo → · Acosta Matos perimeter → · R33 party filing →


Control: this index preserves connections without collapsing distinct events, systems or actors into one narrative. Native provider records are required for technical attribution.