ListPilot ("we", "our", or "us") provides a Chrome browser extension and web tools for listings, inventory, order tracking, and shipping. This Privacy Policy explains what information we collect, how we use it, and your rights.

1. Information We Collect

ListPilot collects the following information:

• License key and browser storage: Your key is stored in your browser and sent to our backend to authenticate requests. Settings and tool records may also remain in browser storage. Signing out removes the website's shared key, but does not erase all locally saved tool records.
• Device and account identifiers: The extension creates a random ID for each device. License checks store a hashed (SHA-256) copy of that device ID. We also store license/customer identifiers, purchase email, and subscription status to activate and protect the service.
• License checks: Each license check records the time, your IP address, the hashed device ID, and the result. These records are kept for 90 days, or longer while an abuse case or legal hold involves the license.
• Device settings copy: For PRO licenses, we keep a copy of each device's ListPilot settings (such as your AI provider, model, and feature toggles) on our server. It records only whether an AI key is saved, never the key itself. This copy is stored with that device's ID as the extension created it, not hashed.
• Checkout campaign labels: If an ad link contains a source, medium, campaign, or keyword label, we attach those labels to Stripe Checkout and billing records. We record checkout, trial, and payment outcomes with Stripe object references to measure which campaigns lead to paid purchases. The labels come from URLs and may contain text selected by the link creator; each label is limited to 200 characters. The reporting feature does not read Google auto-tagging click ID parameters or send customer details to an ad platform.
• Abuse-prevention signals: To prevent repeated trial abuse, we may compare exact or provider-safe email representations, device identifiers, license and Discord identifiers, and Stripe customer/payment references. IP address, name, and user-agent information may be retained as corroborating security evidence, but a shared IP, name, or network alone is not an automatic block.
• Product and marketplace data: Features you use read relevant product, listing, order, and shipment information. Listing and review generation sends relevant product text, marketplace choices, and any reviewer notes directly from your extension to your selected AI provider. Imported inventory, listing details, marketplace connections, and processing results may be stored by our backend to provide crosslisting and tracking.
• Tracker and cashout records: Records you enter, import, or synchronize can include item and order details, account labels, contacts, notes, prices, refund and payment details, and shipping or tracking information. These records may be saved in your browser and our database.
• Diagnostics and feedback: Error reports may include the affected page or marketplace URL (without its query string), error messages, recent extension log lines (up to about 50,000 characters), and diagnostic details associated with your license. Reports about AI listing or review steps can also include the prompts sent to your AI provider and what it wrote back, which can contain product text and your review notes, plus the product title and details, each cut to a set length. eBay pricing feedback you send includes the product title, description, and any note you write. Before a report is sent, the extension removes license keys, API keys, tokens, passwords, email addresses, phone numbers, and the names, street addresses, and ZIP codes it can recognize. Error reports are stored as issues in our private GitHub repository. Suggestions you submit to the feedback board and our responses may be displayed publicly, including in our Discord server.
• Discord: If you link your Discord account to your license, we store your Discord user ID with your license.
• Referral and checkout attribution: A referral code may be kept in browser storage for up to 30 days and sent at checkout to credit the referrer. A paid-search keyword in the current purchase journey may be sent to our backend and Stripe as checkout metadata.
• Listing count: A counter of how many listings you've generated, stored in our database associated with your license.

2. Information We Do Not Collect

• We do not collect a general browsing-history log. Features and diagnostics may send the relevant product, marketplace, or page information described above. Our public website uses cookieless analytics, and a Google Ads measurement tag on some pages, as described in section 4.
• We never receive your AI provider API keys. They are stored in the extension's browser storage and sent in request headers directly to the selected provider to authenticate generation requests.
• We do not sell or rent your personal information. Apart from the Google Ads measurement described in section 4, we do not share it with third parties for marketing purposes.
• We do not receive or store full payment card numbers. Stripe processes payments; we may receive Stripe customer, subscription, payment-intent, and opaque card-fingerprint references needed for billing and abuse prevention.

3. How We Use Your Information

• To validate your license and prevent unauthorized sharing.
• To deliver your license key after checkout.
• To display usage statistics in your account dashboard.
• To synchronize tool records, run marketplace workflows, diagnose failures, respond to feedback, attribute referrals and checkout sources, and measure checkout, trial, and paid purchase outcomes by campaign in aggregate.

4. Third-Party Services

• AI providers: Depending on your selection, generation requests go to Anthropic, OpenAI, or Google Gemini. The selected provider receives the request content and API credential and processes them under its own terms and privacy policy.
• Stripe: Payment processing and subscription management. Stripe's Privacy Policy applies.
• Hosting and storage: GitHub Pages serves our website, Render hosts our backend, and Supabase stores license records, tool records, and photos you upload. Uploaded photos are stored at a public link, so anyone who has the link can view the photo. Requests to these services necessarily include network information such as an IP address. Error reports are stored as issues in a private GitHub repository.
• Shipping rates: When you request rates, Shippo receives the sender and recipient addresses for that shipment (including any name, phone, or email on it) and the package size and weight. These are sent from your browser with your own Shippo API key. Your Shippo key stays in the extension for the current browser session and is never sent to us. Pirate Ship receives the origin and destination ZIP codes and the package size and weight, entered into its rate calculator in your browser.
• Umami: Our public pages use cookieless analytics for page views and selected link clicks, including the selected checkout plan and billing interval. We keep the page path and allowed source, medium, campaign, keyword, or content labels from UTM parameters, while removing ad click IDs, promo codes, and other URL parameters. We reduce referring URLs to their origin before sending analytics events. Umami's Privacy Policy applies.
• Google Ads: Our home, pricing, comparison, setup guide, stats, changelog, checkout, and activation pages load Google's ad tag. For every visitor to those pages, Google receives the page address, your referring site (reduced to its origin), and standard browser and network information such as IP address, and the tag sets cookies so Google can tell which ad clicks led to a trial sign-up. We send Google no email address, name, or license key, and we do not use this data for ad personalization or remarketing. Google's Privacy Policy applies.
• Other browser requests: Pages may load fonts from Google, product images from their source sites, and the spreadsheet import library from jsDelivr. Connected marketplace services receive requests needed for the features you use. Discord processes support conversations you choose to start there.

5. Data Retention

License and billing records are retained for the duration of your subscription and as needed for accounting, support, security, and abuse prevention. Active abuse-prevention records remain while the case is active. Resolved cases become eligible for scheduled deletion or anonymization after 90 days, unless a legal or accounting hold or unresolved enforcement or payment work requires retention. You may request deletion; a request involving an active security block may require manual review.

6. Your Rights

You have the right to access, correct, or delete your personal data. To exercise these rights, contact us at the address below.

7. Security

License keys are bearer credentials: anyone with your key may be able to access the associated web tools and records. New keys are randomly generated and checked against our license records; extension activation also checks device binding. Keep your key private and use a separate browser profile on shared devices. Website and API requests use HTTPS.

8. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated date.

9. Contact

For privacy questions or data requests, reach us in our Discord.

---