GOOGLE · SUN PARK · INSTITUTIONAL FIRST READ · 22 SEPTEMBER 2026

Preserve the audit trail. Keep the platform lanes separate. Test attribution from native records.

This page gives Google a finite, source-bounded route into incidents affecting Sun Park's customer-facing digital identity. It does not allege wrongdoing by Google and does not attribute a platform event to a named person without provider-side evidence.

Public-safe cooperation brief · evidence gaps open

Essential boundary. Google Business Profile / Maps events and Google Account / Gmail security events are different systems and different evidential lanes. Their appearance in one preservation brief does not prove a common actor, common device, shared intent, causation or criminal responsibility.

What the current record establishes

Five bounded facts; no shortcut to attribution.

2019 · customer-facing identity

SUN PARK Gmail communication

A preserved copy records a message from a Gmail account presenting itself as SUN PARK to a historical customer. A Google recovery screen displayed a masked clue compatible with the acostamatos.com domain. The complete recovery address and account controller are not established.

2021–2022 · Business Profile

Three management requests

Google notices identify requests concerning the Sun Park profile on 28 October 2021, 24 February 2022 and 20 June 2022. The notices associate them with Lourdes Castillejo / MYND labels and one requester account. All three documented requests were rejected.

2022 · platform state

Closed, then reinstated

The existing manager received closure notifications; a management capture displayed the profile as permanently closed. Google later confirmed reinstatement in support case 5-5076000032482. The record does not identify what caused the closed state.

2023–2026 · recurring profile state

Later closure/change notices

Connected records include a closure notification on 16 December 2023, a profile-change review notice on 28 June 2024 and another closure notification on 8 January 2026. Each requires provider-side change-source and actor logs before causal attribution.

2026 · account security

Separate security alerts

September 2026 records include security alerts for a recovery-linked personal account and a separate business Google account. They are recorded for preservation only and are not attributed to any person connected with the Business Profile incidents.

Current procedural context

R33 party filing

The insolvency administrator's 14 September 2026 opposition in RPL 3304/2025 is public as a party filing. It does not adjudicate the Google events and does not show that Google participated in, knew of or endorsed any alleged conduct.

System separation

Two lanes, two routing paths, one preservation discipline.

Lane	Current identifiers / events	What is not established	Official Google route
Business Profile / Maps	Legacy profile reference `14170251100259548565`; manager/account reference `4924927283255745814`; location reference `3783157971025960551`; action IDs `19740425`, `24008448`, `26176867`; support case `5-5076000032482`.	Who operated each device; what documents were supplied; what event caused a closure; whether any rejected request caused a later state.	Profile restriction appeal · Business redressal guidance
Google Account / Gmail security	2019 masked recovery clue; 2026 passkey and sign-in alerts retained in the private source corpus.	The full 2019 recovery address; account creator/controller; IP, device, session or actor; any connection to the Business Profile state changes.	Secure a compromised account · Investigate suspicious activity

The official links identify current user-facing routes; they do not replace a lawful preservation request or provider response where competent authorities seek native records.

Finite preservation and verification request

Native records can answer questions the public copies cannot.

Business Profile / Maps

Preserve the complete profile, manager, owner, request, verification, appeal, support and change histories for all listed identifiers.
Preserve action-level timestamps, source channel, account, session, IP/device indicators and documents submitted for action IDs 19740425, 24008448 and 26176867.
Identify the source and audit event for each closure, reopening, reinstatement and material profile change from 2021 through 2026.
Preserve case 5-5076000032482, attachments, internal notes, routing and decision metadata.

Google Account / Gmail

Preserve creation, recovery-option and security-change history for the relevant accounts, subject to lawful process and privacy controls.
Preserve sign-in, passkey, device, session, IP and recovery-flow records for the documented incident windows.
Keep the 2019 recovery-clue question separate from the September 2026 security alerts unless native records establish a connection.
Provide records only through the correct lawful, authenticated channel; this public page is not a demand for disclosure of private data to the public.

Requested outcome. Confirm the correct intake owner, preserve the identified records, assign a reference, and state what formal process a rights-holder or competent authority must use to obtain an authenticated audit trail.

Prosecutorial-forensic lens · controlled connections

Reverse-engineer the mechanism, then test the alleged wider pattern.

DOC · 2016Professional records and notice concerning Sun Park.

HIP · 2018Alleged material-control and funded-exit sequence; not adjudicated here.

DOC / OPEN · 2019Customer-facing Gmail identity plus unresolved native attribution.

DOC / GAP · 2021–26Profile requests, closure states, reinstatement and security events.

NOTICE · 2026Complaints, removal litigation and R33; notice does not prove merits.

Proof ceiling. The chronology permits preservation and comparison. It does not prove a single author, agreement, conspiracy, unlawful purpose, causal chain or offence. Each proposed arrow must be tested by native records and contrary evidence.

Digital-identity hub →2019 incident →2021–2022 requests →2018 control allegation →R33 party filing →