Privacy Policy
This policy covers two things: the Sellerio web application, including the data it accesses through the Amazon Selling Partner API (SP-API) and Amazon Advertising API, and the three Sellerio Chrome extensions — Seller Toolkit, Autofill and Insights. Sellerio does not sell seller data, and does not use it for any purpose beyond powering the account holder's own operations.
If you are here from the Chrome Web Store, the section you want is Sellerio Chrome extensions.
What data is accessed
| Source | Data | Purpose |
|---|---|---|
| Amazon SP-API | Orders, order line items, shipping status, ASIN/SKU catalog data | Order tracking, inventory deduction, revenue reporting |
| Amazon Advertising API | Campaign, ad group, keyword, and search-term performance (spend, clicks, sales) | Bid optimization, negative-keyword management, ad profit & loss reporting |
| Google Sheets API | Values in the specific Google Sheet spreadsheet an account holder chooses to connect, plus the connecting user's Google account email address | Two-way sync of the account holder's own order, inventory, and listing data between Sellerio and their chosen spreadsheet, for offline review/editing and bulk export |
Sellerio does not request access to Amazon buyer personal information beyond what's required to fulfill and report on orders (e.g. shipping status), and does not use SP-API or Advertising API data for advertising, marketing, or any purpose outside the account holder's own operations.
Sellerio's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google Sheets access is used exclusively to read and write the one spreadsheet an account holder explicitly connects, for that account holder's own data sync — never for advertising, never for training any model, and never shared with or sold to any third party.
Sellerio Chrome extensions
Sellerio publishes three Chrome extensions. They share one Sellerio account and one set of servers, but they do not collect the same things, so each is listed separately below.
| 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 the seller sets |
| Sellerio Autofill | sellercentral.amazon.in, seller.flipkart.com, supplier.meesho.com | Fills marketplace listing forms from the seller's own saved templates |
| 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 site it is inactive and reads nothing.
What the extensions collect
The categories below are the ones used by the Chrome Web Store's data-usage disclosure, so that this policy and that disclosure can be read against each other.
-
Personally identifiable information All three
The name, email address and optional mobile number entered when creating or signing in to a Sellerio account. Used to identify the account, to contact the account holder about the service, and for billing where a paid plan is in use. -
Authentication information All three
The email address and password submitted at sign-in, sent over HTTPS to Sellerio's own API and never stored on the device. In exchange the extension stores a bearer token, which is what keeps the seller signed in. The token is held in Chrome's extension storage; where the seller has Chrome Sync enabled, it may sync to their other Chrome profiles the same way a saved password does. Signing out revokes it on the server and erases both copies. -
Location All three
The IP address the request arrives from. For feature-usage events it is resolved to an approximate country, region and city and stored alongside the event. This is used to understand where the product is being used and to 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"), the number of labels or form fields involved, whether it was started by hand or by a schedule, and the extension's version number. Never a page URL, a search query, a product title or a template name. The Toolkit and Autofill additionally count repeated choices on the device — which template a seller usually picks for a category, the weight usually entered for a SKU, the time of day a run is usually started — so the extension can offer to do those things automatically. Those counts are stored with the account so they follow the seller to another computer. -
Website content Toolkit, Autofill
Specific values read from the seller's own marketplace pages: order identifiers and SKU codes with quantities, recorded so the seller can see their own dispatch history; the seller's own store link, used to generate a follow-us QR code for their parcels; and, in Autofill, the listing content the seller is working on — product titles, descriptions and field values, plus a product photo where the seller explicitly asks for an AI suggestion. Insights collects none of this: it reads public product pages and scores them entirely on the device.
What the extensions never collect
- Shipping labels and what is printed on them. A label PDF is downloaded from the marketplace to the seller's 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 on a label are never transmitted to Sellerio and are never stored on Sellerio's servers.
- Browsing history. The extensions do not read Chrome's history, open tabs, or bookmarks. They have no access to any site 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 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.
Data the extensions keep only on the device
Some things are held in the extension's local storage and are never sent anywhere: label crop settings and print history, the label PDFs themselves, the chosen printers and QZ Tray configuration, and listing templates before the seller chooses to sync them to their account. Uninstalling the extension removes all of it.
Who extension data is shared with
Extension data is sent to Sellerio's own servers and, for the optional AI features only, to the AI provider that generates the suggestion. When a seller uses "Suggest category", "Improve" or a listing score in Autofill, the product text or photo for that request is sent to one or more third-party AI providers — Anthropic, OpenAI or Google — solely to produce that suggestion for that seller. Sellerio does not permit those providers to use it for model training.
Beyond that, extension data is not sold, rented, or shared with any third party. Specifically, and matching the certifications Sellerio makes on the Chrome Web Store: extension data is not sold to third parties, is not used or transferred for any purpose unrelated to the extension's single purpose, and is not used or transferred to determine creditworthiness or for lending purposes.
Retention and deletion of extension data
Account details are kept while the account exists. Feature-usage events are kept as aggregate product-usage history. A seller can sign out at any time, which revokes the token on the server, or uninstall the extension, which erases everything held on the device. To delete a Sellerio account and the data associated with it, write to contact@mysellerio.com and it will be removed.
How data is stored
- Data is stored in a private, access-controlled database that is not bound to any public network interface — it cannot be reached directly from the internet, and is not indexed or exposed by any public-facing page.
- All access to Sellerio requires an authenticated staff login with a role-based permission level enforced on every request; there is no public sign-up or anonymous access to any account data.
- Refresh tokens and API credentials are never exposed to the browser or included in any client-side response — only masked placeholders are ever returned to the interface once a credential is saved. Credentials are configured via environment variables and are never hardcoded or committed to source control. This applies equally to Amazon SP-API/Advertising API tokens and to Google OAuth tokens issued when an account holder connects a Google Sheet — Google access and refresh tokens are stored encrypted, scoped to that account holder's own organization, and are never returned to any client.
- All traffic between Sellerio and Amazon's APIs, and between a user's browser and Sellerio, is encrypted in transit (HTTPS/TLS).
- Uploaded files containing account data are served through an authenticated route requiring a valid session, not a publicly browsable directory.
Data retention
Order, inventory, and advertising data is retained for as long as the account remains active, to support historical reporting (e.g. year-over-year comparisons). Data for a disconnected or removed brand can be deleted on request.
Revoking access
An account holder can revoke Sellerio's access to their Amazon account at any time, either from within Sellerio (Remove/Disconnect on the relevant connection) or directly through Amazon — via Seller Central's Manage Apps & Services page, or the Solution Provider Portal's Manage Authorizations page. Revoking access stops all further API calls immediately; previously synced data already stored in Sellerio is not automatically deleted and can be removed on request.
Google Sheets access can be revoked the same way — from within Sellerio (Disconnect on the Google Sheets Sync settings page) or directly through Google, via Google Account > Security > Third-party apps & services. Revoking access immediately stops all further reads or writes to that spreadsheet.
Third parties
Seller data — whether accessed through Amazon's and Google's APIs or collected by the Sellerio Chrome extensions — is not sold, rented, or shared with any third party. Sellerio uses the following third-party infrastructure to operate:
- Hosting — the application and database run on Hostinger's Cloud Startup plan.
- AI-assisted features — optional AI listing analysis and SKU analysis features, in both the web application and the Autofill extension, send the relevant product text or photo to a third-party AI provider (Anthropic, OpenAI or Google, depending on the feature) to generate the recommendation. This is used only for the account holder's own listing optimization, not for any other purpose, and those providers are not permitted to use it for model training.
- Google Sheets API — used solely to read/write the spreadsheet an account holder explicitly connects, for that account holder's own order/inventory/listing data sync.
Changes to this policy
If this policy changes in a way that affects how seller data is handled — whether by the web application or by any of the Sellerio Chrome extensions — the "Last updated" date above will be revised and account holders will be notified.
Contact
The Perfect Creative Studio (operating Sellerio, its brand)
For privacy questions or data deletion requests: contact@mysellerio.com