1 Scope of this policy
This Privacy Policy explains how Seller Queue handles personal information when you visit the public website, create or use an account, upload marketplace reports, use the settlement workspace, make a payment, use seller tools or the browser extension, or contact us. “Seller Queue”, “we”, “us” and “our” refer to the operator of the Seller Queue service. This policy should be read together with the notices shown at the point where a feature requests information.
2 Information we collect
Account and profile information. This may include your name, email address, phone number, company or business name, business type, primary marketplace, GST details, city and address, depending on the fields you complete.
Authentication information. When you use Google or email-based sign-in, Firebase Authentication handles the authentication flow. We receive the identifiers and profile information needed to recognise your account. Do not share passwords or authentication codes with us.
Marketplace and business files. We process files you choose to upload, including order reports, payment and settlement reports, product cost files and generated report inputs. These files can contain order identifiers, SKUs, amounts, deductions, payment dates, returns and other business records. A source report may also include customer names, addresses or contact information.
Enquiries and support. We receive the name, email, topic, marketplace, message, attachments and other information you submit. Support records can include ticket category, status, replies and diagnostic context.
3 Tool and extension information
The Meesho extension processes the information required for the action you choose on supported Meesho pages, including relevant product, pricing or shipping information. It may store an installation identifier, account pairing or authentication state and settings in browser storage. Its declared permissions include storage, tabs and clipboard writing, along with access to relevant Meesho pages.
Image tools process the images and settings you submit to generate the requested output. Source images are handled during processing, and generated outputs are made available temporarily for download. Tool activity such as opens, runs, downloads and generated output counts may be recorded separately from the files.
4 Cookies browser storage and analytics
We use cookies and browser storage to maintain sign-in, recognise a tool visitor and remember relevant settings. A first-party tool visitor cookie currently named sb_tool_vid may retain a randomly generated identifier for up to one year unless you clear it sooner. When you are signed in, tool activity can be associated with your account. A random identifier is pseudonymous information and should not be treated as proof that activity is anonymous.
If Google Analytics is enabled, it may collect information about visits, pages, interactions and device or browser characteristics through Google technology. Where consent is required for optional analytics, the relevant consent mechanism must be used. You can control cookies and local storage in your browser, but blocking them can sign you out or prevent some features from working.
5 How we use information
We use information to create and manage accounts, authenticate access and provide the features you request. This includes processing marketplace files, preparing settlement analysis, applying supplied product costs, generating downloadable reports and images, and maintaining available report history.
We also use information to administer token balances and payment records, answer enquiries, investigate support tickets, manage service access, understand tool usage, troubleshoot errors, investigate misuse, protect accounts, maintain backups and meet applicable legal obligations. If a new use requires additional notice or consent, that notice or consent must be provided before the new processing begins.
6 Payments
Razorpay processes payments for available paid features or tokens when that option is offered. The payment provider handles the payment information entered in its checkout under its own privacy notice. Seller Queue receives or stores information needed to connect the payment to your account and maintain purchase or token records. This may include order and payment identifiers, amount, transaction status and verification details. Do not send card security codes, UPI PINs or one-time payment codes through Contact Us or Support.
7 Service providers and authorised access
Information may be processed by providers that support hosting, storage, authentication, payment processing, email delivery, analytics and customer support. Firebase Authentication and Razorpay support the functions described above. Where configured, public enquiries may pass through Google Forms and support information may be mirrored to a Google-managed workflow such as Sheets or Apps Script. Email delivery may use the configured email provider.
Authorised personnel may access information to administer accounts, deliver the service, investigate support issues or protect the service. Information may also be disclosed when required by law or necessary to respond to a valid legal process. External providers process information under their own applicable terms and privacy notices.
8 Where information is processed
Information may be stored or processed where Seller Queue and its service providers operate. The exact location depends on the deployed hosting arrangement and provider settings. Use of the service should not be understood as a promise that all information remains in India. International processing, where applicable, is handled according to the legal requirements that apply to the transfer.
9 How long information is kept
Different records have different retention needs. Removing an uploaded source file does not necessarily remove a generated report, account record, support conversation, payment record, tool activity record or backup copy.
Temporary uploads and support attachments are subject to scheduled cleanup. The current application default makes eligible files available for cleanup after approximately seven days. Generated image outputs currently use an expiry setting of approximately thirty minutes. These are cleanup settings, not guarantees that every copy will be erased at an exact time; actual timing depends on the deployed configuration and successful execution of cleanup tasks.
Account information, generated settlement reports, support records, tool activity and transaction records can remain in persistent storage while needed for the account, service, security, legal or support purpose. Backups may retain copies after information is removed from active storage. Automatic database backups are rotated as a limited set of recent copies, while manual backups may be handled separately.
10 Security
Seller Queue uses authentication and access controls for protected features. Security also depends on the hosting configuration, administrative access and external services involved. No website or storage system can promise absolute security. Keep your sign-in credentials and authentication codes private, protect devices used for the account and contact us if you suspect unauthorised access. When a personal-data breach creates a legal notification duty, the required notifications will be made under applicable law.
11 Your choices and privacy requests
You may contact us to request information about personal data associated with you, correction of inaccurate information, or deletion where appropriate. Where processing relies on consent, you may request withdrawal of that consent. Withdrawal does not undo processing already carried out and may prevent a feature from working when the information is necessary for that feature.
Rights to access, correction, erasure, grievance redressal, nomination or other remedies depend on the law applicable to the request and the effective provisions of that law. We handle requests under those requirements and may retain information where the law allows or requires it. We may ask for proportionate information to verify identity and protect the account.
12 Information uploaded by a seller
If your information appears in a marketplace report uploaded by a Seller Queue user, the relevant seller is normally the source of that upload and may need to help identify the record. Contact us with the seller and record details where possible. We may coordinate with the account holder whose instructions govern the upload, subject to applicable law. Sellers should upload only information they are authorised to share and remove unnecessary personal information where the report format allows it.
13 Children and external services
Seller Queue is intended for adult business users and is not directed at children. If you believe a child has provided personal information through the service, contact us so the matter can be reviewed. Links to marketplaces, authentication providers, payment services and other external websites lead to services governed by their own terms and privacy notices.
14 Changes to this policy
We may update this policy when features, providers, practices or legal requirements change. The current version will show its effective and last-updated date. Where required, we will provide additional notice or request consent before a change that materially affects how personal information is processed.
15 Privacy contact and grievances
For a privacy question, request or complaint, use the Contact Us page and choose Privacy request, or use Support inside your dashboard for an account-related matter. Use the email linked to your account where possible, describe the information or action concerned, and do not include passwords or unnecessary identity documents. Requests and complaints will be handled within the timelines required by applicable law. Where available under applicable law, you may also approach the relevant data-protection authority or other competent body.