Cleanup and Uninstall

Cleanup and Uninstall

Uninstalling GhostlyShare removes the installed package or app files. It does not guarantee that user settings, logs, cached Cloudflare tunnel files, saved custom-domain tokens, or other local app data are removed automatically.

Windows Desktop

If you installed GhostlyShare from the Microsoft Store, uninstall it from Windows Settings:

Settings -> Apps -> Installed apps -> GhostlyShare -> Uninstall

If you installed GhostlyShare with GhostlyShareSetup_win-x64.zip, uninstall it from Windows Settings or from the uninstaller entry created by the setup package.

Windows CLI

GhostlyShareCLI_win-x64.zip contains a standalone ghs.exe. Delete the extracted folder or file to remove the CLI.

If you added that folder to PATH, remove it from your user or system environment variables as well.

Ubuntu, Debian, Kali, Linux Mint, Pop!_OS

Remove the desktop package:

sudo apt remove ghostlyshare

Remove the CLI package:

sudo apt remove ghostlyshare-cli

Remove both:

sudo apt remove ghostlyshare ghostlyshare-cli

Arch Linux

Remove the desktop package:

sudo pacman -R ghostlyshare

Remove the CLI package:

sudo pacman -R ghostlyshare-cli

Remove both:

sudo pacman -R ghostlyshare ghostlyshare-cli

Fedora, RHEL, Rocky Linux, AlmaLinux

Remove the desktop package:

sudo dnf remove ghostlyshare

Remove the CLI package:

sudo dnf remove ghostlyshare-cli

Remove both:

sudo dnf remove ghostlyshare ghostlyshare-cli

openSUSE

Remove the desktop package:

sudo zypper remove ghostlyshare

Remove the CLI package:

sudo zypper remove ghostlyshare-cli

Remove both:

sudo zypper remove ghostlyshare ghostlyshare-cli

RPM Signing Key

Importing RPM-GPG-KEY-GhostlyShare adds the GhostlyShare release key to the RPM trust database. Removing the packages does not necessarily remove that imported key.

Most users can leave the imported public key in place. If you need to audit or remove RPM keys, use your distribution's RPM key management tools and verify the exact key before deleting anything.

Package Files vs. Local App Data

Package files are installed system-wide by the Windows, DEB, Arch, or RPM package. Local app data is stored in your user profile and can include settings, logs, cached files, stored custom-domain token entries, and GhostlyShare-managed cloudflared data.

On Linux, user state is usually stored under:

~/.local/state/GhostlyShare

If XDG_STATE_HOME is set, GhostlyShare uses:

$XDG_STATE_HOME/GhostlyShare

On Windows, user data is stored under the normal per-user application data locations for GhostlyShare.

Exact files can vary by version and platform.

Managed Cloudflare Files

GhostlyShare may manage its own downloaded cloudflared binary, tunnel cache, token storage, settings, and logs.

When GhostlyShare closes normally, it attempts to stop the Cloudflare tunnel processes it started. If the app is force-killed or the computer shuts down abruptly, cleanup may not finish.

GhostlyShare only removes files and processes it manages. It does not remove system-wide cloudflared installations that you installed separately.

Stored Custom-Domain Tokens

Custom-domain API tokens are stored through the platform credential store when available:

• Windows uses Windows credential storage.
• macOS uses Keychain.
• Linux uses Secret Service through secret-tool.

Package uninstall commands remove GhostlyShare binaries. They do not guarantee that stored credentials are removed from the platform credential store. Use GhostlyShare settings or your platform's credential tools if you need to remove stored custom-domain tokens.

Before Manual Cleanup

Use cleanup or token-removal options in GhostlyShare settings if they are available. When deleting files manually, only remove data that clearly belongs to GhostlyShare.

Never post tokens, passwords, private URLs, or logs with secrets in public issues.