SNAPBOARD

Uninstalling Snapboard

Last updated 2026-08-29

What happens when you uninstall

When you remove Snapboard Toolkit from HighLevel, whether you published your theme Agency-wide, to a Location group, or to just This sub-account only: when HighLevel tells us the app was uninstalled, we immediately delete our access credential and stop serving your themes. If a theme ever keeps rendering after uninstall, remove the pasted code in HighLevel under Settings, Company, Custom JavaScript, and it stops instantly.

What we keep

Your theme drafts and their full version history stay in your Snapboard workspace. Nothing is deleted on your side of the product. If you reinstall later, reconnecting restores your work, you do not have to rebuild your theme from scratch. Uninstalling from HighLevel also does not cancel or otherwise touch your Snapboard subscription; that is billed and managed separately from your HighLevel connection.

What we delete

We delete the HighLevel access credential tied to that connection. Once it is gone, we have no way to reach your HighLevel account until you reinstall and reconnect. We do not delete your theme configuration, drafts, or history, see "What we keep" above.

Removing a manually pasted loader

If Snapboard's Custom JavaScript loader was pasted into HighLevel by hand instead of installed through the Marketplace, uninstalling the app does not remove that pasted snippet, HighLevel treats it as your own code. To fully remove it, go to Settings, then Company, then Custom JavaScript inside HighLevel, and delete the Snapboard snippet there.

Not sure if it's the theme? Check without uninstalling

Append ?css=false to the end of any HighLevel page URL in your browser to load that page without Snapboard's theme applied, just for that tab. It is a quick way to tell whether something you are seeing is caused by your theme or by HighLevel itself, with no uninstall or reinstall required.

Related pages

See our Privacy Policy for the fuller detail on what we store, or Support if uninstalling does not resolve what you were trying to fix.