Weaviate

The quote above names one provider. The multi-provider finding rests on the vendor’s full disclosure — Snowflake Arctic Embed; 3rd-party vectorizers — not on that line alone.

This page gives the finding and links the document it comes from. The AI Subprocessor Jurisdiction Report ($299) quotes the clause this finding rests on, and the clause for each other vendor in your stack where the report can quote one, in one dated document you can hand to an auditor.

Training and retention posture varies by plan. What we publish above describes the vendor’s default plan; enterprise, team and API agreements frequently differ, often materially, and a contract can override the published default entirely. Check your own plan and contract before relying on this row.

On U.S. CLOUD Act reach specifically: the statute reaches a provider subject to U.S. jurisdiction over data in its possession, custody or control. Corporate control is a strong indicator of that and it is what we can evidence from published documents — but it is not the whole test. A company founded outside the U.S. can still contract through a U.S. entity or run substantial U.S. operations. Treat this as a starting point for your own review, not a legal determination, and take advice on anything that matters.

• 29 Sep 2026 · the record changed. Changed: its country. Why: we corrected our reading.
• 26 Sep 2026 · the vendor’s document was read again; none of the fields this history tracks changed
• 11 Sep 2026 · the record changed. Changed: what the answer depends on. Why: we corrected our reading.
• 29 Jul 2026 · first recorded: “Contracting entity depends on your region or order form — read the clause.”

This is the history of our record of this vendor: when we first recorded it; each time one of these changed: the determination sentence, the contracting entity, its country, the governing law, the US-control finding, what the answer depends on, the note beside the finding, or the cited document; and each time the vendor's document was read again and none of them changed. A change only in capitals, punctuation or spacing is not a line, and neither is a first document title. A line names what changed and does not repeat what those fields said before; the determination above says what they say now. Where the determination sentence itself changed, the line shows the earlier sentence too, marked as before, with why it changed. The automated re-check's latest result is not a line here; it is printed beside the clause above. A change here may be the vendor changing its document or us correcting our reading of it, and a line says which only where the record shows it; otherwise it says the cause is not established. Each line is today's reading of the record as it stood on that date. A reading we later found its citation does not carry was withdrawn, and is not repeated here. This history as data.

Weaviate publishes a list of the other companies it uses as sub-processors. It lists 23 entries, and some name the same company more than once, in more than one of its lists. The list gives no location for any of them, so each is shown by name only, as the vendor lists it.

Under its heading “1. Primary Hosting Providers (Customer-Selected)”: Customers’ business data resides only on the cloud provider (and region) they select from the following options.

Under its heading “2. Supporting Infrastructure (Used for All Deployments)”: The following subprocessors provide supporting infrastructure services that are used across all customer environments, regardless of the selected cloud provider.

Under its heading “Optional Infrastructure Subprocessors”: These subprocessors are used only if customers choose to utilise our Agent services.

Under its heading “Weaviate Engram”: These subprocessors are used to host and operate our core application.

Under its heading “Personal Data Subprocessors”: These subprocessors process personal data related to our customers, such as billing, marketing, and support information. They do not process customer-stored business data.

These are other companies, not Weaviate. The list names no place where any of them handles your data, and Vannus does not fill that in. Where Weaviate itself keeps your data is a separate question, which Vannus answers only from a document in which the vendor says so.

The same document also lists 1 entry for Weaviate’s own corporate group, or for companies that carry its name. It is counted separately from the entries above, which are other companies.

Read from weaviate.io on 2026-09-26, from the page the vendor titles “Weaviate List of Subprocessors | Weaviate”. Every entry above is a verbatim span of that page.

This is the vendor’s own disclosure, reproduced. Vannus has not audited what any of these companies do with your data, and a list can change without notice. Treat it as a starting point for your own review, not a legal determination, and take advice on anything that matters.

Weaviate: “Contracting entity depends on your region or order form — read the clause.”
Vannus, https://vannus.co/tool/weaviate
weaviate.io · read 2026-09-26

How you may reuse this record

Vannus records, from the vendor's own published documents, the legal entity a customer contracts with, the country that entity sits in, and the governing law of its terms — and whether the vendor runs its own model or resells someone else's. Each finding is quoted to its source and dated, or marked not disclosed where the vendor publishes nothing. No paid placement on a record, in the catalog or in search — affiliate status is walled off from the record, enforced by a test in the build. See the methodology →