Privacy Policy

1. Who this policy covers

SellerBay is responsible for the information handled in its own services under the SellerBay name. This policy covers sellerbay.net, SellerBay-operated tools and the SellerBay Discord bot. It does not replace the policies of Discord, payment providers, marketplaces or independent vendors you choose to use.

For privacy requests, Join SellerBay on Discord and open #help-desk to start a private ticket with the SellerBay Team. A paid subscription is not required to request help.

2. Information we handle

• Account and membership information: username, email or profile details when provided, authentication information, account identifiers, Discord identifiers and linked membership or subscription status. For linked Apex accounts, SellerBay may use existing account information and credential verification to support access and migration.
• Billing information: selected plan, payment-provider identifiers, payment and subscription status, transaction references, the checkout terms and prices you accepted, their acceptance time and related support records. Whop handles new membership checkout payment details. Stripe and PayPal continue to handle existing billing where applicable. Do not send full card numbers to SellerBay support.
• Workspace and support content: listing inputs, inventory records, images, receipt fields, feedback, vendor or product suggestions, tool requests and support messages that you provide. A receipt you create may contain customer or transaction information; enter only information you are authorized to use.
• Community information: Discord messages processed as described below, message and channel identifiers, ticket activity, communication preferences and relevant follow-up records.
• Technical information: request and security logs, IP addresses, device or browser information available with requests, error reports and service-usage records.

Information may come from you, your use of the service, connected platforms and payment providers. Avoid putting passwords, API keys, full payment details or sensitive personal information into tool prompts or community messages.

3. Why we use information

We use information to provide accounts and tools, verify payments and membership, link Discord access, operate referrals, respond to support requests and maintain service security. We also use relevant community activity to identify interest in SellerBay, help the Team follow up and offer product assistance. AI-generated assessments are suggestions for the Team and do not determine legal, employment, credit or similar eligibility.

We may use information to investigate misuse, resolve billing disputes, meet legal obligations and improve service reliability. For billing disputes, relevant payment records, accepted checkout terms, membership periods and records of successful authenticated tool requests may be shared with the payment provider. An automated response may submit those factual records; cases with missing or conflicting evidence require Team review. These records do not include passwords or the contents of tool requests. We do not need access to unrelated private conversations to provide these features.

4. Discord and AI processing

Member assistance: the bot replies to current SellerBay server members in DMs and when explicitly mentioned or replied to in configured public community channels. Limited message text, recent context and relevant SellerBay help material are sent to OpenAI to generate an answer. The bot identifies itself as AI. It does not read attachments as part of these replies or access private account records to answer questions.

Public-message interest detection: eligible messages in #seller-chat and #small-wins, including their public threads, may be sent to DeepSeek to identify interest in SellerBay. Positive results can create a private Team card containing a short quotation, source link and suggested follow-up. Private tickets and DMs are excluded from this lead analysis. Paying members and staff are excluded from lead classification.

Greetings and outreach: new members may receive a welcome DM. An eligible prospective customer may receive an initial AI help DM based on public interest, subject to limits and communication preferences. Type stop to turn off proactive DMs, forget to clear saved bot chat context and turn off outreach, or start to allow outreach again. Stopping DMs does not itself delete public Discord messages or stop public-message analysis; contact the Team for a broader privacy request.

Website AI: features such as listing assistance may send the relevant product details and your tool inputs to the configured OpenAI or DeepSeek service. Only submit information needed for the task. Provider processing and retention can differ from the Discord assistant.

The assistant uses locally maintained SellerBay help content. Basic credential and contact-detail filtering reduces accidental disclosure in chat requests but cannot guarantee that all personal information is removed. API requests are not a promise of anonymous processing or zero provider retention. Human Team members can read tickets and follow-up cards for their support work.

5. Cookies and browser storage

SellerBay uses necessary cookies or browser storage for sign-in, preferences and referral rewards. Connected payment and authentication services may use their own storage for security or service delivery. These functions are separate from optional website analytics.

Optional first-party analytics: only after you choose Allow analytics, SellerBay uses host-only browser and session cookies to measure page visits, time actively visible, traffic sources and campaign labels. An observed session ends after 30 minutes of inactivity or 24 hours. A browser identifier lasts at most 90 days. These counts describe consented browser activity, not unique people or activity across devices. Independent shop domains keep separate identifiers.

Analytics stores route templates instead of private order or account IDs, referrer hostnames instead of full referring URLs, and bounded UTM campaign labels. It does not record page titles, arbitrary URL queries, form contents, passwords, payment details or session replay. Raw IP addresses and user-agent strings are not stored in analytics; the server derives broad browser and device categories. Necessary security logs are separate.

For an account signed in after consent, the server can associate the consented session with verified signups and purchases. Financial totals come from verified operational records even when analytics is declined; those records remain unattributed. Campaign attribution describes a recorded source and does not prove that a campaign caused a purchase. Referral reward attribution remains separate.

