STANDALONE DOSSIER · 6 JUNE 2019
2019 Sun Park incident: sunpark264@gmail.com and a recovery clue compatible with @acostamatos.com
This dossier deals only with the email sent to a historical Sun Park customer and the Google account-recovery screen preserved on the same date. The later Lourdes / MYND incident of 2021–2022 is published separately and linked as a related episode.
The customer email
On 6 June 2019, a preserved copy records a message sent under the name SUN PARK from sunpark264@gmail.com to a historical customer of the complex. The message told the customer to remove belongings because Sun Park would shortly be refurbished.
The preserved response from the historical operation challenged the legitimacy of that Gmail address on the same day and asked that the information be retained. The customer explained that he and others had written their email addresses on their luggage after being instructed to do so.
The preserved copy documents a Gmail account presenting itself as SUN PARK and communicating directly with a customer about belongings and an impending refurbishment. It does not establish who created the account, who controlled it, who physically wrote the message or what authority the sender had to speak as Sun Park.
The Google recovery clue
In a preserved Google recovery capture for sunpark264@gmail.com, Google's interface displays this partially masked clue:
ros••••••@aco••••••••.comFact: that string appears as provider-generated text in the preserved screen. Limited inference: the pattern is compatible with the domain acostamatos.com. Limit: the capture does not reveal the complete email address or identify the person or entity that created, controlled or used the account.
During the contemporaneous check a full address under the acostamatos.com domain was typed into the form. That address was entered by the person conducting the test and must not be treated as a value confirmed by Google. The human identity associated with the recovery account remains unresolved.
Questions for native evidence
- What exact recovery email was configured on 6 June 2019?
- When was that recovery address added or changed?
- Who created and administered sunpark264@gmail.com?
- Which IP addresses, devices and sessions used the account?
- Who sent the customer message and where did the contact data come from?
- What instructions existed concerning luggage, customers and future refurbishment?
- What relationship, if any, existed between the account and people or companies in the Acosta Matos perimeter?
See the Acosta Matos perimeter →
Editorial control / CR-031: no complete recovery address is published as Google-confirmed data and no specific person is publicly identified from the masked pattern. Technical attribution requires native provider records.