LEGAL
last updated TK · effective TK
COPY PENDING COUNSEL
This is the container. Every section below is a description of what the clause covers, not the clause itself — the binding language comes from a human or counsel and lands marked TK until it does. Namespaced under /legal/ rather than bare /terms because “terms” already names engineering vocabulary elsewhere in the product.
Who is agreeing to what, and when — connecting a repository or using any Preston surface is the moment that matters.
TK — binding mechanism, effective-date handling, and the changes-notification clause.
What Preston does — reviews pull requests, and on eligible plans grounds coding agents through a metered credit model — and what availability a given plan promises.
TK — SLA language, the beta disclaimer, and a transitional note covering that nothing is gated yet.
Your code and the claims Preston derives from it stay inside your team's isolation boundary. What actually leaves the repository is the subject of the security page, once its audit lands.
TK — align this section verbatim with the in-flight security audit before publishing any data-handling claim.
A seat is a person whose work Preston reviewed during the billing period. Charges bind to the team as the billable unit, with exactly one owner account responsible for payment.
TK — refund policy, proration on seat changes, and tax handling.
How either side ends the relationship, and what happens to your data and your team's understanding afterward.
TK — notice period, data retention on cancellation, and what survives deletion (invoices usually must).