Privacy and data handling
The American Workshop · last updated November 18, 2026
Who we are and what this covers
The American Workshop is a small online store that sells on Amazon. Its owner, Trevor Davis, is responsible for how data is handled. This policy covers the private business application we use to run the store (listings, orders, supplier purchases, buyer messages, and advertising). The application has a single user, the owner; it is not a service offered to the public, and it has no customer accounts.
What we receive from Amazon
- Our listings and catalog data: our own listings, product prices, search terms and search-frequency ranks, and counts of competing listings.
- Orders: the Amazon order ID, purchase date, ship-by date, order status, items and quantities, and item prices.
- Fees, refunds, and reports: Amazon fees and refunds per order, sales and traffic reports, and advertising reports for our campaigns.
- Buyer messages: when a buyer writes to us through Amazon's Buyer-Seller Messaging, Amazon relays the message to our email. We keep the anonymized relay address Amazon assigns, the subject, and the text, so we can answer.
- Shipping addresses: not stored. Today the application does not receive buyer shipping addresses at all; supplier orders that need one are placed by hand from Seller Central. If Amazon later approves our application for its restricted shipping-address role, the address will be requested at the moment a supplier order is placed, passed directly to that supplier, and never written to our database, logs, or backups.
We do not receive or store payment details, buyer phone numbers, or buyer email addresses (only Amazon's anonymized relay addresses).
Why we use it
Only to run the store: fulfilling and tracking orders, answering buyers, setting prices and advertising budgets, and keeping our books and taxes. We do not sell data, use it for advertising profiles, or contact buyers outside Amazon.
Where it is stored
- In a single database on our server in Amazon Web Services (US East, Virginia), on a disk encrypted at rest with AES-256 keys managed in AWS Key Management Service.
- Backups: a daily copy on the same encrypted disk and a daily copy in a private, encrypted storage bucket in our AWS account, plus encrypted daily disk snapshots. Every backup is deleted after 14 days.
- All connections to the application use HTTPS (TLS). Access keys for Amazon and other services are kept in a file readable only by the application's service account, never in the database or logs.
Who we share it with
- Amazon, through the Selling Partner API and Amazon Ads API, to manage our listings, orders, and campaigns.
- Amazon Web Services, which hosts our server (infrastructure only; AWS does not access the data for its own purposes).
- CJ Dropshipping (our supplier), only what is needed to ship an order: the product, quantity, and shipping method, and, only if Amazon approves the restricted role described above, the buyer's name and shipping address for that order.
- Anthropic (Claude) or xAI (Grok), only when AI features are turned on: product information to draft listing copy, and a buyer's message text so a reply can be drafted for our review. Shipping addresses are never sent to them.
- Resend, our email-delivery service: our reply, its subject, and the Amazon relay address it goes to.
- Our inbound-email service (such as Postmark or CloudMailin), which passes Amazon's relayed buyer messages from our mailbox to the application.
- Phone and chat alerts to the owner (ntfy, Slack, or Discord) say only that a buyer is waiting or an action needs approval; they do not contain buyer messages or addresses.
We share data with no one else, except when required by law.
How long we keep it
- Buyer data (message text, relay addresses, reply drafts, and copies of that text in our notifications and AI logs) is deleted automatically 30 days after the order ships, or 30 days after the message if the buyer writes later or the message has no order. A message still waiting for our answer is kept until it is answered. Because backups are deleted after 14 days, deleted buyer data is gone from every backup within 14 days after that.
- Shipping addresses: never stored (see above).
- Order and financial records (order IDs, dates, quantities, prices, fees, refunds, supplier costs, and tracking numbers) are kept as business records for bookkeeping and tax purposes. They contain no buyer names, addresses, or messages.
- Security log (sign-ins, settings changes, and actions taken; no buyer data): 12 months.
How we protect it
- Owner sign-in with a password and an authenticator-app code (two-factor), with lockout after repeated failures; every sign-in and change is recorded in a security log kept 12 months.
- Programmatic access uses separate tokens with limited permissions (read-only, routine, owner); one-tap approval links are signed and expire within 48 hours.
- A firewall that allows only web traffic (HTTPS); no remote-login port is open, and administration uses AWS Systems Manager with its own logging.
- Intrusion detection and blocking (CrowdSec), daily anti-malware scans (ClamAV), automatic security updates, and AWS GuardDuty, Inspector, and CloudTrail monitoring of the server and account.
- Software dependencies are checked for known vulnerabilities before every release.
Security incidents
If we find or suspect that Amazon data was exposed, we contain it (including revoking the application's Amazon access and replacing every key), notify Amazon at security@amazon.com within 24 hours of detection, and inform anyone else as the law requires. To report a security concern to us, write to td1355@g.ucla.edu.
Questions and deletion requests
Buyers can contact us through Amazon's Buyer-Seller Messaging, and anyone can write to td1355@g.ucla.edu. On request we delete the buyer data we hold about an order (it is also deleted automatically as described above), and we answer within 30 days.
Changes to this policy are posted on this page with a new date.