Subprocessors
Summary
Logethos uses a small, fixed set of vendors. Only the AI providers ever receive content derived from a customer's documents, and only a question plus the handful of retrieved passages that answer it, never a whole document. Retrieval embeddings are computed on Logethos hardware, so there is no embedding vendor at all. This page is the company-wide list; a product may use fewer of these, never more.
This website itself uses none of them beyond hosting. It loads no third-party script, font, or image.
1. Current subprocessors
| Vendor | Purpose | What it receives | Location |
|---|---|---|---|
| Hostinger | Virtual private server hosting. Runs the website, the products, the database, and the object storage | All data held by Logethos, at rest on the server | Mumbai, India |
| Anthropic, PBC | Primary AI provider. Drafts answers, and at intake reads scanned questionnaire pages that have no text layer | At answer time: one question plus the retrieved passages. At intake, for scanned pages only: the page image and its extracted text | United States |
| Paddle (Paddle.com Market Ltd) | Payments, as merchant of record | Billing details, collected by Paddle. No document content. Logethos never sees a card number | United Kingdom and global |
2. Conditional subprocessors
These receive data only when a specific feature is switched on. When it is off, the vendor receives nothing.
| Vendor | Engaged when | Purpose | What it receives |
|---|---|---|---|
| Google LLC, federated sign-in | Google sign-in is configured, and only for a user who chooses it | Optional sign-in | That user's account email and Google profile identifier. No document content |
3. Categories not currently engaged
Two categories appear on most vendor lists and are named here so their absence is explicit rather than an omission:
- Transactional email. No email sending provider is configured. Verification and password-reset email is inert until one is.
- Error tracking. No error tracking service is configured.
Neither receives data today. Either will be named here, with its location and what it receives, before it is switched on.
4. Embeddings do not have a vendor
Turning evidence into retrievable vectors is the step that would normally send the full text of every document to a third party. Logethos runs that step on its own server, on a self-hosted bge-large-en-v1.5 model on CPU. Chunk text is never sent anywhere to produce a retrieval vector. This holds whether or not a customer supplies their own provider key, because customer keys apply to the language model and never to embeddings.
5. Customer-supplied provider keys
A customer who adds their own AI provider key moves that provider out of this list for their organisation. The calls then run on the customer's own account, under the customer's own agreement with that provider, and Logethos is no longer the party sending the data. Embeddings stay local either way.
6. Training and retention
Anthropic, the only AI provider that receives customer content under Logethos's own key, is engaged under a signed agreement that prohibits training on the content it receives and holds retention to what serving the request requires.
No customer content is used to train any model by Logethos, and none is sold to anyone.
7. Changes
Vendors may be added or replaced as the products change. A change is reflected here with a new version and last-updated date. Customers under a data processing agreement may ask for advance notice of a new vendor that would handle their content, and may object on reasonable data-protection grounds.
Each product may also publish this list in a form generated from the running system, so that the published page cannot drift from what the software actually calls. Where a product's generated list and this page disagree, the generated list is the newer fact and this page is corrected.
8. Contact
Questions about a vendor or a data flow: privacy@logethos.com. See also Security and the Privacy Policy.