What we collect, and why.

What we collect

• We collect only what the registry needs to work. We don't sell personal information, and we don't use advertising trackers.
• Your account. If you sign in to the app: your email address, when you sign in, and your authenticator setup, stored encrypted. We use them to sign you in and to send account emails. Each time you sign in or claim a brand we also record the IP address of your connection, the country it's in and the name of the organization that owns the network, to prevent fraud and investigate a claim that turns out to be false. Only registry admins see these, and they're deleted after 12 months.
• Claiming a brand. The domain and brand name you claim, your confirmation that you're authorized to represent the brand, and, when your email isn't at the brand's domain, what you tell us about your connection to it. Registry admins read this before approving a brand. It stays with the claim for as long as the brand is registered.
• What you add. Brand details, retailer names, seller IDs, store domains, territories, product lines, listing requests, domain verification records and a log of every change to a brand's list. This is how the registry works.
• People you invite. The email addresses of colleagues, retailers or brand contacts you invite, or IT contacts you send verification steps to. We use them to send that one invitation or instruction.
• Verify API and MCP queries. The brand, seller, territory and product asked about, the answer and the time, the product identifiers the request sent, and for MCP the tool or method called, plus up to five things about the caller: a keyed hash of its IP address (never the address itself); the name of the organization that owns the network the request came from, such as a cloud provider or a company; the country the request came from, as our hosting provider reports it; the User-Agent text the client sends, which many AI agents use to name themselves; and, for a call made with an API key, the key's ID. Requests we refuse (no or invalid key, too large, malformed or rate limited) are logged the same way, with the reason. We use the hash to rate-limit and to stop anyone downloading a private list one question at a time. We use the network owner and User-Agent to see which platforms and agents use the registry and, where a client names its developer or company, to reach out to them about the service. Only registry admins see any of this. Brands see how many times they're checked and which sellers were asked about, never who asked. On a home or office connection the network owner is the internet provider, which says nothing about who you are, and we don't try to identify individual people.
• Amazon seller details. For seller IDs added to the registry, what Amazon publicly lists: storefront and business name, address, contact details and ratings, fetched through Keepa. In the US we also standardize the address and look up its location to warn brands about PO boxes and mailbox stores.
• Seller detection. If a registry admin runs seller detection for a brand, we search Amazon, eBay, Walmart and Google Shopping for sellers carrying that brand's products. For each seller we keep what the platform shows publicly: seller ID or store domain, storefront or business name, address where listed, ratings and the titles of matching listings. The brand sees these as leads and decides whether to authorize, declare or ignore each one. Nothing is published, and a seller isn't marked unauthorized unless the brand declares it. A seller can ask us to delete or correct its entry.
• Retailer accounts. If a brand invites you and you open a retailer account: your email, the channels you say you sell on and the proof we check for each, such as a reply from an address at your store's domain.
• Declarations and disputes. If a brand declares a seller unauthorized, we keep the declaration and who at the brand made it. If you dispute one, we keep the contact email and evidence you give, share them with the brand, and email you how the dispute closed.
• Booking a call. If you book a call with us: your name, email, company domain, time zone and the email addresses of any guests you add. The call goes on our Google Calendar with a Google Meet link, and the invitation and any update reach you by email.
• Email delivery. For invitations we send on a brand's behalf, whether the email bounced or was reported as spam, so the brand can see that it didn't arrive.
• API keys and agent developer accounts. If you sign up for an API key: your work email, your name and organization, the agent you're building and what it is for, when you accepted the terms of use, and, for each key you make, its name and when it was made and last used. We keep only a hash of a key's secret, never the secret. We use this to sign you in, to rate-limit each key on its own, to tell which agents use the registry and to reach you about the service. Only registry admins see it: a brand sees how many times it's checked, never who asked.
• Asking to be contacted. If you say you don't have a work email, we keep your name, email, organization and what you told us about your agent, so we can reply to you, and delete the request 30 days after you make it.
• Waitlist and feedback. The email and brands you give us on the retailer waitlist, the business name, store domain, marketplace seller ID or store names and email you give us if you register your interest as a retailer, and any feedback you send, with your email if you include one.

Who sees what

• A brand's list is public or private, as the brand chooses. A private list is never published. Agents can only ask about one seller at a time.
• Brands see how many verify queries are made about their own domain, and which seller identifiers were asked about. They never see who asked.
• When a retailer asks a brand for a listing, the brand sees the request and what we checked about the retailer's channels. Requests are never published.
• A brand's declarations are never published as a list. An agent learns of one only by asking about that seller. Seller addresses, contact details, ratings and prices fetched from marketplaces are shown to the brand only; a published list carries the retailer's name and channel identifiers.

Who we share it with

Only the services that run the registry: Cloudflare (hosting, database, email routing and the bot checks on this site and the booking form), Resend (sending email), Google (Calendar and Meet for calls you book with us), Keepa (looking up Amazon seller IDs; only the seller ID is sent), SearchAPI (eBay, Walmart and Google Shopping searches for seller detection; only the brand and product names are sent), Anthropic (its Claude model reads the public seller details from detection to flag stores that look like the brand's own), Click2Mail (US address standardization; only the address is sent) and the US Census Bureau geocoder (only the address is sent). We share information with anyone else only if the law requires it.

How long we keep it

Query logs, including the network owner, country, User-Agent and key ID, are kept for 90 days. After that we keep only daily totals, with no caller information, for up to 25 months. Account information is kept while your account is open; sign-in links and sessions are deleted once they expire, and the connection details of a sign-in or claim after 12 months. Booking records are kept so we can reschedule, cancel or follow up on the call. Waitlist entries are kept until retailer accounts open to everyone, or until you ask us to delete yours.

Cookies

The app sets a cookie to keep you signed in, for up to 12 hours or until you sign out. Signing in through the Sign in dialog on this site, or to manage your API keys, sets that same app cookie. If you start a brand claim from this site, the app also sets a one-day cookie that remembers the domain. Cloudflare may set a cookie when it checks that a visitor is not a bot. We use no analytics or advertising cookies.

Your choices

Email hello@authorizedretailers.ai to see, correct or delete your information, or to close your account. Depending on where you live, you may have further rights, including the right to complain to a data protection regulator.

Changes

If this notice changes, we'll update it here with a new effective date, and email account holders about significant changes.

Who we are

Authorized Retailers LLC
c/o Northwest Registered Agent LLC
7901 4th St N Ste 300
St. Petersburg, FL 33702, USA