Privacy Policy
How EzSeller collects, uses, shares, and deletes data for sellers and ChatGPT / MCP users.
Last updated: 5 November 2026 · Operator: SMAT Designs · Contact: onboarding@smatdesigns.com
1. Who this covers
EzSeller is Amazon seller-operations software operated by SMAT Designs. This policy covers the EzSeller website, account system, Amazon Seller Central connection, billing, and the tenant-scoped Model Context Protocol (MCP) endpoint used by compatible AI clients — including ChatGPT / OpenAI when you install or connect the EzSeller plugin, plus other OAuth-authorized MCP hosts you choose.
2. Categories of personal and seller data we process
Depending on how you use EzSeller, we may process:
- Account data: work email address, display or company name you provide, workspace/tenant identifiers, membership role, and sign-in session metadata.
- Amazon authorization data: Amazon OAuth tokens and related connection state, encrypted and stored server-side so EzSeller can call Amazon SP-API on behalf of your workspace. Tokens and passwords are not intentionally returned in MCP tool results.
- Amazon seller-operations data: marketplace and product identifiers (for example seller SKU, ASIN, FNSKU, UPC), your Amazon store name, listing and catalog state, FBA inventory and ledger evidence, Sales & Traffic and related performance metrics, financial events and fee estimates, order identifiers associated with the financial events you ask about, reimbursement and settlement evidence, including the disbursement account tail (the last characters of the payout account on file, shown to identify a settlement's destination), Seller Account Health signals, and similar fields required to answer an authorized tool request.
- Amazon Ads and agency data: advertiser profile identifiers, agency client-organization and manager-account identifiers, and advertising performance metrics, returned when you use Amazon Ads or agency tools so the requested account can be scoped.
- Operational evidence: Amazon API request identifiers, payload hashes, approval records, and security/workflow audit events used for provenance, abuse detection, and support.
- Tool-response evidence summaries: MCP tool results include a bounded evidence summary (whether Amazon data was observed, when, and what remains unknown) and, for report and audit tools, report and audit reference identifiers you can quote to support.
- Billing data: Stripe customer and subscription references, plan/entitlement state, and invoice-related metadata. Card numbers are handled by Stripe, not stored on EzSeller workers.
- First-party acquisition measurement: an opaque browser correlation cookie plus bounded page path, UI surface, referrer host, and UTM fields (see section 6).
We do not intentionally collect payment-card PAN/CVV, government IDs, PHI, Amazon passwords, MFA codes, or buyer PII (names, shipping addresses, buyer messages, tax-remittance PII) for launch seller-operations workflows.
3. Purposes of use
- Authenticate you, maintain workspace tenancy, and enforce entitlements.
- Connect to Amazon SP-API for the marketplaces you authorize and run the seller-operations workflows you request.
- Return tool results to the OAuth-authorized AI client (for example ChatGPT) that you connected to your workspace.
- Bill for paid plans, prevent abuse, debug failures, and meet security and legal obligations.
- Measure whether public pages lead to signup and Amazon connection, using minimized first-party events.
4. Recipients and service providers
Data may be processed by:
- SMAT Designs / EzSeller — application operator.
- Cloudflare — application runtime and edge delivery.
- Neon — application database storage.
- Stripe — payment processing and subscription state.
- Resend — transactional account email (for example magic-link sign-in).
- Amazon — when you authorize Seller Central; Amazon processes data under Amazon’s terms for SP-API.
- Connected AI clients — including OpenAI / ChatGPT when you use the EzSeller ChatGPT plugin or MCP connection, and any other MCP host you authorize. Those clients receive the MCP tool results for your workspace and process them under their own privacy terms.
EzSeller does not sell personal data. We do not use Amazon seller payloads for advertising networks or unrelated profiling.
5. MCP / ChatGPT tool responses
When an authorized client calls EzSeller tools, responses are limited to fields needed for the requested seller-operations task (for example the seller SKU or order identifier named in the request, relevant metrics, diagnoses, and evidence summaries). Public ChatGPT/MCP responses filter account identity and contact fields such as user/customer IDs, email addresses, phone numbers, buyer/recipient contact data, plus internal tenant and grant IDs, request IDs, raw provider payloads, and debug/trace data. Amazon access tokens, refresh tokens, passwords, and card data are not intentionally included. Host platforms (including ChatGPT) may retain conversation content under their own policies. Agency and Ads tools return the client-organization, manager-account, and advertiser-profile identifiers required to scope the requested work.
6. First-party acquisition measurement
EzSeller sets an HttpOnly Secure cookie (ezseller_acq, Max-Age 90 days) with an opaque correlation id and records first-party conversion events (page path, surface, referrer host, UTM fields). The acquisition design is not meant to store marketing email addresses, IP addresses, user-agent strings, Amazon credentials, or access tokens. After sign-in, eligible anonymous events may be associated with the workspace for aggregate conversion measurement. Telemetry failures do not block signup, billing, or Amazon connection.
7. Retention timelines
- Amazon-sourced seller data: kept only for the authorized purpose. After Amazon disconnect/revoke, access termination, or equivalent loss of authority, Amazon-sourced payloads are purged as soon as practical and within a maximum 30-day deletion window (cleanup is retried if interrupted), unless a specific legal, tax, or regulatory obligation requires a limited retained copy.
- Account, membership, entitlement, and connection metadata: retained while the workspace is active and for a reasonable period afterward as needed for security, billing reconciliation, fraud prevention, and legal obligations; deleted or anonymized when no longer required after a verified deletion request.
- Browser sessions: ChatGPT Sign-in-with-ChatGPT / comparable OpenAI session cookies are bounded (currently up to 30 days). Synthetic reviewer sessions used for directory review are short-lived (currently 8 hours).
- Acquisition cookie / events: cookie Max-Age 90 days; event rows retained for conversion analysis and deleted or dissociated when no longer needed or upon verified account deletion where feasible.
- Security and audit records: retained as long as reasonably necessary for security monitoring, incident response, and abuse detection.
- Billing records: Stripe retains payment records under Stripe’s policies; EzSeller retains plan/entitlement references as needed for access control and accounting.
8. Your controls
- Revoke Amazon authorization and start Amazon-data deletion from EzSeller connect/disconnect flows.
- Request account data deletion or access revocation via the public support page or onboarding@smatdesigns.com. Do not email Amazon credentials or tokens.
- Disconnect the EzSeller MCP / ChatGPT plugin in the host product to stop new tool calls from that client.
- Subscription cancel changes paid access; it is not the same as Amazon revoke or full data deletion.
9. Restricted Amazon buyer data
Launch workflows do not require Amazon restricted buyer PII roles and do not need buyer names, shipping addresses, buyer-message content, or tax-remittance PII. A future feature that needs restricted Amazon data would require separate role approval plus updated security and retention controls before launch.
See Amazon SP-API access and security for the current launch boundary and security summary.
10. Changes
We may update this policy as the product changes. The “Last updated” date at the top will change when we do. Material changes that affect ChatGPT / MCP users will be reflected on this page before or as those changes ship.