SRProject Sun RockDigital incident · Lourdes / MYND

STANDALONE DOSSIER · UPDATED 22 SEPTEMBER 2026

Lourdes / MYND incident: requests to control Sun Park's Google Business Profile

This dossier deals only with requests which Google associated in 2021–2022 with Lourdes Castillejo / MYND and a specified requester account preserved in the source record. Native-source review now closes one important question: all three documented requests were rejected. The separate 2019 customer-account episode remains on its own page.

What is now documented directly by Google

28 October 2021Google notified a request associated with Lourdes Castillejo, role “Business owner”, using mynd.hotels@gmail.com.
Outcome: rejected.
24 February 2022Google again showed Lourdes Castillejo, now as “Employee”, using the same Gmail account.
Outcome: rejected.
20 June 2022Google identified another request as “MYND Hotels, Employee”, again using mynd.hotels@gmail.com.
Outcome: rejected on 20 June.

All three original notices have now been located in connected email as direct provider messages and their authentication headers were reviewed. The three share the same technical Sun Park profile reference on Google's side, while each carries a distinct action identifier. That improves traceability, but does not by itself identify the person physically using the device or the actual controller of the requester account.

PUBLIC_DERIVATIVE_INTEGRITY_FAILED · visual withheld from display.

The previously embedded public derivative is retained in repository history for preservation, but an integrity check found that its current public bytes do not provide a reliable readable image. It is therefore no longer displayed or relied on as evidence. It has not been reconstructed, regenerated or silently replaced. The provider messages and controlled textual record remain the source for the three rejected-request propositions; a new visual may be published only from authenticated source material with a new provenance record.

An essential distinction.

Google displaying “Lourdes Castillejo” or “MYND Hotels” on a request does not yet prove who physically submitted it, who controlled mynd.hotels@gmail.com, which IP or device was used, what documents were supplied, or whether Lourdes personally authorised use of her name. Contemporaneous February-2022 correspondence expressly kept open the possibility that a third party may have used her name without consent.

After the rejections: the profile appeared as closed and Google reinstated it

  1. 22 June 2022: a native Google email told the existing manager that Sun Park was marked as closed on Google.
  2. 30 June 2022: a contemporaneous management capture showed “You manage this Business Profile” and Sun Park as “Permanently closed”; Google also showed that a suggestion that the place was open was under review.
  3. 15 July 2022: Google again notified the existing manager that Sun Park was marked as closed.
  4. 26 August 2022: in support case 5-5076000032482, Google confirmed that, from the information supplied, it had reinstated the Business Profile and that no further verification action was required at that time. Google added that, once live again, the profile might take a few days to reappear in Search.

We do not attribute causation. The three reviewed ownership/management attempts were rejected. The later closed state and Google's need to reinstate the profile document a real platform-state sequence, but do not prove that Lourdes, MYND, Canarian Hospitality, HNT, CAM or any of those three requests caused it. Google's native audit/change-source records are required to identify the mechanism.

Later profile-state records. The connected corpus also contains a closure notice dated 16 December 2023, a profile-change review notice dated 28 June 2024 and a further closure notice dated 8 January 2026. These later notices are documented platform events, not proof of who caused them. They are consolidated—together with the separate 2026 Google Account security lane—in the Google cooperation brief.

What genuinely remains to be resolved

  • Who created and administered mynd.hotels@gmail.com, and who authenticated each request?
  • Which IP, device, session or Google account originated each request?
  • Which entity was being represented, and what title, authority, employment or ownership document was supplied?
  • Which event, user, public suggestion, API, manager action or Google process caused the “Permanently closed” state?
  • Did any requester later use a verification route separate from the three rejected requests?
  • If Lourdes did not personally make one or more requests, who used her identity?
Related incident, published separately

Two years earlier there is a different digital episode: an email from sunpark264@gmail.com to a Sun Park customer and a Google-displayed recovery clue compatible with the acostamatos.com domain. The renewed search still has not located the native 2019 original with full transport headers. We do not claim common authorship.

Open the 2019 Sun Park incident →

Open the Google evidence-preservation and cooperation brief →

Read the open letter to Lourdes Castillejo →

Editorial control: the rejections are documented platform facts; they are not proof of a crime. The later “closed” state and Google's reinstatement likewise do not identify the actor or cause. Google is not presented here as having made a finding of fraud or impersonation. CAM, HNT, Canarian Hospitality, MYND and individuals remain legally distinct. Corrections, explanations and evidence that confirms or contradicts this reconstruction are invited.