This entry runs no foundation model. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing. The control finding below is the exception: it is quoted to the party claiming control, named and dated where it appears, because this record cannot reach the vendor's own terms. The model-provenance finding is a second exception: no vendor document backs it, so it is established from what the product is, and says so.
Instant cloud dev environments for rapid prototyping and collaboration
No foundation model. CodeSandbox does not run one, so there is no model provenance to record. Cloud development environments: isolated virtual machines used to run code, including as a runtime for other people's AI agents. The product itself performs no inference. Established from what the product is; codesandbox.io returns 403 to both clients, so no page of the vendor's own documentation has been read here. If that is out of date, tell us at right of reply.
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.
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. A contracting entity we later found its citation never carried is withdrawn from each line that named it, and the line says so. This history as data.
CodeSandbox: “Contracting entity not established, under terms this record cannot reach; the vendor is under US corporate control, so US law may have legal reach over it and the data it controls.” (controlled by Together Computer, Inc. (United States), per a release issued by Together AI, the party claiming control [2026-09-12]) Vannus, https://vannus.co/tool/codesandbox together.ai · read 2026-07-29 and 2026-09-12
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 →