Legal
Sub-processors
Last updated {{EFFECTIVE}}
The third parties that process data for the hosted Shield 360 service. A self-hosted deployment uses none of them: its data stays in the customer's own environment. Sign-in, organization provisioning and billing run on Base316, ThinkFleet's own identity and billing platform, on the same infrastructure listed below; it is not a third party.
Hosted service
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Hosting, databases, storage and backups | All Customer Data on the hosted service | United States (us-east-2) |
| Stripe, Inc. | Payment processing | Billing contact and payment details | United States |
This website
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Google LLC | Analytics (with consent where required) and web fonts | IP address, pages viewed, device and browser details | United States |
| Cal.com, Inc. | Booking calls | Name, email and the notes you enter | United States |
Services a customer chooses to connect
These are not our sub-processors. A customer connects them with its own credentials and under its own agreement with the provider, and data flows to them only on the customer's instruction:
- Model providers used for evaluations and Openground, such as OpenAI, Anthropic, Google, Mistral or Cohere. Running an evaluation sends the trace being scored to the provider selected.
- Memory stores such as Claude, Mem0 or Zep.
- GitHub, for AI code findings.
- AI providers' usage and billing APIs, for cost reconciliation.
- The customer's identity provider, for single sign-on.
- Alert destinations the customer configures: Slack, Microsoft Teams, PagerDuty, a webhook, or email recipients.
- SIEM and security tools the customer configures, such as Splunk, Microsoft Sentinel, Datadog, Elastic, the customer's S3 bucket or a syslog server.
- Agent test targets: the model provider or endpoint a customer tests.
Changes
We update this page at least 30 days before a new sub-processor begins processing Customer Data. To be told by email, write to privacy@thinkfleet.ai with the subject "Sub-processor notifications". Our Terms of Service explain how to object.