Privacy Policy

Effective date: July 16, 2026

This policy describes what the eBay Reseller Toolkit browser extension ("the extension") does and does not do with your data. We wrote it to be accurate, not to be reassuring — if a claim isn't backed by the code, it isn't in here.

1. Summary

• The extension runs entirely on your device. There is no backend server operated by us that the extension talks to.
• The extension makes only two kinds of network requests: same-origin requests to eBay pages you are already browsing (see §2), and — only in connection with the paid Pro tier — license-status checks to our own license-validation service (see §4). Payment itself is handled by Paddle, our Merchant of Record, on a page outside the extension. Neither request carries your browsing or search data.
• We do not run analytics or telemetry of any kind, and we do not sell or share your data, because we never receive it in the first place.

2. What the extension does over the network

When you use the "Sort by sold" or "Comps" features on an eBay search or item page, the extension's content script — already running on that ebay.com or ebay.co.uk page as part of normal page injection — issues a fetch() request to that same eBay domain (e.g. /sch/i.html?...&LH_Sold=1 for a sold/completed-listings search). This is functionally the same request your browser would send if you navigated to that sold-listings search yourself.

Details, so this claim can be checked against the code:

• One request per click. There is no background polling, no prefetching, and no automatic retry loop — on a network failure the extension retries the fetch exactly once and then gives up (see src/lib/soldFetch.ts).
• Results are cached on-device for 1 hour per search keyword, so repeating the same lookup within that window makes zero additional requests.
• The extension does not add any host_permissions beyond the eBay domains it is designed for, and it does not contact any analytics endpoint or ad network. The only other network endpoint it contacts is our own license-validation service, described in §4 — those requests contain no browsing, search, or pricing data. There is no remote code loaded into the extension at runtime — all code ships inside the extension package.

3. What is stored, and where

All storage is local to your browser profile (via the standard chrome.storage extension APIs) and is never transmitted anywhere by us:

We do not maintain any database, server, or log of your searches, prices, or browsing activity outside of your own browser's local storage.

4. Payments (Pro subscription)

Payments for the Pro tier are processed by Paddle.com Market Limited ("Paddle"), which acts as our Merchant of Record — Paddle, not us, is the seller of record for your Pro purchase, handles card processing, and calculates/remits any applicable sales tax or VAT. Subscription/license status inside the extension is validated separately, by our own license service, not by Paddle directly. Integration details, verifiable in the code and the extension manifest:

• Clicking "Upgrade" opens Paddle's checkout in an ordinary browser tab, outside the extension. Card details are entered directly into that Paddle-hosted checkout — the extension never sees, collects, or stores your card number, billing address, or other payment details.
• After checkout, the extension's background service worker contacts our own license-validation service (not Paddle) to activate and periodically re-check your subscription status. This request sends only a license identifier — never your eBay searches, browsing activity, or any comps/pricing data.
• Our license service receives subscription events from Paddle (for example, that a subscription is active, cancelled, or refunded) so it can keep your license status current. Paddle only ever sees that you purchased a subscription — never anything about how you use the extension on eBay.
• The extension's manifest lists the domain of our license-validation service under host_permissions so the extension can check subscription status; the exact domain is ebay-rt-license.dadiyuhuang88.workers.dev. Paddle's own checkout domain is not part of the extension package at all — it only ever opens in an ordinary browser tab, never as an in-extension request.

The extension only ever receives a subscription-status flag (active Pro / not Pro) back from our license service — no card number, billing address, or other payment detail is ever stored by, or visible to, the extension. Your purchase itself, including receipts, billing history, and refund processing, is governed by Paddle's own Privacy Policy. See our Refund Policy for how refunds work.

5. Permissions we request, and why

We do not request tabs, history, webRequest, <all_urls>, or any permission unrelated to the two features above. If a future version needs an additional permission, this section will be updated and the change will be disclosed in the extension's store listing update notes.

6. What we do not do

• We do not run any analytics, crash-reporting, or telemetry SDK.
• We do not inject ads or affiliate redirects.
• We do not automate your eBay account (no auto-bidding, auto-listing, auto-following, or any action taken on your behalf without a direct click).
• We do not sell, rent, or share data, because the extension does not collect data to sell in the first place — everything described in §3 stays in your own browser's local storage.

7. Changes to this policy

If the extension's data handling changes (for example, once the Pro payment provider in §4 is finalized, or if a future version adds a permission), we will update this document and note the change in the extension's release notes before the update reaches users.

8. Contact

Questions about this policy or the extension's data handling:
dadiyuhuang88@gmail.com