Sellerio Chrome Extensions — Privacy Policy
This policy covers Sellerio's three browser extensions. It is a separate, narrower document from Sellerio's main privacy policy, which covers the Sellerio web application. The three extensions share one Sellerio account and one set of servers, but they do not collect the same things, so each is listed separately below.
The categories used in "What each extension collects" are the ones used by the Chrome Web Store's own data-usage disclosure, so that this page and that disclosure can be read against each other line by line.
The three extensions, and where each one runs
| Extension | Runs on | What it does |
|---|---|---|
| Sellerio Seller Toolkit | sellercentral.amazon.in, sellerflex.amazon.in, seller.flipkart.com, supplier.meesho.com |
Crops and prints shipping labels, and accepts, packs and dispatches orders on a schedule you set |
| Sellerio Autofill | sellercentral.amazon.in, seller.flipkart.com, supplier.meesho.com |
Saves a filled-in listing form as a reusable template and fills it back in on a new listing |
| Sellerio Insights | amazon.in, amazon.com, amazon.co.uk, flipkart.com, meesho.com |
Scores publicly visible product listings and shows category rank information |
Each extension runs only on the sites listed above. On every other website it is inactive and reads nothing at all.
What each extension collects
-
Personally identifiable information — all three
The name, email address and optional mobile number you enter when creating or signing in to a Sellerio account. Used to identify your account, to contact you about the service, and for billing if you are on a paid plan. -
Authentication information — all three
The email address and password you submit when signing in, sent over an encrypted connection to Sellerio's own API and never stored on your computer. In exchange the extension stores a sign-in token, which is what keeps you signed in. See Signing in below for the detail, including the alternative sign-in that never involves the extension at all. -
Location — all three
The IP address a request arrives from. For feature-usage events it is resolved to an approximate country, region and city and stored alongside the event, so we can understand where the product is being used and investigate abuse. No GPS or device-level location is ever requested or read. -
User activity — all three
Feature-usage events: a fixed event name from a short, fixed list (for example "a label was cropped on Flipkart", "a template was filled", "the panel was opened"), how many labels or form fields were involved, whether you started it by hand or on a schedule, and the extension's version number. Never a page address, a search query, a product title or a template name. The Toolkit and Autofill additionally count repeated choices — which template you usually pick for a category, the weight you usually enter for a SKU, the time of day you usually start a run — so the extension can offer to do those things for you. Those counts are stored with your account so they follow you to another computer. -
Website content — all three
Specific values read from the page you are on. In the Toolkit: order numbers and SKU codes with quantities, recorded so you can see your own dispatch history, and your own store link, used to make a follow-us QR code for your parcels. In Autofill: the listing content you are working on — product titles, descriptions and field values, plus a product photo when you explicitly ask for an AI suggestion. In Insights: a product's identifier, and — if you press Import — the publicly visible details on that page, such as its rating, badges and specifications. Insights sends these only when you press Import, Watchlist or an analysis button; it scores a page you are simply reading entirely on your own computer, and sends nothing.
What is never collected
- Shipping labels and what is printed on them. A label PDF is downloaded from the marketplace to your own computer, cropped there, and printed from there — either through Chrome or through a QZ Tray application installed on that same computer. The buyer names, addresses and phone numbers printed on a label are never transmitted to Sellerio and are stored on no Sellerio server.
- Your browsing history. The extensions cannot read Chrome's history, your open tabs, or your bookmarks, and have no access to any website other than those listed above.
- Financial and payment information. No card number, bank detail, settlement amount or order value is read or transmitted. Sellerio never sees a marketplace password or a payment instrument.
- Health information and personal communications. Neither is read, in any form.
- Keystroke, mouse or screen monitoring. There is no keylogging, no mouse or scroll tracking, no session recording and no network monitoring.
What stays on your own computer
Some things are held in the extension's own storage and are never sent anywhere:
- Label files and print history — the label PDFs themselves, your crop settings, the printers you chose and your QZ Tray configuration (Toolkit).
- Common details — a saved set of fields that repeat across listings, such as country of origin, manufacturer, seller and importer information, if you choose to save one (Autofill).
- Preferences — dark mode, auto-fill on or off, which template is set to auto-fill, the floating bar's position on screen.
- Bulk-import queues — if you bulk-fill from a CSV, the imported rows and your place in the queue stay on your computer until you finish or clear the queue (Autofill).
Removing an extension deletes all of it. Listing templates are the exception: they are synced to your Sellerio account so they are available on your other computers, and they are described under Retention below.
Signing in to your Sellerio account
There are two ways to sign in, and they differ in a way worth stating plainly:
- With an email address and password. You type both into the extension's own sign-in panel, and the extension sends them over an encrypted connection to Sellerio's API (
api.sellerio.in) to be checked. They are not stored on your computer and are not sent anywhere else. - With Google or Apple. The extension opens the ordinary Sellerio login page on
sellerio.inin a normal browser tab. You sign in there, on the website; the website then passes a short-lived, single-use code back to the extension, which exchanges it for a sign-in token. On this path the extension never sees your password at all — and because the code is passed to all three extensions, signing in once signs you in everywhere.
Either way, what the extension ends up storing is a sign-in token, not a password, plus your display name and email address for the account panel. The token is held in Chrome's extension storage; if you have Chrome Sync switched on, it may sync to your other Chrome profiles, in the same way a password saved in Chrome does. Signing out revokes the token on the server and erases it from your computer.
No selling, no ad tracking
- Extension data is not sold to any third party.
- It is not used or transferred for any purpose unrelated to the extension's single purpose.
- It is not used or transferred to determine creditworthiness, or for lending purposes.
- It is not used for advertising, and there is no advertising or cross-site tracking of any kind in any of the three extensions.
Network calls go to Sellerio's own API (api.sellerio.in) and, for the optional AI features only, to the AI provider that produces the suggestion. When you use "Suggest category", "Improve" or a listing score in Autofill, the product text or photo for that one request is sent to a third-party AI provider — Anthropic, OpenAI or Google, depending on the feature — solely to produce that suggestion for you. Those providers are not permitted to use it to train their models.
Two things are sent without you pressing anything, and are named here rather than left implied: the feature-usage event described above, which is sent after an action completes, and the learned-habit counts, which sync to your account in the background so they reach your other computers.
Why each permission is requested
Requested by all three extensions:
| Permission | Why |
|---|---|
storage | Holds your sign-in token, your settings and preferences, and the extension's own working data described above. |
identity | Used by the sign-in flow to identify the extension's own return address, so a completed sign-in on the Sellerio website can be handed back to the extension. |
Host access to api.sellerio.in | The Sellerio API itself: signing in, syncing your templates and settings, and the optional AI features. |
Requested by the Seller Toolkit and Autofill:
| Permission | Why |
|---|---|
| Host access to the marketplace seller sites | Lets the extension read and act on your own seller pages — the order list it is processing, or the listing form it is filling. This is the entire core function. |
sidePanel | Draws the extension's panel in Chrome's side panel instead of a small pop-up, so it can stay open while you work. |
unlimitedStorage | Toolkit only. Lifts Chrome's default cap on extension storage, so a seller with a very large catalogue of saved package sizes and box choices does not hit a browser limit. |
Requested by the Seller Toolkit only:
| Permission | Why |
|---|---|
alarms | Runs your daily order schedule at the time you set. Chrome must be running on the computer at that time. |
scripting | Loads the PDF engine that crops your labels, on demand, into the marketplace page you are already on — rather than loading it on every page visit. |
declarativeNetRequestWithHostAccess | Redirects a label file the marketplace would otherwise open in Chrome's own PDF viewer into Sellerio's crop view instead. It does not read, block or modify any other request. |
| Host access to Amazon's and the marketplaces' file storage | Label files are not served from the seller site itself but from the marketplace's file storage. This is what lets the extension fetch the label you just asked for, so it can be cropped. |
notifications (optional) | Only requested if you turn on notifications for scheduled runs, so you are told when one finishes or could not run. The extension works without it. |
Retention & deletion
Your account details are kept for as long as your account exists. Feature-usage events are kept as aggregate product-usage history. Listing templates and synced settings live on your Sellerio account and stay until you delete them — deleting a template from the extension, the pop-up or your dashboard removes it everywhere.
You can sign out at any time, which revokes the token on the server and clears it from your computer, or remove the extension, which erases everything it kept on your computer. To delete your Sellerio account and the data associated with it, write to contact@mysellerio.com and it will be removed.
Contact
Questions about these extensions' data handling: contact@mysellerio.com. See also: Sellerio's main privacy policy and Terms & Conditions.