Privacy policy.
What we collect
- Anonymous analytics via Vercel Analytics and Google Analytics 4 (page views, referrers, country, device class). No personally identifying information.
- Email + name when you submit a prep-center claim form, listing-suggestion email, or contact form.
- Claim verification codes and tokens when you claim a listing with a code we email to the listing's published address, or with a file or meta tag on the listing's website. We keep a code only as a keyed hash, with the address we sent it to, and a website token as a random string with your claim. A code expires after 15 minutes and a website token after 72 hours.
- Cookies for session continuity if you sign in to manage a claimed listing (Supabase Auth + magic-link email). When you ask for a sign-in link, we keep the address you typed in a cookie on your browser for up to one hour so the next page can show it, and scripts cannot read that cookie. If the sign-in link in your shortlist email has expired or was already used and we email you a fresh one, a second cookie holds a reference to your match request for up to one hour so the next page can say where we sent it, and scripts cannot read that one either.
- A first-party attribution cookie set on your first page view, which stores the page you landed on, the domain of the site that referred you (the domain only, not the full address), and any campaign tags in the link, including our own short tag for which of our posts or videos the link was in. It expires after 30 days, holds no identifier for you, is not readable by any other site, and is not shared with anyone. If you later submit a match request, those three values are stored with it so we know which pages bring sellers to us.
- Referral links. If you arrive through a prep center's referral link, we record which center's link it was. It is saved with the form that link opens (a match request, or an application to list your own center) when you submit it, and it is not part of the attribution cookie. That center's dashboard on this site shows a row for each match request that came through its link, with the date and whether it qualified for a credit. If you tell us you signed with another center on your shortlist, it can also show that, but not which center. For an application, it shows a row once the center you applied to list is published. It never shows your name, email, company or requirements.
What we don't collect
- Behavioral tracking for advertising. We don't run ads.
- Cross-site cookies, device fingerprints, or third-party trackers beyond GA4.
- Card numbers. Operator subscriptions and one-off purchases run through Stripe Checkout and Stripe Elements, so card details go straight to Stripe and never touch our servers or our database. We store only Stripe's identifiers and the resulting subscription state.
- Phone numbers (unless you voluntarily provide one in a claim or contact form).
Amazon Connect
If you connect your Amazon seller account, the app reads it to build your prep analysis. Amazon grants apps access by role, and a role can allow changes as well as reads, so the limit is in our code: it requests reports and reads data, and it never creates, edits or deletes a listing, shipment, order or setting in your account. It reads no buyer names, addresses or other buyer details.
What we keep with your analysis: monthly units and ordered product sales for your US store, with the units for each month split between FBA and FBM, and up to 100 active listings with title, SKU, ASIN, listed price, merchant stock and whether the listing is FBA or FBM. For up to 10 SKUs we also keep the units and ordered product sales of each, and from the Amazon catalog its title, brand, product type, category, size and weight, with our estimated size tier. We also keep the prep profile we compute from your data: totals and monthly averages of your units and sales, how many SKUs need each kind of prep, and our estimate of Amazon prep fees for them.
With the connection itself we keep the encrypted token Amazon issues to the app, your Amazon seller ID, the IDs of the Amazon marketplaces linked to your account, and your store name as Amazon shows it, which we use to fill in the company field when you finish connecting. What you submit in that field is kept with your match request, like your other answers.
We automatically delete everything listed above no later than 18 months after you last connect, except your seller ID and marketplace IDs, which stay on our record of the connection, with its dates and its link to your request or account. On request we delete all of it, those two included. Revoking the app in Seller Central under Apps and Services stops all reads at once.
Third parties we share with
- Vercel - hosts the site; sees request metadata.
- Supabase - database + auth; stores claim records.
- Resend - delivers transactional emails (magic-link sign-in, claim verifications).
- Google Analytics 4 - aggregated traffic analytics.
- Stripe - processes operator payments and subscriptions. Stripe receives the billing details you enter on its own checkout surface.
- OpenAI - we send text to OpenAI's API for the following. When you submit a match request, the name, email, company, company website and answers you typed into the form are sent to check that the request comes from a real seller, and your answers and company website (without your name or email) are sent to rank which verified centers fit it. Nothing an AI model writes is sent to you about your match request: the acknowledgement and your shortlist are assembled from your form answers and our own center data. Email sent to hello@fbaprepfinder.com or in reply to our emails (the sender's name and address, the subject and the message text) is sent to sort it, to draft a reply and to check that draft before it goes out, so a reply from us may be drafted with AI help. Public Reddit posts we monitor (the post text, the subreddit and the author's username) are sent to judge whether the author is looking for a prep center, and for a post that is, the post text and subreddit (without the username) are sent again to draft a suggested reply that a person may edit and post. Requests go out with OpenAI's option to keep the response for later retrieval switched off.
- Google (Gmail API) - our hello@ mailbox sends and stores correspondence with buyers and operators.
- MillionVerifier - receives an email address on its own to check the mailbox exists before we write to it, so a reply does not bounce.
- Slack - new match requests and operator events post to our Slack workspace so a person on our team sees them quickly. One channel there is public, so people outside our team can see what is posted in it. In that channel a seller's request names the seller only by first name, the company name they typed on our match form and a partly hidden email address. Nothing read from a connected Amazon account is posted in it. A request you send when you finish connecting Amazon shows no company there, because that field starts out as your store name. Full email addresses, phone numbers and last names go only to our private channels, and the full record stays on our admin site, which needs a sign-in.
- The prep centers we send your request to (requests made on our current matching form): once you confirm your email, we send a summary of your answers to up to 25 prep centers that fit. The summary holds where you are with FBA, your timeframe, your monthly volume band, product categories, marketplaces, sales channels, services, special handling, and the state or region where you want a prep center. If you answer the "Tell us about your shipments" questions in your portal, the summary also holds how your shipments arrive and whether you need storage. It holds your SKU count and cartons a month too, but only as ranges (such as "11 to 50"). It never holds your name, business, website, email, phone or anything you typed in your own words. A prep center you pick as the one you use now is not sent it. Nothing that identifies you goes to any prep center until you press Accept introduction on it. Then your name, business, email and answers (your exact numbers too), plus your website and phone if you gave them, go to that prep center so we can introduce you. A prep center pays us a fee for an introduction you accept (its first is free); Featured prep centers pay for placement instead. We store which version of this wording you saw. To withdraw afterwards, email hello@fbaprepfinder.com: we close any summaries still open and stop passing your details on. We cannot unsend an introduction a prep center already received.
- The prep centers you ask us to introduce (requests made after we added Introduce me and before we added Accept introduction): nothing that identifies you goes to any prep center until you press Introduce me on it. Then your name, business, email and answers, plus your website and phone if you gave them, go to that prep center so we can introduce you. Prep centers on our introduction plan pay us a flat fee for that introduction; Featured prep centers pay monthly instead. We store which version of this wording you saw. To withdraw afterwards, email hello@fbaprepfinder.com and we will stop passing your details on. We cannot unsend an introduction a prep center already received.
- The prep centers you pick (requests made before we added Introduce me) - nothing goes to any center when you send your answers. Your name, business, website, email and answers go only to the centers you pick, and only once you pick them, plus your phone if you gave one. Centers you do not pick never receive anything that identifies you. A Featured center pays for a labeled placement slot, not for your details, and we are not paid per introduction. We store which version of this wording you saw and whether your request came from a United States connection. To withdraw afterwards, email hello@fbaprepfinder.com and we will stop passing your details on. We cannot unsend an email a center already received, so we will also tell you which centers have them.
- The prep centers we match you with (requests made on our earlier form) - only if you choose the option on the match form asking them to contact you directly, and only the Featured centers on your own shortlist (a Featured center pays for placement on the site, not for your details; we are not paid per introduction). They receive your name, email, company and company website. The other centers on your shortlist get your requirements with nothing that identifies you. Choose the other option and every center is told your requirements with nothing that identifies you. For visitors in the United States the first option is selected when the form opens and you can switch it in one click; everywhere else neither option is selected and you pick one. We store which of the two you were shown. To withdraw afterwards, email hello@fbaprepfinder.com and we will stop passing your details on, and stop showing them in those centers' dashboards. We cannot unsend an email a center already received, so we will also tell you which centers have them.
We do not sell, rent, or trade your name or contact details. For requests made on our current matching form, prep centers that fit see a summary with nothing that identifies you. When you accept an introduction to a prep center, it may pay us for that introduction, by a fee or as part of a Featured plan; that is the only time money is tied to sharing your details, and it happens only with a prep center you chose. We share only what's necessary to operate these specific services, plus the introductions you asked for and the posts described below.
What we post publicly
We may post a seller's match request on our social media accounts so prep centers can see what sellers are looking for, but only if our matching form told the seller so on the step where the request was sent. A request sent without that notice is never posted. A post carries only these facts from the request:
- units per month and timeframe, as the ranges our form offers
- product categories, special handling, sales channels and Amazon marketplaces
- location, by US state or region only
- the prep services asked for, and whether a setup fee or monthly minimum is OK
- if the seller adds shipment details after sending the request: the answers on labeling, poly bagging, bundling and inspection, inbound mode, storage, and lot or serial tracking
A post never carries the seller's name, email address, phone number, company or store name, website, or current prep center. It never carries a city, street address or ZIP code, an exact count or date, or anything the seller typed in their own words. Our public Slack channel is separate: the Slack entry in the list of third parties above says what it shows.
Our public API and AI assistants
We publish a read-only Model Context Protocol endpoint at /api/mcp/, plus JSON dataset endpoints. These let an AI assistant search our verified directory and cite it. They serve only information that is already public on this site.
- They require no sign-in. There is deliberately no tool that accepts your name, email, or phone number, and we do not store what you or your assistant search for, the tool arguments, or the client details an assistant sends when it connects. If you want a shortlist ranked on fit, you fill in the form on this site, where this policy governs.
- They return no operator contact addresses, only links back to the profile page.
- Results are ordered by fit and verification recency. Paid placement is not applied on this surface, and no click from an assistant is billed to an operator.
- What the MCP endpoint does store, to count its use: one row per connection, tool listing and tool call, holding the method or tool name, the time, which of our deployments answered, a keyed hash of the IP address the request came from and the user agent your client sends (for example openai-mcp/1.0.0). The keyed hash is an HMAC-SHA-256 of the address made with a fixed secret key that we keep apart from the rows, so a row does not hold the address and the address cannot be worked back out of it without that key. If the key is not set, no row is written. Rows written before we switched to the keyed hash in November 2026 hold a plain SHA-256 hash of the address instead. We use these rows only to count connections, calls and distinct callers in total. Nothing deletes them automatically today: they are kept with our other site analytics. Deletion by IP address works: write to hello@fbaprepfinder.com with the IP address you used, and we compute the same hashes from it and delete every matching row.
- Our rate limiter holds the IP address itself for up to one minute, to cap requests per address. As with any web request, our host also receives standard request metadata such as IP address and user agent. We do not use any of it to profile you.
The data is published under CC BY 4.0. You are free to reuse it with attribution to fbaprepfinder.com.
How long we keep things
- Approved claims and live operator accounts: kept indefinitely so operators can continue to manage their listing. You can request removal at any time via the operator dashboard or by emailing us.
- Rejected or duplicate applications, and rejected or revoked claims: contact fields (email, phone, name) are anonymized 24 months after the rejection. The row itself stays so we can answer "did you ever consider X?" honestly, but the personal data is removed.
- Match requests (the "get matched" form): contact fields are anonymized once the match is closed or after 24 months, whichever comes first.
- Operator audit log: kept for the life of the listing as a record of who changed what. Removal of the listing also removes the audit rows.
We anonymize older records periodically as we scale. Write to hello@fbaprepfinder.com any time to request earlier deletion of your own data.
Contact
Questions or requests (deletion, access, correction): hello@fbaprepfinder.com. We respond within 7 days.