Sub-Processors

BuyerBot uses the following third-party sub-processors to deliver and operate the Service. Each sub-processor has been selected for its security practices and processes only the minimum data necessary to perform its function.

This page is maintained as a living document. If we add or change a sub-processor that materially affects how customer data is processed, we will update this page and note the change date below.

Current sub-processors

Sub-processor	Purpose	Data processed	Location
Cloudflare, Inc.	Hosting, infrastructure, data storage (Workers, D1, KV, R2, Queues, Durable Objects)	All customer data: workspace configuration, user records, purchase requests, approval history, bot tokens, cached search results, cached product images	Global (edge network)
Groq, Inc.	LLM inference for conversational agent	User messages sent to BuyerBot (DMs, @mentions, /buy commands) and BuyerBot's responses. Used for real-time inference only; not stored or used for training.	United States
RapidAPI (by Zoominfo)	Real-time Amazon product search API	Product search queries only. No personal data, user identifiers, or workspace information is transmitted.	United States
Slack (Salesforce, Inc.)	Messaging platform integration	Messages sent and received through the Slack API, user IDs, channel IDs, workspace IDs	United States
Amazon.com, Inc.	Cart link generation (Amazon Associates Program)	Product ASINs embedded in cart URLs. No personal data is sent to Amazon by BuyerBot.	United States

Guidelines for sub-processor management

Selection criteria

Before engaging a new sub-processor, we evaluate:

• Whether the sub-processor has appropriate security measures and data protection practices
• Whether the sub-processor's terms prohibit using customer data for their own purposes (e.g., model training)
• Whether data processing can be limited to the minimum necessary for the function
• The sub-processor's data residency and jurisdiction

Data minimization

Each sub-processor receives only the data it needs to perform its specific function. For example, the product search API receives only search query text — no user identifiers, workspace information, or conversation history.

Contractual safeguards

We use each sub-processor under their standard terms of service or data processing agreements, which include provisions for data security, confidentiality, and restrictions on data use.

Notification of changes

If we add a new sub-processor or materially change how an existing sub-processor processes customer data, we will:

• Update this page with the change and date
• Note the change in our Privacy Policy revision history

Change log

Date	Change
July 11, 2026	Initial sub-processor list published

Contact

Questions about our sub-processors? Contact us at [email protected].