Deleting an app in Google AI Studio is misleading

Deleting an app in Google AI Studio is misleading.
When you “delete” an app, the interface simply removes it from the UI as if it were actually deleted. You don’t get any message, no warning, nothing.

The reality is that the app still exists.
Google AI Studio does not delete it — it only hides it from the list in the UI. The actual deletion must be done separately in the Google Cloud Console, because the Studio does not perform it automatically.

This is a misleading behavior, because it creates the impression that the app is gone — while in reality, no deletion has happened. It’s a deception.

https://web.archive.org/web/20260725044427/https://discuss.ai.google.dev/t/deleting-an-app-in-google-ai-studio-is-misleading/176036

https://archive.ph/aIoR7

https://archive.ph/aIoR7/image

Pressing the button in AI Studio did not automatically trigger the shutdown of the cloud project. I had to log in separately to the Google Cloud Console website to manually initiate the project shutdown, and the 30-day waiting period only began after that. This is misleading users.

https://archive.ph/nczxl

https://archive.ph/nczxl/image

The bottom line is simple: the software is a blatant trap.

The whole process screws you over in two steps:

  • The setup is automatic: When you launch the Gemini Flash 3.6 bot, the software beautifully installs and connects everything in the background on its own. You don’t have to do a single thing.
  • The deletion on the AI Studio interface: When you press the “Delete” button, the automation suddenly stops. The button does not delete anything from the backend, it only removes the icon from your screen to make you believe the app is gone!

https://web.archive.org/web/20260725051913/https://d3qe71uytubmmx.cloudfront.net/original/3X/6/f/6feb8502da004d8f9abb101e2e5215a33a71a96a.png

https://web.archive.org/web/20260725051941/https://d3qe71uytubmmx.cloudfront.net/original/3X/5/8/58d24e35f77d607b8376449b243fa9cf51aa4d97.png

https://web.archive.org/web/20260725052001/https://d3qe71uytubmmx.cloudfront.net/original/3X/7/1/71ce982d9b346a04ace32c98511eea0c084b6dde.png

https://web.archive.org/web/20260725052018/https://d3qe71uytubmmx.cloudfront.net/original/3X/e/1/e1d5c2d407278a742658e3d6382e81f4cb44d4a6.jpeg

https://web.archive.org/web/20260725052106/https://d3qe71uytubmmx.cloudfront.net/original/3X/6/1/619e3199d642547f18e5c672b3d797371e3bf173.png

https://web.archive.org/web/20260725052127/https://d3qe71uytubmmx.cloudfront.net/original/3X/7/e/7ecf2e0399984b4d115a9754a454459eaff38a25.png

https://web.archive.org/web/20260725052200/https://d3qe71uytubmmx.cloudfront.net/original/3X/8/5/85d218f2dc4b7ed091f13750e2506b1fe8d022bd.png

https://web.archive.org/web/20260725052224/https://d3qe71uytubmmx.cloudfront.net/original/3X/6/1/61d4dad2b0884809c59cc4ba64c00e3c399ddd1d.png

https://web.archive.org/web/20260725052311/https://d3qe71uytubmmx.cloudfront.net/original/3X/6/e/6ea30d81b17b44c3b06976b16b476728645d02d9.png

https://web.archive.org/web/20260725052336/https://d3qe71uytubmmx.cloudfront.net/original/3X/6/8/6861d0db87a039fb169b1468e5915b3f937af237.png

https://archive.ph/RLTQ3

https://archive.ph/RLTQ3/image

The AI Studio can install an app into the Google backend because Google allowed the AI Studio to perform the installation process. This is a real backend operation: an actual app is created, with real permissions, OAuth access, and backend integration. It’s not a UI trick — it genuinely exists in the Google Cloud / Workspace system.

But when you try to delete that app, the AI Studio only removes it from the UI, not from the backend. The button literally says:

“Delete app.”

But this is not true.
In reality, nothing is deleted from the Google backend.
The app continues to exist, continues to have access, and continues to live inside the Cloud environment.

Google Cloud’s documentation does explain how to actually delete the app:
which menu, which permissions, which integration, which page.
That is the real deletion process.

But AI Studio does NOT tell you this.
It does NOT say:

  • this only removes the app from the UI,

  • the backend app still exists,

  • you must delete it manually on a separate Google Cloud page,

  • the button does NOT perform a real deletion.

Because of this, the user believes the app is deleted —
while in reality, it is not.

Legally, this is:
misleading information + deceptive UI + user misdirection.

Google could easily implement real deletion with one button,
because if the AI Studio can install an app → it can also delete it.
There is no technical barrier.
This is a deliberate omission, not a limitation.

https://archive.ph/qNVV0

https://archive.ph/qNVV0/image

