S
SoldSnap
Privacy & Preference Center

Privacy & Preference Center

SoldSnap Privacy & Preference Center

A clear, detailed explanation of how the SoldSnap Chrome extension handles data, what it processes, what it never touches, how its support-link system works, and the choices you have as a user.

Last updated: June 10, 2026Chrome Web Store readyMobile responsive

What SoldSnap is

A product research assistant Chrome extension for supported marketplaces.

What it never does

No passwords, no payment data, no personal messages, no data selling.

Support links

Support links may be used at no extra cost to you. Your price never changes.

Disclosure: Support links may be used at no extra cost to you. Some actions may produce links that include referral or affiliate tracking parameters where the marketplace supports them.

What SoldSnap is, who it is for, and what this Privacy & Preference Center covers.

SoldSnap is a product research assistant delivered as a Chrome extension. It is designed for resellers, sourcing specialists, dropshippers, online arbitrage buyers, comparison shoppers, and everyday users who want a faster way to look at product information on supported marketplaces. SoldSnap does not replace any marketplace, does not log you in, and does not act on your behalf. It is a helper layer that sits on top of pages you already visit in your own browser.

This Privacy & Preference Center explains, in plain English, exactly what SoldSnap does, what information it works with, what information it never touches, how its support-link system works, and the choices you have as a user. We have tried to avoid heavy legal jargon. Where a technical detail is unavoidable, we explain what it means for you in practice.

The extension's core features are:

  • Viewing product information on supported marketplace pages.
  • Downloading product images that are publicly displayed on a listing.
  • Copying product links with one click.
  • Viewing marketplace-related product data such as title, price, and identifiers.
  • Viewing eBay purchase / sold history where eBay shows it on the page.
  • Opening cross-search links to compare a product on supported marketplaces.
  • Processing supported product links through a backend support-link system.

We believe that a privacy policy is only useful if it tells the truth about how a product actually behaves. So we have written this page to match how SoldSnap really works today, not a generic template. Where the extension performs background work, we say so. Where it stores something locally, we say so. Where it talks to a backend, we say so. And where a link may include affiliate or referral tracking, we say so clearly — both at the top of the page and in the dedicated section below.

Support links may be used at no extra cost to you. Some of the marketplace links that SoldSnap helps you open or copy may pass through a support-link system that can include referral or affiliate tracking parameters where they are supported by the marketplace. Your price never changes. You are never charged extra. You can choose not to use these actions at any time.

A feature-by-feature description of SoldSnap so you know exactly what runs in the background and what only runs when you click.

SoldSnap is built around a small set of focused features. Each one is described below so you can clearly see when SoldSnap is doing something automatically in the background, and when it is only reacting to a button you pressed.

Download Images

When you are on a supported product page and you click the “Download Images” action, SoldSnap looks at the product gallery on that page and asks your browser to save the gallery images to your computer using the standard Chrome download flow. The extension does not upload those images to our servers. It does not send copies to anyone. It does not modify them. They go from the marketplace, through your browser, directly to your local downloads folder.

Copy Link

Copy Link puts a marketplace product link onto your clipboard so you can paste it into a spreadsheet, sourcing list, message, or notes app. Depending on the marketplace and configuration, the link copied may be the original product link, or it may be a processed support link (see Section 6). If support-link generation fails for any reason, SoldSnap falls back to the original product link so the action does not break.

Product Information Panel

The product information panel surfaces details that are already visible on the marketplace page in a single compact view. This may include the product title, identifiers such as ASIN or item ID, price, image URLs, and marketplace domain. This information is read from the page in your browser. It is shown back to you in the extension UI. It is not silently uploaded.

eBay Sold / Purchase History

On eBay listings that expose recent sold or purchase history to buyers, SoldSnap can show that history inside the extension panel for easier reading. It reads what eBay already shows on the page, including masked buyer usernames, sale dates, prices, and quantities. It does not bypass any eBay privacy protections. If eBay does not show this data on a page, SoldSnap will tell you that no recent sold history was found.

Cross-Search Buttons

Cross-search buttons open new tabs that run a search for the current product on other supported marketplaces. These are normal search URLs — the same kind you would type into a search box. They do not log you into anything and they do not transmit your data anywhere new.

Support-Link Processing

When you trigger an action that produces a marketplace link on a supported product page, SoldSnap may prepare a support link in the background. This is explained in detail in Section 6. The short version: the user-visible price never changes, and the original link is always used as a fallback.

Backend Processing

SoldSnap may contact backend endpoints under soldsnap.worknexas.com to convert a product identifier into a support link, or to fetch updated configuration files. The backend does not need your password, payment information, or personal identity. See Section 7 for what the backend does and does not do.

Marketplace Configuration Files

Marketplaces change their page layouts frequently. To avoid forcing a new extension update every time a small thing changes, SoldSnap can fetch a marketplace-config.json file from the backend with up-to-date selectors. If that fetch fails, SoldSnap uses a local fallback configuration that ships with the extension.

