Privacy Policy

1. Amazon SP-API Data Retention

EzSeller processes Amazon seller data on behalf of the authorized workspace and returns supported results to the connected AI client through the tenant-scoped MCP endpoint. Amazon credentials are handled server-side and are not intentionally returned to the AI client. EzSeller also stores account, membership, entitlement, connection, approval, evidence, and audit metadata needed to operate and secure the service.

• Provider Evidence: When you execute a tool, we may store the Amazon API Request IDs and essential payload hashes in our evidence store to prove data provenance.
• Audit Ledger: Our audit_events table stores security and workflow audit records. This is retained for security auditing and anomaly detection.

2. Data Flow and Service Providers

For supported workflows, data flows from Amazon to EzSeller and then to the OAuth-authorized AI client. Neon provides application data storage and Stripe processes billing. Connected AI clients process the MCP results under their own terms and privacy practices. EzSeller does not require a separate backend implementation for each AI client.

3. Authentication & Tenancy

EzSeller uses email sign-in links for account access and a separate OAuth flow for compatible MCP clients. Stripe processes billing; Neon stores account, membership and entitlement records. Requests are checked against the authorized workspace.

4. First-Party Acquisition Measurement

EzSeller records a small set of first-party conversion events so we can understand whether public pages lead to signup and Amazon connection. These records use an opaque first-party correlation identifier plus bounded page, surface, referrer-host and UTM attribution fields. The acquisition-event table is not designed to store marketing email addresses, IP addresses, user-agent strings, Amazon credentials or access tokens. After successful sign-in, eligible anonymous acquisition events may be associated with the workspace so aggregate conversion can be measured. Telemetry failures do not block signup, billing or Amazon connection.

5. Data Deletion and Revocation

Subscription cancellation changes paid access according to the billing lifecycle; it is not the same as a data-deletion request. Contact the onboarding team to request deletion. The team must review applicable security, billing and legal retention requirements before confirming completion.

Use the public support page or reply to your EzSeller onboarding email for a data-deletion or access-revocation request. Do not send Amazon credentials or access tokens. EzSeller does not promise a fixed deletion interval here because retained security, billing, evidence, or legal records can have different applicable requirements.