Use Privacy choices on the website or Account settings to change your choice. Declining prevents optional collection. Withdrawing clears the analytics queue, deletes the browser identifiers and associated analytics details, and removes attribution from retained financial facts. If disconnected, removal retries when you reconnect. Anonymous aggregates and required account or financial records are retained under their separate purposes. Global Privacy Control and Do Not Track signals disable optional analytics, including when a previous choice allowed it. Older generic cookie acceptance does not enable this analytics system.

You can also manage stored site data through your browser. Clearing necessary storage may sign you out or affect referral rewards. The service has no configured advertising-network tracking integration.

6. Who receives information

We share information with service providers as needed for the purposes described here: hosting and infrastructure providers, Whop, Stripe and PayPal for the applicable billing, Discord for community functions, OpenAI and DeepSeek for the applicable AI assistance, listing tools and public-message interest analysis.

Authorized Team members can access relevant account, support and community records for their work. We may disclose information when legally required, to protect rights and service security, or as part of a business transfer subject to applicable safeguards and notice requirements.

We do not sell personal information for money. The current service does not share information with advertising networks for cross-context behavioral advertising. If these practices change, we will update this policy and provide any required choices before the new use.

When you open an external service, information you provide to it is governed by that recipient’s practices. Supplier contact records are private to the SellerBay team. Fulfilling an order requires sharing the delivery details needed by the supplier and shipping provider.

7. How long information stays

We keep account, workspace, billing and support information for as long as reasonably needed to provide the service, meet legal obligations, prevent abuse or resolve disputes. The appropriate period depends on the kind of record and why it is needed. Successful tool-request records collected for billing evidence are retained for up to 400 days. Relevant records attached to an open dispute may be retained with the case until it is resolved and any required recordkeeping period ends.

Optional analytics event and session details, and browser identifiers, are retained for up to 90 days. Anonymous daily aggregates are retained for up to 13 months. Authorized Admin Members can access aggregate reports and bounded exports; analytics does not provide a raw session replay or individual browsing-history screen. Verified financial facts have separate operational retention, and a privacy choice does not delete them.

The Discord assistant’s short local conversation context expires after 24 hours and is removed by routine cleanup. Reply identifiers used to avoid duplicate processing are kept for up to seven days, short usage-limit events for two days and AI spend records for 100 days. Minimal opt-out and once-only outreach records remain so preferences and contact limits can be respected.

Public-message identifiers used by lead detection expire after seven days. Unattended new lead assessments also expire after seven days. Follow-up records marked contacted, dismissed or converted can remain until reviewed or deleted; a source message being removed, edited or made private can withdraw its quoted evidence when detected. Support ticket records and owner announcement records have separate operational retention.

Deleting bot context does not delete messages from Discord, records held by an AI provider, required billing or security records, or copies awaiting backup rotation. Those systems and copies may have different retention periods. Contact the Team to request broader deletion.

Connected marketplace accounts

When you connect eBay, SellerBay stores the connection credentials encrypted on its server. Credentials are not sent to other customers or included in public pages. Selected listing, order and performance information is stored to synchronize the items you manage and show reports.

Disconnecting stops SellerBay automation for that connection and removes its stored credentials. The account deletion process removes the connected marketplace data within its scope, subject to the recordkeeping limits described in this policy. It does not delete your eBay account or listings. Payments made on eBay are handled through the seller’s eBay account and do not become a SellerBay wallet balance.

8. Your choices and privacy requests

You can review available profile controls and request account deletion in Account settings. For access, correction, a copy of information, deletion or another privacy request, Join SellerBay on Discord and open #help-desk to start a private ticket with the SellerBay Team. A paid subscription is not required to request help.

Depending on where you live and whether a law applies to SellerBay, you may have rights to know what information is collected, obtain a portable copy, correct or delete information, restrict certain uses, object to processing, opt out of covered sales, sharing or targeted advertising, or appeal a denied request. We will handle applicable requests without unlawful discrimination. You may also contact the relevant privacy regulator.

We may need to verify that a request concerns your account, or verify an authorized agent’s authority. Provide only what is reasonably needed for that verification; do not send a password. Some information may need to be retained for security, transaction records or legal obligations. We will explain applicable limits when responding.

The current service does not conduct the advertising sale or sharing described above. Global Privacy Control and Do Not Track turn off optional website analytics. Browser privacy signals do not turn off necessary account or billing processing. You can ask the Team about an applicable opt-out or other privacy right.

9. Security and international processing

We use access controls and other technical and organizational measures intended to protect information. No storage or transmission method is completely secure. Keep credentials private and report suspected account compromise through support.

SellerBay and its providers may process or store information in countries other than where you live, including the United States. Those countries may have different privacy laws. We will apply any safeguards required by applicable law for those transfers.

10. Children

SellerBay is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided information, contact the Team so we can investigate and take appropriate steps. Other minimum-age rules may apply in your location or on connected platforms.

11. Policy updates

The date above identifies this version. We will update this page as the service changes and provide notice of material changes where appropriate or required by law. Our Terms of Service explain account use, subscriptions and cancellation.