Privacy Policy

Effective date: August 29, 2026

This policy describes what the eBay Reseller Toolkit browser extension ("the extension", listed on the Chrome Web Store as eBay Sold History & Profit Calculator) 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

• Sorting, sold-comps parsing, reports, and profit calculations run on your device. The only backend operated by us that the extension contacts is the license-validation service used to activate and periodically verify the optional Pro tier.
• The extension makes only two kinds of automatic 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. Your eBay search data is never sent to us.
• We do not run analytics or telemetry, sell data, or automatically send feedback. We receive personal information only when you voluntarily email us or purchase Pro through Paddle, as described below.

2. What the extension does over the network

Sorting itself reads the eBay search page already open in your browser and makes no network request. For the automatic search-page market summary and for a comps lookup you request on an 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:

• On a new eBay search page, the market-summary lookup runs once after the results load. An item-page comps lookup runs when you click the comps control. Each cache miss makes exactly one same-origin request; there is no polling, prefetching, or automatic retry.
• Results are cached on-device for 1 hour per site, normalized keyword, and relevant search filters, so repeating the same lookup within that window makes zero additional requests.
• The extension contacts no analytics endpoint or ad network. Its only non-eBay network endpoint is our own license-validation service, described in §4; those requests contain a license identifier but no browsing, search, or pricing data. There is no remote code loaded into the extension at runtime — all extension code ships inside the package.

3. What is stored, and where

The extension uses the browser's standard chrome.storage APIs. Page-derived eBay data uses chrome.storage.local and stays in that browser profile. Preferences and license state use chrome.storage.sync, which the browser vendor may sync between browsers where you are signed into the same profile; that browser-managed sync is not sent to or controlled by us.

Expired sold-comps entries are not used after one hour; they are replaced when that same query is refreshed, and otherwise can remain until extension storage is cleared or the extension is uninstalled. The latest report is replaced each time you open a new report. Other settings and license state remain until you change them, clear extension storage, or uninstall. We do not maintain any database, server, or log of your searches, prices, or browsing activity.

Optional feedback

Clicking Send feedback opens your default email client with a support template. Nothing is sent automatically. If you choose to send the message, we receive your email address and whatever text, screenshots, or page URL you include. We use it only to answer the request, investigate the reported issue, and — for actionable product feedback or a confirmed issue — deliver the advertised one-month Pro key. A store rating or review is never required. You can ask us to delete a support message by emailing the address in §8.

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.
• Our license service stores the randomized license key together with Paddle's subscription and customer identifiers, the selected plan, status, and relevant timestamps. It does not store your card details, eBay searches, or listing/pricing data. These entitlement records are retained while needed to validate the subscription and handle cancellations, refunds, and support.
• 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 receives a signed entitlement token containing the plan, active status, and expiry, but no card number, billing address, Paddle customer ID, or other payment detail. Card and billing details are never 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 functions 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 page-derived data. It stays in the browser's extension storage; browser-managed sync for preferences and license state is described in §3.

Chrome Web Store Limited Use

The extension's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. eBay page content and browsing context are used only to provide the prominently described, user-facing research features. They are not transferred to us or to third parties, used for advertising, or made available for human review.

7. Changes to this policy

If the extension's data handling changes (for example, 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