A website installed through Chrome can appear beside ordinary desktop applications. Before removing it, identify the service behind the icon and whether it holds any unsynchronised work. Removing a launcher and deleting browser-stored data are separate choices in the uninstall flow.

Check where the work exists

Open the app through its usual route and note the signed-in account. Save or synchronise outstanding work using the service’s supported process. If the app offers offline editing, check its pending-change indicator instead of assuming that recent edits already exist on the server.

Open the same service through a normal trusted browser address and inspect a representative document or record. Where practical, confirm its latest change on another authorised device. This checks the work’s availability beyond the installed app window.

Do not remove local data if it is the only visible copy of important work. Use the application’s documented export or support process to preserve it first. Chrome notes that web apps vary in how completely they function offline.

Read the uninstall options

Google documents management through chrome://apps and an Uninstall option in the web app’s menu. On desktop platforms, the removal dialog can include Also delete data from Chrome. Choose that only after understanding which local data the service uses and completing the required preservation checks.

After uninstalling, confirm the intended app entry is gone. Then open the service in a normal browser tab if continued access is required. A fresh sign-in may be necessary after local site data is removed.

Uninstalling a web app is not the same as closing the online account or cancelling a service arrangement. Handle those separately through the provider if that is the actual goal. Record the app name, account and data choice so a later user understands why the launcher disappeared and which access route remains available.

Sources: Chrome documentation.