← Back to StoreSpy

Privacy Policy

StoreSpy is a Chrome extension that helps users analyze publicly visible eCommerce store signals directly in their browser. This Privacy Policy explains what information StoreSpy processes, how it is used, how it is stored, and what is shared outside the browser.

1. Information StoreSpy Processes

StoreSpy may process the following information when you use the extension:

Publicly visible page data

When you open the extension on an eCommerce website, StoreSpy analyzes publicly visible page data in your browser, such as:

• Page HTML and metadata
• Public scripts and resource URLs
• Public store platform signals
• Theme and app signals
• Public tracking and analytics signals
• Public product data where available
• Contact links, social links, and payment method signals

StoreSpy does not access private account pages, admin dashboards, passwords, payment card details, checkout information, or private customer data.

Scan history and watchlist data

StoreSpy may store scan results locally in your browser, including:

• Store domain
• Detected platform
• Detected app and theme signals
• Public tracking signals
• Public product signals where available
• Scan timestamps
• Change history between scans
• Watchlist entries selected by the user

This information is used to provide store history, watchlist, CSV export, and change tracking features.

License and account activation data

If you activate StoreSpy Pro, the extension may process your email address to verify your license or subscription status.

2. How StoreSpy Uses Information

StoreSpy uses the information above only to provide the extension's core functionality, including:

• Detecting public eCommerce store signals
• Showing platform, app, theme, product, payment, and tracking information
• Saving local scan history
• Comparing changes between scans
• Managing a local watchlist
• Exporting scan data to CSV
• Verifying Pro license status

StoreSpy does not use this information for advertising, profiling, creditworthiness, or unrelated purposes.

3. Local Storage

Most StoreSpy data is stored locally in your browser using Chrome local storage.

This includes scan history, watchlist data, settings, and license status. This data remains on your device unless you remove the extension, clear browser storage, or delete the data inside the extension.

4. External Requests

StoreSpy does not send scan history, browsing history, page content, or detected store data to StoreSpy servers.

The only external request made by StoreSpy's own service is for Pro license verification when you activate Pro. This may include your email address and license status request.

StoreSpy may also observe publicly loaded network requests in the browser in order to detect public tracking and analytics signals visible on the current page. This is used only for the extension's detection functionality.

5. Data Sharing

StoreSpy does not sell, rent, or transfer user data to third parties.

StoreSpy does not share browsing history, scan results, page content, or watchlist data with third parties.

License verification may be handled through a payment or subscription service provider only for the purpose of confirming Pro access.

6. Data Retention

Local scan history, watchlist data, settings, and license status remain stored in your browser until you delete them, clear browser storage, or uninstall the extension.

StoreSpy does not maintain a server-side database of your scan history or watchlist data.

7. User Control

You can remove locally stored StoreSpy data by:

• Clearing extension storage in Chrome
• Removing the extension
• Clearing browser site and extension data
• Using the "Clear history" option inside the extension's History tab

8. Permissions Explained

• activeTab — Required to read the currently open tab's URL and run the scanning script.
• scripting — Required to execute the store analysis script on the active page.
• storage — Required to save scan history, watchlist, and license status locally on your device.
• host_permissions (<all_urls>) — Required to analyze publicly visible page signals on websites where the user uses StoreSpy. This allows StoreSpy to detect store platforms, app signals, public tracking signals, and changes between scans. Scan results are stored locally in the user's browser and are not sent to StoreSpy servers.
• webRequest — Required to detect publicly loaded tracking and analytics requests visible in the browser. This is used only to identify public tracking signals for the current scan.

9. Third-Party Services

StoreSpy Pro uses Polar.sh as its payment processor and subscription manager. When you purchase a subscription, Polar.sh's privacy policy applies to your payment data. StoreSpy does not receive or store your payment card information.

10. Security

StoreSpy is designed to process store analysis data locally in your browser where possible. StoreSpy does not access passwords, payment information, private account data, or admin-only content.

11. Children's Privacy

StoreSpy is not directed at children under 13. We do not knowingly collect any information from children.

12. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated effective date.

13. Contact

If you have questions about this Privacy Policy, contact us at support@clingogo.com.