How we handle Amazon data
Last updated October 29, 2026
Quince MCP follows Amazon's Acceptable Use Policy and Data Protection Policy for the Selling Partner API, and the Amazon Ads API terms. This page sets out what that means in practice.
What we access, and why
| Data | Why we need it |
|---|---|
| Advertising campaigns, keywords, targets and reports | To answer questions about ad performance and to propose and apply the ad changes you approve |
| Sales and traffic by ASIN | To compare ad results with total sales and conversion |
| Brand Analytics (Search Query Performance, Top Search Terms) | To show how your products perform on the searches that matter, for brand owners with access |
| FBA inventory | To warn you before spend goes up on a product that's running out |
| Listings, your own prices and Buy Box | To check listing status and to warn about and apply the price changes you approve |
| Fees and settlements | To work out profit and break-even ACoS with the costs you enter |
We don't request data the features don't use, and we don't access buyer personal information.
AI, accuracy and data freshness
- Quince MCP returns data and runs fixed calculations, such as ACoS, TACoS and break-even ACoS. The written answers and the proposals come from the AI app you connected. AI output can be wrong, so every change shows its numbers and needs your approval.
- Every result says which dates it covers and when the data was last synced from Amazon.
- Amazon Ads results for the most recent days can keep changing for up to 14 days while Amazon attributes sales, and we re-sync that window every day.
- Seller Central reports arrive with Amazon's own delay, and Brand Analytics reports are weekly. When Amazon hasn't reported a day yet, it comes back as missing with the reason, never as zero.
- Before applying a change we check its inputs against your live account, and after applying we read it back from Amazon.
What we don't do
- We don't sell, rent or license Amazon data.
- We don't combine data across customers, share one customer's data with another or publish insights about Amazon's business.
- We don't use Amazon data to train AI models.
- We don't contact Amazon customers or help anyone solicit, filter or manipulate reviews.
- We don't ask for Seller Central passwords or access keys.
Who receives the data
You receive your data in the AI app you connected, and that app's provider handles it under its own terms. Apart from that, only the service providers below handle Amazon data, and only to run Quince MCP:
| Provider | What it does for us | Data it handles | Location |
|---|---|---|---|
| Vercel Inc. | Hosts the website, the MCP server and the approval pages | Requests in transit, account data, Amazon data while a request is served | United States |
| Neon Inc. (on Amazon Web Services) | Database | Account data, encrypted Amazon tokens, synced Amazon data, the change log | United States |
| Amazon (Selling Partner API, Amazon Ads API) | The source of your Amazon data and where approved changes are sent | API requests and tokens in transit | United States and the marketplace region |
Retention and deletion
- We keep Amazon data only as long as the Service needs it, at most a rolling 24 months.
- When you disconnect, close your account or Amazon asks us to, we revoke the tokens immediately and permanently delete all of that Amazon data, including every live copy, within 30 days.
- Amazon data is tagged with its source account so it can be found and deleted completely.
Security
Encryption, access control, logging and our incident process are on the Security page. Incidents involving Amazon data are reported to Amazon within 24 hours of detection.
Raise a concern
If you think Quince MCP is being used in a way that breaks Amazon's policies, email support@quincemcp.com with "Policy concern" in the subject. We block accounts that misuse the Service and report them to Amazon where its policies require.