UPDATED SEPTEMBER 24, 2026
Subprocessor List#
This page lists the third-party subprocessors TensorCase uses to process Customer Data.
AI SUBPROCESSORS#
These subprocessors process Customer Data to generate outputs within the Services. None of them uses Customer Data to train its models.
| Subprocessor Name | Purpose | Data Types | Processing Location |
|---|---|---|---|
| Amazon Web Services (Amazon Bedrock) | AI service provider | Customer Data processed by AI models to generate outputs | USA; United Kingdom (UK and EU customers) |
| Anthropic | AI service provider (failover when Amazon Bedrock is unavailable) | Customer Data processed by AI models to generate outputs | USA (all customers) |
| Google (Gemini API) | AI service provider | Customer Data processed for embeddings and search | USA |
| LlamaIndex (LlamaParse) | Document parsing service | Customer Data in spreadsheets processed for parsing and extraction | USA |
ALL OTHER SUBPROCESSORS#
| Subprocessor Name | Purpose | Data Types | Data Processing Location |
|---|---|---|---|
| Amazon Web Services | Cloud infrastructure | Customer Data and account data hosted on cloud infrastructure | USA, Canada, United Kingdom, or Australia |
| Nango | Integration connector | Authentication tokens for connected services, and files transmitted from SharePoint and Dropbox at Customer's direction | USA |
| PropelAuth | Authentication | Account credentials and user identity data | USA |
| PostHog | Product analytics | Product usage and operational telemetry; no case, document or matter content | USA |
| Google (Google Workspace) | Business email and productivity | Business contact information and support correspondence | USA |
UPDATES#
We give at least 30 days' notice before a new subprocessor processes Customer Personal Data, as set out in our Data Processing Addendum.
Questions: privacy@tensorcase.com
Need help? Contact us at support@tensorcase.com