Neo4j
Vannus has not established which model this vendor runs, and does not infer one. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.
- Contracting entity
- Two contracting entities, split by where the CUSTOMER is incorporated: Neo4j Sweden AB for customers incorporated in Europe, the Middle East, Africa, China and Singapore; Neo4j, Inc. for customers incorporated in all other countries, and for transactions through a cloud-provider (CSP) marketplace. An Order Form or SOW may name a different entity, which takes precedence.
- Jurisdiction
- Sweden (Neo4j Sweden AB) for customers incorporated in Europe, the Middle East, Africa, China and Singapore; United States (Neo4j, Inc.) for customers incorporated elsewhere and for CSP-marketplace purchases
- Governing law
- Swedish law with exclusive jurisdiction in the courts of Malmö, Sweden (Neo4j Sweden AB); California law with exclusive jurisdiction in the state and U.S. federal courts in Santa Clara, California (Neo4j, Inc.)
- 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 order form, how you buy or where your company is incorporated: read the clause for your position.
Native graph database — property graph model with Cypher query language for multi-hop reasoning, entity-relationship traversal, and explainable dependency tracing across enterprise AI tool ecosystems
Not established. The finding this entry held rested on a page from a site whose terms we read as forbidding a scripted read, so it is not published here.
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. It now reads: “Contracting entity depends on your order form, how you buy or where your company is incorporated — read the clause.” Before: “Contracting entity depends on your region or order form — read the clause.” Changed: what the answer depends on. Why: we corrected our reading.
- 16 Sep 2026 · the vendor’s document was read again; none of the fields this history tracks changed
- 7 Sep 2026 · the record changed. It now reads: “Contracting entity depends on your region or order form — read the clause.” Before: “Contracts with Neo4j, Inc. (United States) — within reach of US legal process.” Changed: the contracting entity, its country, the governing law, the US-control finding, what the answer depends on, the note beside the finding and the cited document. Why: we corrected our reading.
- 29 Jul 2026 · first recorded: “Contracts with Neo4j, Inc. (United States) — within reach of US legal process.”
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.
The vendor's published or catalog-recorded posture — the concrete facts this entry is built from. A full audit verifies each against the vendor's current documentation.
Neo4j: “Contracting entity depends on your order form, how you buy or where your company is incorporated — read the clause.” Vannus, https://vannus.co/tool/neo4j neo4j.com · read 2026-09-16
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 →
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.