Remote Selector Configuration

Remote selector configuration is what allows SoldSnap to keep finding the product title or price even if a marketplace renames a CSS class on its page. Selectors are not personal data — they are tiny rules describing where on a page to look.

Local Fallback Selectors

If your network is offline or the backend cannot be reached, SoldSnap falls back to selectors bundled inside the extension so the core features keep working. You should rarely notice this happen.

The marketplaces SoldSnap is designed to work on, plus important exceptions.

SoldSnap is built to recognise and assist on specific marketplace domains. Outside of these domains, the extension generally stays quiet and does not analyse the page. The current supported list includes:

  • Amazon US
  • Amazon Australia
  • AliExpress
  • eBay US
  • eBay UK
  • eBay Australia
  • Etsy
  • Walmart
  • Home Depot
  • Sam's Club

Important exceptions and notes:

  • Temu is disabled. SoldSnap does not currently process Temu pages as a supported marketplace.
  • Amazon UK support-link conversion may be disabled. If configured that way, SoldSnap will not convert Amazon UK links into support links and will use the original link instead.
  • Some features may vary by marketplace. For example, sold history is an eBay-specific concept and is not available on other marketplaces.
  • Supported marketplaces and feature availability may change over time. We update this list when meaningful changes happen.

A precise list of the kinds of data SoldSnap works with so there are no surprises.

To deliver the features above, SoldSnap may process the following kinds of information. “Processed” here means read in your browser, briefly held in memory, possibly cached in local extension storage, and in some cases sent to the backend to prepare a support link or fetch configuration.

  • Product page URL of the page you are currently viewing.
  • Product identifier such as ASIN, item ID, product ID, or listing ID extracted from the page or URL.
  • Marketplace domain (for example amazon.com).
  • Product title displayed on the page.
  • Public product image URLs displayed in the gallery.
  • Visible price and other publicly visible product information.
  • eBay sold or purchase history rows already visible on the page, including masked buyer usernames.
  • User-selected actions such as “Copy Link” or “Download Images” so the feature can run.
  • Extension settings that you have changed, saved locally.

The extension does not try to read the entire page. It looks for specific structured fields such as title, price, identifier, and gallery. It does not record your scroll position, mouse movements, or what you type into the marketplace.

A clear list of categories that are intentionally out of scope.

We treat the following categories as out of scope. SoldSnap is not designed to collect, store, transmit, or analyse any of them:

  • Passwords or any authentication credentials.
  • Payment card numbers, CVV, or expiry data.
  • Bank account details.
  • Personal messages, chats, or DMs.
  • Sensitive personal information such as health or government IDs.
  • Unrelated browsing content from sites that are not supported marketplaces.
  • Private account credentials of any kind.
  • The contents of checkout or payment pages for the purpose of payment data extraction.

We do not sell personal data. We do not build advertising profiles. We do not share information with data brokers.

What the backend does and does not need in order to support the extension.

The extension may communicate with backend endpoints hosted at soldsnap.worknexas.com. The backend exists to support specific features of the extension. It is not an analytics pipeline, an ad system, or a data broker.

What the backend may do:

  • Accept a product identifier and the marketplace it came from so it can return a support link.
  • Serve the latest marketplace-config.json with updated selector hints.
  • Serve the latest link-config.json with support-link configuration.
  • Return short, minimal responses focused on what the extension needs.

What the backend does NOT need:

  • Your password or any marketplace login credentials.
  • Your payment information.
  • Your personal identity or real name.
  • The full HTML of pages you visit.

Standard request metadata such as IP address and user agent may be visible to the hosting provider as part of normal web traffic. This is true of any website you visit and is required for the internet to work.

How marketplace-config.json and link-config.json keep the extension working when sites change.

Marketplaces frequently tweak their HTML structure. To stay stable without forcing daily updates, SoldSnap uses two small configuration files:

  • marketplace-config.json — describes how to recognise products and read structured fields on each supported marketplace.
  • link-config.json — describes which marketplaces have support-link conversion enabled and how a link should be shaped.

These configuration files contain no personal data. If the remote fetch fails (you are offline, the backend is being updated, etc.) SoldSnap silently falls back to the local configuration that shipped with the extension. The result is fewer broken features for you and fewer surprise updates.

Exactly how SoldSnap reads eBay sold history and what it never does.

On eBay listings where eBay itself displays recent purchase or sold history to buyers, SoldSnap can present that information in a cleaner, more compact format inside its panel. This makes it easier to spot trends — how often a product sold, at what price, and at what quantity.

What SoldSnap does:

  • Reads the visible rows of sold / purchase history.
  • Captures fields such as date, price, quantity, and the masked buyer username that eBay already shows.
  • Displays the rows back to you inside the extension.

What SoldSnap does not do:

  • Reveal hidden or unmasked buyer identities.
  • Bypass any eBay privacy protection.
  • Show data that is not already displayed on the page to a normal logged-in or signed-out viewer.

