SPE — Store Product Exporter: Privacy Policy

Effective September 18, 2026

A plain explanation of what this Chrome extension can see, what it does with it, and — just as important — everything it doesn't do.

The short version: SPE runs entirely inside your own browser. It reads the Uzum Seller session you're already logged into, uses it to call Uzum's own seller API for your own product catalog, and saves the result as a ZIP file on your computer. There is no SPE server. Nothing about your store, your products, or your session ever reaches us — we simply never see it.

1. What SPE can access

When you open the extension's control tab and click Start export while logged into seller.uzum.uz, SPE reads:

• Your session token and shop ID — already sitting in that page's local storage after you signed in yourself. SPE reads them to make API calls on your behalf; it never asks for, stores, or even sees your Uzum username or password.
• Your product catalog — titles, descriptions, categories, characteristics, prices, SKUs, barcodes, IKPU codes, and images, fetched directly from Uzum's own seller API for your own shop.

All of it belongs to the store you're already logged into. SPE has no mechanism to reach any other account.

2. What SPE does not do

• No SPE-operated server — there's nothing behind this extension for your data to be sent to.
• No analytics, tracking, or telemetry of any kind.
• No sharing, selling, or transferring your data to anyone, for any reason.
• No advertising.
• No access to your Uzum password — SPE only reuses the session token your browser already holds.

3. How your data is used and stored

Everything happens in memory, inside your browser, for the length of one export run. SPE fetches your catalog, builds a ZIP (product data as JSON and CSV, plus the images), and hands it to Chrome's own download mechanism. Once the download starts, that file lives wherever your browser saves downloads — on your computer, under your control, like any other file you download.

SPE doesn't write your token, shop ID, or catalog data anywhere else: no chrome.storage, no cookies, no database. Close the tab, and nothing about the run is left behind.

4. Permissions, explained

Chrome requires every permission an extension requests to be declared up front. Here's what each one is for: