Privacy Policy

Effective and last updated: November 10, 2026

Limits Express Company provides the Limits Express website and Chrome extension for managing marketplace listings, inventory tracking, and order fulfillment. This policy explains how these services handle information. Contact us at limitsexpresswholesale@gmail.com.

Information we handle

• Account and authentication: usernames, email addresses where provided, account identifiers, service status, and authentication/session tokens. Login credentials are processed through Amazon Web Services (AWS) Cognito. The extension stores session information locally to maintain your login.
• Optional Account Logins: if you use this feature, marketplace and supplier usernames, passwords, and authenticator setup keys are sent over HTTPS to our AWS backend and stored encrypted using AWS Key Management Service. They are associated with your Limits Express account and load on other browsers where you sign into that account. QR images are decoded locally and are not uploaded or retained. Current authenticator codes are generated on your device. These credentials and setup keys are not sent to FreshCrawl. You can remove a platform’s saved details from Account Logins; account deletion also removes them under the deletion policy below. Existing device-saved details transfer to AWS before the device copy is removed. This interface does not yet automatically sign into marketplace or supplier accounts.
• Listings and inventory: source and marketplace URLs and product identifiers, titles, descriptions, images/image URLs, brands, variations, prices, availability, delivery information, listing/vault records, scan results, deletion queues, and automation settings and history.
• Orders and fulfillment: customer/recipient names, delivery addresses and order details needed to perform enabled fulfillment workflows; marketplace and supplier order identifiers, purchase amounts, earnings, and fulfillment status. Cloud records include customer names, order identifiers, amounts, status, and spreadsheet references. We do not intentionally collect or store full payment-card numbers or card security codes.
• Buyer communications: enabled eBay fulfillment generates, stores, sends and verifies buyer delivery messages. The workflow reads relevant conversation messages and timestamps to confirm sending and avoid duplicate messages. Message content is processed locally and sent to eBay; fulfillment status and diagnostics may be synchronized to AWS. We do not use buyer conversations for unrelated purposes.
• Service operation: timestamps, run and installation identifiers, errors, relevant page URLs, account activity, and technical/service logs. Hosting and service providers may process connection metadata such as IP addresses. The extension may record interactions with Amazon verification screens to support its automation workflow.
• Google Sheets: spreadsheet identifiers, tab names, row references, and relevant spreadsheet content accessed or entered when you enable spreadsheet-based fulfillment. The current Sheets integration operates through the signed-in Google Sheets webpage using browser automation; it does not request Google OAuth API scopes. We access website content needed for enabled features, not unrelated browsing history.

How we use information

We use information to authenticate users; operate listing preparation and publishing; synchronize vaults; check source prices, stock, and delivery; run enabled schedules; end listings according to configured rules; process user-enabled fulfillment and spreadsheet updates; provide support; and maintain security and service reliability. Starting automation can publish or end marketplace listings. Enabled fulfillment can perform purchasing actions using your signed-in marketplace or supplier session. Settings and automation controls determine which workflows run.

Local storage and cloud processing

The extension stores settings, session tokens, product data, queues, and activity locally in Chrome storage. Relevant account, listing, vault, order, and diagnostic records are transmitted to our AWS-hosted backend and made available through the website. FreshCrawl receives source product identifiers and related request parameters to return product information for tracking. We do not send FreshCrawl your marketplace passwords or payment-card details.

Sharing and access

We share information only as needed to operate the disclosed service, with Amazon Web Services (AWS) for authentication, hosting, storage and processing; FreshCrawl for product checks; Amazon, Walmart, eBay, Poshmark, and Mercari when involved in workflows you enable; and Google when you use Google Sheets or contact us through our Gmail support address. These services also handle information under their own policies. Authorized Limits Express operators may view the account, listing and order information you expressly authorize them to access for service operation or support. Other human access is limited to legally permitted security investigations or legal requirements.

We do not sell user data, use it for personalized advertising, provide it to data brokers, or use it for creditworthiness or lending decisions. We may disclose necessary information to comply with law or address fraud, abuse, or security threats. A transfer as part of a business merger, acquisition, or asset sale requires the prior explicit consent required by applicable policy.

If you provide customer or other third-party information, you must have authority to use it for the enabled workflow and provide any notices required of your business. This does not limit our own obligations under this policy.

Chrome Web Store Limited Use

Our collection, use, and transfer of user data comply with the Chrome Web Store User Data Policy, including its Limited Use restrictions. Our use of user data is limited to providing and improving the disclosed seller-management features and their necessary operation and security. Our use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not use Google data or other user data for unrelated advertising or resale.

Retention and deletion

We retain information while your account is active as needed to provide the service. After cancellation or a verified deletion request, our team will delete your account-associated personal data from systems we control within 30 days, except information we must retain to meet legal obligations. Any legally required retained information is restricted to that purpose. This is a deletion service commitment; it does not mean that merely uninstalling the extension automatically deletes cloud records.

To request access, correction, cancellation, or deletion, email limitsexpresswholesale@gmail.com from your account email where possible and identify the account. We may verify authority before acting; do not send passwords or payment-card details. The 30-day commitment includes account-associated data in our active storage, diagnostic records, exports and backup copies under our control, except legally required retained records. We verify deletion across those locations as part of processing a request. Local extension data is removed by uninstalling the extension or clearing its data. Copies held independently by marketplaces, suppliers, Google, or other third parties must be managed through those services.

Security and your choices

We use HTTPS for service communications and account-based authorization to restrict access. Local extension data depends on Chrome and your device's security; protect your browser profile and signed-in accounts. No system can guarantee complete security. You can stop automation, disable schedules, sign out, adjust extension site access, or uninstall the extension. Use “Withdraw data consent” in the extension login/dashboard or website footer to remove the saved consent and sign out on that browser. Each control affects only the website or extension where you use it. Extension withdrawal blocks subsequent authenticated extension requests until you agree again; it does not itself delete existing records or stop previously scheduled cloud work. Email us to request account cancellation or deletion, or to withdraw consent for ongoing cloud processing. Stopping local automation does not necessarily cancel a cloud scan or request already submitted; contact us if you need help stopping cloud processing.

Updates and contact

We will update this page and its date when practices change. Material changes requiring additional consent will be presented before the new collection or use begins. Questions and privacy requests: limitsexpresswholesale@gmail.com.