Decision: Sub-Processor Register & Classification
Decision: Sub-Processor Register & Classification
Status: Decided and shipped
Channel: #x-all
Participants: Arun Gandlur, Madhur Joshi, DK
PR: boo-marketing-site #12
Context
Boo Lab needed a public sub-processor register at /legal/subprocessors for the Slack Marketplace submission. No concrete vendor list previously existed.
Decision
18 Sub-Processors Listed
See the Security & Privacy page for the full categorized list.
Classification Rule
Customer-connected integrations are NOT sub-processors.
When a customer connects Slack, GitHub, Linear, Teams, or Google Chat to Boo, those are the customer's own tools accessed on their behalf with their own credentials. This follows industry standard practice (confirmed by checking Linear, Figma, Asana, Datadog).
Boo Lab's own internal tools ARE sub-processors when they process customer data. For example, Boo Lab's internal Slack workspace and Linear instance handle support threads that discuss customer issues, making them sub-processors.
Future-Proofing
Services coming soon but not yet in production were included (e.g., BrowserUse, Tavily) to avoid needing immediate updates.