Vannus / Catalog / Qodo

Qodo

Vannus records that this vendor routes across several model providers — not captured by one. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.

Determination
Contracting entity depends on your region or order form — read the clause.
qodo.ai · read 2026-07-29
read from terms of service
Contracting entity
Codium Ltd. (Israel) and CodiumAI, Inc. (United States)
Jurisdiction
Israel and United States
Governing law
State of Israel (courts of Tel Aviv) for customers outside North America; State of New York for North American customers
US corporate control
More than one contracting entity is on record, and which one a buyer signs with depends on facts about the buyer, such as where it is. The record does not establish US corporate control on every track, so it makes no single finding on US legal reach. the rule
Depends on
The contracting entity depends on your region or order form: read the clause for your position. The agreement is under a governing law that depends on where the customer is based.

AI code review and governance platform (formerly CodiumAI) covering both the IDE and the git host.

coding, AI, code-analysis
What the vendor's own documentation says
The default models used by Qodo (as of December 2025) is GPT-5.2. In some cases we use other models from the major LLM providers (Anthropic and Google)
docs.qodo.ai ↗ Vendor-sourcedQuote re-checked 19 Oct 2026
Who controls it
US corporate controlRegion-dependent — a US entity contracts in some regions; elsewhere a non-US entity does, and whether a US company controls it is not established · clause last confirmed 5 Oct 2026; the document could not be read when re-checked 19 Oct 2026
Contracting entityCodium Ltd. (Israel) and CodiumAI, Inc. (United States)
Governing lawState of Israel (courts of Tel Aviv) for customers outside North America; State of New York for North American customers

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.

Record history

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.

Who else handles your data

Qodo publishes a list of the other companies it uses as sub-processors. It lists 4 entries. Each is shown below with the location the vendor lists it under, in the vendor’s own words.

Google Cloud Platform · U.S. or EU at Customer’s electionAmazon Web Services, Inc. and Amazon Web Services EMEA SARL · U.S., EU or Australia at Customer’s electionSlack · United StatesGoogle Workspace · U.S.

Taken together those entries name at least Australia, EU, U.S., United States. That is what our place list could match in the vendor’s own words above, so treat it as a floor rather than the whole of it — the entries themselves are the record.

These are other companies, not Qodo. Where a sub-processor is listed as operating is a fact about that company. It is not a statement about where Qodo keeps your data, which Vannus publishes separately and only from a document in which the vendor says so.

Read from qodo.ai on 2026-09-23, from the page the vendor titles “Data Processing Addendum | Qodo”. 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.

Cite this record
Qodo: “Contracting entity depends on your region or order form — read the clause.”
Vannus, https://vannus.co/tool/qodo
qodo.ai · read 2026-07-29

How you may reuse this record

How this entry is set

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 →

Related tools we record
Visit Qodo ↗ Check your whole stack →
Vannus (PRAXIS AI LLC) · entry as of the latest catalog build · all 376 tools · MCP for assistants
Work here and think we got something wrong? Corrections and right of reply → — free, no account, and we publish your response next to our entry.