These providers process data on Logthread's behalf. We will update this page before adding a subprocessor that handles telemetry data.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| plycdn | Storage and querying of telemetry data (logs, traces and metrics). Each live workspace has its own sub-organization. | Telemetry data customers send, and the queries run on it. | India (Mumbai region) |
| Email delivery provider (SMTP) | Transactional email: verification, password reset, invitations, alert emails, usage and deletion notices. | Recipient email addresses, names, workspace names and the message content. | Provider name and location to be confirmed before publication |
| Infrastructure hosting provider | Runs the web app, the ingest pipeline, jobs and the control-plane database. | Account data, and telemetry data in transit through the ingest queue. | Provider name and location to be confirmed before publication |
| Anthropic, PBC | Optional AI features (plain-English search, story explanations, parser drafts). Used only for a workspace whose owner has enabled AI and accepted its consent text. | The question asked and selected log lines, after Logthread masks cards, Aadhaar, PAN, emails, phone numbers and secrets. | United States |
Other third parties
- Google Fonts serves the typefaces on the public pages, so a visitor's browser contacts Google. The signed-in app does not need it for telemetry data.
- Alert destinations (for example a webhook or chat service) are chosen and controlled by the customer. Logthread sends alert content there only when the customer has set up that channel.