Privacy practices for every extension we ship

Amazon Price History

Amazon Price History runs only on Amazon product pages. When you open a product detail page at https://www.amazon.com/<...>, the extension reads two things directly from the page DOM: the product’s ASIN (the identifier in the URL) and the current visible price. It then writes one { price, timestamp, isRange? } record to your browser’s local storage under amazonPriceHistory.v1[<ASIN>]. That’s the entire record — price, when you saw it, and a tag if Amazon was showing a price range rather than a single number.

The extension never makes any network request. It does not call fetch, XMLHttpRequest, or WebSocket— not to Amazon, not to us, not to anyone. There is no cloud sync, no account, no login, and no analytics. Your price history lives only on the device where you installed the extension, and you can wipe it by clearing the extension’s storage or uninstalling it.

NinjaOne Tracker

NinjaOne Tracker is a paid Companion tool that overlays live per-ticket status timers on the NinjaOne dashboard. The extension stores one piece of information in chrome.storage.local: an installation identifier that the extension uses to confirm with extensionpay.com whether your install has an active Pro subscription. In plain English, this is the “license key” — the local token that tells the extension whether you’ve paid for Pro. Without it the extension runs in Free mode; with it, the Pro analytics overlay lights up.

The only third party the extension talks to is extensionpay.com. The extension loads ExtensionPay’s hosted SDK (https://extensionpay.com/extpay.js) in its background service worker and asks ExtensionPay whether your installation is paid. That single check is what unlocks Pro. Ticket data, notes, and the overlay state stay on your device in chrome.storage.local. They are never sent to us, to ExtensionPay, or elsewhere.

We don’t collect NinjaOne credentials, ticket contents, or any data from your NinjaOne dashboard. The extension has read access only to the page structure it needs to find ticket rows and overlay its timers; that DOM access stays in the browser.

ConnectWise PSA waitlist

The ConnectWise PSA add-on is on our roadmap and isn’t released yet. To notify interested teams when it ships, we accept email signups on /extensions, /connectwise-tracker, and /supported-sites. Submitting the form sends a single POST request with your email to /api/connectwise-waitlist on our own deploy origin.

Our server forwards that email to our team via Polsia’s email proxy and then sends you a confirmation message from the same system. We store the email address only long enough to notify you when the ConnectWise extension launches; the address is used for that single notification and no other purpose. It is never sold, shared, or used for marketing.

Sharing and selling

Across every extension and every surface on this site, we do not include advertising networks, third-party analytics SDKs, telemetry beacons, or fingerprinting scripts. The only outbound network call from any of our extensions is the ExtensionPay paid-status check described above — and that call carries only an installation identifier, never the contents of your browser, your tabs, or your data.

We do not sell, rent, share, or trade email addresses or any other user data with third parties. The briefest summary of this whole page: your data stays on your device, and the only thing that ever leaves it is the single ExtensionPay handshake that confirms a NinjaOne Pro subscription.