The screenshots and the uploaded video together prove that active, independent read and write access existed from both accounts to the same duplicated dataset on the backend.
Evidence package Attached: • screenshots from both accounts, with different prompt IDs but identical content • Drive log of the 20:43 backend‑level creation • video recording(https://www.youtube.com/watch?v=LOblGT519cU&t=4036s) of the ghost session running at 20:55 • both prompt URLs (/u/0/ and /u/1/) • timestamps proving that the user performed no action during the replication period This is a closed, verifiable chain of evidence. The fact that the old chat reappeared without user interaction, together with the backend‑automatically regenerated prompt that the system assigned to another account, clearly constitutes a backend isolation failure. No available user‑facing function or action can trigger this behavior. There is no operation in the Google AI Studio interface that could produce this phenomenon. If Google claimed in court that “the user must have copied it,” the only legitimate question would be: with which button? There is no button called “Copy to other account.” There is no button called “Transfer to other tenant.” There is no button called “Clone into another user’s workspace.” Even Drive sharing cannot create such an internal AI Studio prompt under another account.