Privacy Policy

We're going to keep this quick and simple.

We don't collect any identifiable information about you, nor the portals you access on HubSpot. We do track the number of installs, uninstalls, current number of users with the app installed, and impressions. These statistics are all provided and stored by Google.

We may track events, for example, if you click a button or use a keyboard shortcut in the extension we may log it with the purpose of identifying the most commonly used features and identify features that are not being used. We do not track any interactions outside of the extension's popup, options screen, and injected developer menu. We use Google Analytics and basic stats that the Google Chrome developer dashboard provides.

Broken down very simply we track(or plan to track):

• views of the extension popup
• views of the Options page
• clicks to all of the buttons on the Debug Tab
• clicks to all of the buttons on the Develop Tab
• We have the "demographics" feature of Google Analytics installed, this is to get an idea of the types of people that develop on the HubSpot platform. Though for extensions this functionality is more limited in what it can do than the normal version of the feature.
• Interactions with the toggle switches on the Develop Tab.
• Interactions with the developer Menu
• Error and bug data All of this data is stored anonymized per the methods Google Analytics uses.

We do NOT track and do NOT plan to track:

• HubIDs
• any personally identifiable information.
• Your activity on any websites, including HubSpot (outside of the injected functionality we provide).

This data may be shared publicly only in aggregate and anonymized with the other developers involved in the development of this chrome extension, as well as with HubSpot. The data will never be personally identifiable or individualized.

If you would rather have a peak under the hood to keep the honest honest, we encourage you to take a look at the code and feel free to contribute.

Our long term plans are to try to use optional permissions whenever possible to add features that require a permission. This means you will not need to give the extension permission for most functionality that requires granting the extension permission until you want to actually use it. An example of a feature that will likely require this: We want to detect if you have the design manager for the same site open in multiple tabs so we can alert you, preventing you from accidentally overwriting your own code. This requires grabbing tab URLs and we hope we can do this as an optional permission.

Side Note: HubSpot developers know about and use the extension themselves. I say this because HubSpot theoretically if they want to, could track usage of some of the functionality of the chrome extension. They do log whenever the cache buster is used, that data is used to help them identify where the cache is failing to update. In other words you are making HubSpot better by using the extension. We could obfuscate the cache buster URLs to prevent them from tracking but we feel that no actual privacy is being affected by them having this data, and us as developers benefit from their work on improving the caching.