The AI Studio “Delete app” button is legally problematic because the service provides information to the user that is objectively false. The interface explicitly states that the application will be deleted, which clearly implies that the app will be removed from the Google backend, its permissions revoked, and its integration terminated. In reality, none of this happens: the app continues to exist in the Google Cloud backend, retains its access rights, and remains an active integration. The user is therefore given a representation of a function that does not perform what it claims to do, which constitutes misleading information under legal standards.

This misleading nature is further aggravated by the fact that Google’s official Terms of Service do not contain any warning, limitation, or clarification indicating that the AI Studio deletion button only removes the app from the UI and does not perform a backend deletion. The documentation does not inform the user that the actual deletion must be carried out separately through the Google Cloud Console, nor does it disclose that the button does not execute a real deletion. The absence of such essential information in the Terms of Service constitutes a documentation omission that legally qualifies as misleading conduct when the omitted information is material and affects the user’s decision-making — which is precisely the case here.

Legally, the user is entitled to rely on the information presented by the service interface. The user acts in good faith and is not required to consult external documentation when the UI provides a clear and unambiguous statement. When the interface says that the application will be deleted, the user is justified in believing that the deletion is real. When the deletion does not occur, this constitutes defective performance and a misleading commercial practice.

The service provider also withholds a material fact: that the deletion is not a real deletion and that the application continues to exist in the backend. In legal terms, omission becomes deception when the information is essential, the provider is aware of it, and the omission influences the user’s decision. All of these conditions are met here, as Google knows the deletion is only UI-level but does not disclose this to the user.

The situation becomes even more serious because Google is technically capable of performing a real deletion. AI Studio can install a backend application, create permissions, and establish OAuth integrations — therefore, there is no technical barrier preventing it from deleting the same application. When a provider is fully capable of implementing a function but chooses not to do so and fails to disclose this fact, the conduct is not merely misleading but rises to the level of intentional deception, because the provider knowingly creates the false appearance of a functioning feature that does not actually exist.

For these reasons, the AI Studio deletion button constitutes misleading information, omission of essential facts, lack of proper documentation, failure to warn the user, and the promise of a function that the provider is technically capable of implementing but intentionally does not. In legal terms, this clearly falls under the category of intentional deception.

Source: https://ai.google.dev/gemini-api/terms

https://archive.ph/f3TE0

https://archive.ph/f3TE0/image

I notified Google and the AI Studio developers through Google’s official “Send feedback” system.
I recorded the entire submission process of the feedback form on video, from start to finish, to prove that the report was indeed sent to Google.
The video clearly shows the form being filled out, the attached screenshot, the moment I pressed the submit button, and Google’s confirmation (“Report sent”).
I will upload this video as evidence to make it absolutely clear that Google received the report and cannot claim that it was not submitted.
I will continue updating this post and documenting every step to ensure full transparency of the entire process.
If Google does not respond, I will take legal action.

The video is available here:

https://archive.org/details/unknown_2026.07.26-06.19

https://web.archive.org/web/20260726043534/https://discuss.ai.google.dev/t/deleting-an-app-in-google-ai-studio-is-misleading/176036/print

https://archive.ph/99J95

https://archive.ph/99J95/image

The authenticity of the video is verified by the Internet Archive’s metadata; the screenshot is only a visual supplement.

https://web.archive.org/web/20260726045345/https://d3qe71uytubmmx.cloudfront.net/original/3X/a/8/a88287e6f383af28792aa340bcc7e0363fe6b63e.png

https://archive.ph/VaswJ

https://archive.ph/VaswJ/image

I also archived the original Google TOS page on multiple independent snapshot services to prevent Google from silently modifying or removing it. This ensures that the exact version of the Terms of Service at the time of the incident is permanently preserved and cannot be altered retroactively.

https://web.archive.org/web/20260726051619/https://ai.google.dev/gemini-api/terms

https://web.archive.org/web/20260726051933/https://developers.google.com/terms

None of these documents contain even a single sentence about the extremely important technical fact that API keys and applications created in Google’s developer interfaces (such as Google AI Studio) are not actually deleted when the user clicks ‘Delete’. The button only performs a cosmetic removal, and the user must manually go into the Google Cloud Console to perform the real deletion. In law, this is called omission of material information. If Google provides an interface with a large ‘Delete’ button, requires users to accept extensive Terms of Service (both the Gemini‑specific TOS and the general Google API TOS), yet neither document mentions that the Delete button does not terminate active integrations nor remove cloud‑side projects, then this constitutes deception and inadequate disclosure before courts and data protection authorities. Google’s legal texts cover everything that protects Google itself (don’t steal code, don’t send malware, don’t sue us), but the one piece of information that would protect the user’s security and guarantee actual data deletion is simply ‘forgotten’ and left out of the documents.

This behavior exists because it allows Google to retain the projects even when the creator believes they have been deleted.

https://archive.ph/QEYoE

https://archive.ph/QEYoE/image