Greener Closet

Last updated: 2026-05-18

Browser Extension Privacy

This addendum to our site privacy policy describes what the Greener Closet browser extension sends, what we store, and what we never collect. It is written to be accurate against the code as shipped, not aspirational.

What extension requests send to our servers

When you visit a supported retailer's product page, or when you choose Analyze this page from the toolbar popup on another shopping site, the extension may call greenercloset.com to look up a score, queue an analysis, or record extension telemetry. Depending on the action, those requests send:

  • The product page URL you are viewing on the supported retailer or active tab you chose to analyze (canonicalized — tracking parameters are stripped before score lookup and analysis requests leave your browser). Badge and popup telemetry events send the page path or canonical URL they relate to.
  • The retailer name (for example, lululemon) derived from the page's hostname.
  • Extension telemetry details such as the event name, source: "extension", entry: "extension", and limited status metadata such as an error code or product ID when available.
  • An X-Extension-Version header identifying the installed extension version.

The extension runs automatically only on the retailer hostnames listed in its manifest. On other sites, it runs only after you click Analyze this page in the toolbar popup.

What our servers persist

Like any web request to our API, your browser also includes standard request metadata. We persist the following so we can debug failures, prevent abuse, and measure usage:

  • A SHA-256 hash of your IP address. We never store the raw IP in extension analysis jobs, analyzer logs, or telemetry events.
  • Your user-agent string (the browser/OS identifier your browser sends on HTTP requests).
  • Analyzer job and log fields including the canonical product URL, request timestamp, derived product domain, retailer, job status, and sanitized error code when an analysis fails.
  • Telemetry event fields including event name, path, extension entry/source tags, retailer, optional product ID, and sanitized metadata. The /api/events route may also generate an anonymous event ID for the event row.
  • Rate-limit records keyed by a hash of the route, IP address, and time window.

The website's optional-tracking choice does not apply to the extension, and the extension does not receive or send that preference. The website may use a first-party gc_anon_id cookie only after Analytics consent; allowlisted extension calls never set or reuse it. The extension has no PostHog or other third-party analytics SDK. Browser Do Not Track remains the extension telemetry control.

What we do NOT collect

  • Page content sent to our servers beyond the product URL and telemetry paths described above. The content script checks local page selectors to place the badge, but it does not transmit retailer page text such as prices, cart contents, or account state.
  • Cookies from the retailer site. The extension runs in an isolated context and cannot read retailer cookies.
  • Browsing history outside supported product-page use.The extension does not run automatically outside the supported retailer list. On other sites, it can access only the active tab you explicitly choose to analyze from the popup.
  • Your Greener Closet account or personally identifiable information. The extension does not bridge a signed-in greenercloset.com session into score lookup or analysis requests in this version.
  • Third-party tracking SDKs. The extension does not include analytics or advertising SDKs.

How we use this data

  • To return a score. We look up the canonical URL in our product database; if we do not have it yet, we analyze the page and store the result so subsequent visitors see a faster response.
  • To prevent abuse. The IP hash powers rate-limiting on the analyze endpoint.
  • To measure reliability and usage. We segment our internal dashboard by entry point (extension vs. web vs. share target) so we can see where the analyzer is failing.
  • To keep extension telemetry separate. Badge renders, popup opens, analyzer completions, and analyzer failures are tagged as extension events.

We do not sell this data, and we do not share it with third parties for advertising purposes.

Chrome Web Store Limited Use

Our use of information received from the Greener Closet browser extension follows the Chrome Web Store User Data Policy, including the Limited Use requirements. We use extension data only to provide or improve the score badge, popup, analysis workflow, abuse prevention, and reliability reporting described on this page.

Data retention

Analysis logs and telemetry event rows are retained indefinitely so we can debug failure regressions and measure reliability. Workflow coordination job records are automatically pruned after completion. Request metadata is stored alongside the applicable log or event row.

Contact

Questions or data requests: contact us.

Your privacy choices

Optional analytics are off unless you choose them. Necessary features such as analysis, sign-in, language, security, and requested emails keep working either way.