If no sold history is available on a page, SoldSnap simply tells you that no recent sold history was found.

How the image downloader picks images and why it does not upload anything.

When you trigger the image download feature, SoldSnap inspects the product gallery on the page you are viewing and asks Chrome to download those gallery images to your computer.

  • The extension detects images that look like product gallery images.
  • It tries to avoid unrelated images such as ads, banners, or recommended items.
  • It does not intentionally download private images.
  • It skips unrelated marketplace assets where possible.
  • Downloads are saved through the standard Chrome download API, so they appear in your normal downloads folder.
  • Downloaded images are never uploaded to our servers, never shared, and never logged remotely.

You are responsible for how you use the images you download. Marketplace and brand image rights still apply.

What SoldSnap keeps inside chrome.storage.local and how to clear it.

For speed and reliability, SoldSnap keeps a small amount of data locally inside your browser using chrome.storage.local. This data lives on your machine, not on our servers.

  • Your extension preferences and toggled options.
  • Cached marketplace and link configuration files.
  • Temporary “prepared” support-link state so that actions like Copy Link feel instant.

Local caching exists to reduce repeated network requests and to keep the extension responsive. You can clear all of this at any time by removing or reinstalling the extension, or by clearing extension storage from chrome://extensions.

Every permission the extension may request and the human-readable reason for each.

Chrome asks the extension to declare permissions up front. Here is what each one is used for inside SoldSnap:

  • activeTab / tabs — lets SoldSnap know which marketplace tab you are actively using so its features apply to the right page.
  • storage — used to save your preferences and to cache configuration locally.
  • downloads — used so that “Download Images” can save files through Chrome.
  • host permissions for supported marketplaces — needed so the extension can read product information from those specific marketplace pages.
  • backend domain access — used to fetch support links and remote configuration from soldsnap.worknexas.com.
  • clipboard / copy behaviour — used so that “Copy Link” can place a link on your clipboard.

These permissions exist to power product research tools. They are not used to collect passwords, payment information, or identity details.

Who, if anyone, receives information — and who definitely does not.

SoldSnap does not sell your data. Specifically:

  • Data may be sent to the SoldSnap backend only for feature functionality such as preparing a support link or fetching configuration.
  • Marketplaces will naturally receive normal page requests when you open or click on their links — that is just how browsing works.
  • Your browser's and the marketplace's own privacy policies also apply to your activity there.
  • We do not share data with advertising networks, data brokers, or unrelated third parties.

The third-party services that necessarily come into play.

Because SoldSnap helps you interact with marketplaces, some third parties are unavoidably involved when you use it:

  • Amazon
  • AliExpress
  • eBay
  • Walmart
  • Etsy
  • Home Depot
  • Sam's Club
  • Browser / Chrome platform APIs
  • Our hosting / backend infrastructure provider

These services have their own privacy policies. SoldSnap does not control them and is not responsible for how they handle information that you send to them by visiting their websites.

How we keep secrets out of the extension and harden the system.

Security practices we follow:

  • API keys are stored on the server, not inside the extension package.
  • Private configuration files are not exposed publicly.
  • HTTPS is used for backend communication where applicable.
  • The extension uses fallback logic (local configuration, original product links) so that failures do not break basic usage.
  • We actively avoid exposing sensitive credentials to web pages, to other extensions, or to the user interface.

No system can promise perfect security. What we can promise is that we design SoldSnap so that even if a part of it fails, no sensitive secret should leak out of it.

The controls you have over how SoldSnap behaves in your browser.

You are always in control:

  • You can choose whether or not to use Copy Link.
  • You can uninstall the extension at any time.
  • You can clear your browser data, including extension storage.
  • You can disable the extension without uninstalling it.
  • You can avoid using support links by not using related actions on supported pages.
  • You can contact us with privacy questions at the address in Section 20.

Age-related boundaries.

SoldSnap is intended for adults who are doing product research or shopping. It is not directed at children under 13, or under the applicable minimum age in your jurisdiction. We do not knowingly collect personal information from children. If you believe a child has used the extension and you would like us to look into something, please contact us.

Notes for users outside the regions where the backend is hosted.

SoldSnap users may live anywhere in the world and may visit marketplaces in many countries. Depending on where our backend and supporting services are located, your requests may be processed in a different country than the one you live in. By using the extension, you understand that this kind of cross-border processing is normal for internet services.

You should only use SoldSnap where it is legal for you to do so, and you should respect the terms of service of every marketplace you visit.

How we will let you know when this policy changes.

We may update this Privacy & Preference Center from time to time as the extension evolves, as new features are added, or as laws or marketplace requirements change. When we do, we will update the “Last updated” date at the top of this page. Material changes will be reflected in the relevant sections rather than buried in a separate document.

We encourage you to review this page occasionally so you are aware of how SoldSnap currently handles information.

How to reach us.

If you have any questions about this policy, about a feature, or about a specific behaviour you have observed, please get in touch: