Recovea — Baseline & Assessment Terms

What this is. These Baseline & Assessment Terms (these "Assessment Terms") state what the two free features of the Recovea Service are, how they run on your own traffic without any of that traffic passing through Recovea, what their figures are and are not, and what happens to the data they collect. The two features are the Baseline, a free seven-calendar-day view of what your own AI calls cost, and the Assessment, the fully computed report that appears in your organization when a Baseline closes. Neither is sold. Neither carries a fee, a card, an order, a guarantee, or a credit. They are features of the Recovea Service, furnished at no charge under the Terms of Service, the Acceptable Use Policy, the Privacy Policy and the DPA, and these Assessment Terms say the things about them that are specific to them. (Restated in full on 2026-09-23 under founder ruling 81. Until that day this document was the ordering document for a fixed-fee Assessment; that engagement is retired, and the change log records what left.)

What comes after them is a Subscription, not an engagement. The Assessment ends in one offer: a Recovea Subscription sized to what the Assessment found, which you may start or not. A Subscription is governed by the Terms of Service and the plan terms they incorporate, not by these Assessment Terms, with the one addition in §5.4: a plan started from the Assessment page begins without a trial period and is charged at checkout, because the Baseline and the Assessment were the trial.

The honesty bar is load-bearing here, and it does not move with the price, which is zero. The Baseline and the Assessment state cost, never savings. They report figures your own software reported, model cost from a published price list, and carry figures you declared, each labeled as such. Nothing in either is a savings figure, an outcome guarantee, an audit, an attestation, or advice, and the word "verified" does not appear in either. A free report held to a lower standard than a paid one would be the cheapest way this company could lose the thing it sells, and there is no longer a paid one to compare it to: the standard is the standard.

Where this fits. These Assessment Terms are incorporated into, and are part of, the Recovea Terms of Service (the "Terms") — see terms-of-service.md — and, together with the Terms and the other documents they incorporate, form part of the "Agreement." The Terms, the Data Processing Agreement ("DPA") and the BYO-Key & Provider Terms control over these Assessment Terms as stated in the Terms' order of precedence. The Professional Services & SOW Terms no longer apply to anything described here: the Assessment is not a professional-services engagement, no Statement of Work exists for it, and nothing in it is written or signed by a person at Recovea.

1. The Baseline, and the Assessment

1.1 The Baseline (free). The Baseline is a free seven-calendar-day view of what your own AI calls cost, produced by the passive tap described in §4. You install Recovea, the Baseline fills as your application reports call envelopes, and it closes at the end of seven calendar days counted from the first whole day on which your application reported priced calls, or sixty days after you created it, whichever comes first. The Baseline is furnished at no charge, with no card and no order, as a feature of the Service under the Terms; it is not a professional-services engagement and carries no fee, no guarantee, no credit, and no review window. Recovea may lengthen a Baseline at no charge where too little ran during it, may set and adjust reasonable volume ceilings for abuse control (§4.9), and may end or decline a Baseline under the Acceptable Use Policy.

1.2 The Assessment (free, and computed). When a Baseline closes, the Assessment appears in the same organization at no charge: every section computed from the call envelopes your application reported during the Baseline, with nothing to buy, nothing to wait for, and nothing written by a person. There is one Assessment per organization, it is not bought, and it is not sold. It carries no fee, no order, no guarantee, no credit, no readout, no written findings authored by Recovea, and no signed statement; every sentence on it is computed by the Service from the figures on it, by a method printed beside the figure.

1.3 Sections. The Assessment is organized into sections, and every section is open. Two lead sections exist today and keep their names: the AI Cost Defensibility section, for a business that bills a client, answers to an investor, examiner, or auditor, or makes a cost claim about its own work; and the Agent Exposure section, for a business that runs software agents unattended, overnight, or at volume. Your answer to the one install question (§5.1) decides which section leads; both are always open. Every section Recovea later adds is included at no charge, computed on the traffic your tap has already reported where the data to do so exists. Recovea does not commit to adding any particular section, to any schedule, and may revise or retire a section. A section Recovea cannot compute from what your tap reported says so on its own page rather than showing an empty chart.

1.4 What the AI Cost Defensibility section answers. If someone outside your company asked what a unit of work cost you in AI, would your number hold up? From the calls your application reported and the tag you declared: your AI cost per declared unit of work with its spread; one declared unit traced call by call; how the reported calls split across the units you tagged; a per-client roll-up by the tags you declared; where the number would break under scrutiny; the allocation rule stated so an outside reader can accept or reject it; what the section does and does not say.

1.5 What the Agent Exposure section answers. If an agent looped all night, what is the most it could cost you, and what stops it today? From the calls your application reported: the workloads your tags name; the worst hour the traffic showed, call by call; what the traffic showed by tag (bursts, stop reasons, statuses, latency, peak calls per minute); a modeled worst hour at the same call rate, with its arithmetic printed; a ceiling on what ran unattended; where each workload can be bounded; what the section does and does not say.

1.6 What every item is. Every figure in the Baseline and in the Assessment is one of three things, and is labeled as the one it is (§7): a figure reported by your own software; a figure modeled by Recovea from reported figures and a published price list; or a figure declared by you. Neither ever contains a figure of a fourth kind. In particular, because Recovea never reads the content of your calls and never sits in their path (§4), neither the Baseline nor the Assessment reports on the content of any prompt or response, on which API key a call used, on the structure of an agent run or its sub-agents, or on anything your software did not report to the tap.

1.7 What the Assessment contains. (a) The in-product pages for every section, with charts computed from the reported calls; (b) the computed sentences on those pages, each generated by the Service from the figures beside it, never by a person; (c) the moves: where the figures show a cost or an exposure that a control would bound, the Assessment states that control and the cost or the exposure it puts a ceiling under, never a saving — never "worth $X", never a percentage, and never a comparison to a baseline of Recovea's choosing; and (d) the export of every reported event with the hash chain described in §11.1. Recovea provides no written findings, no readout, no signed statement, no video, and no recorded walk-through, and the words "verified" and "attested" appear nowhere in it.

1.8 No entitlement changes. The Baseline and the Assessment grant, extend, and change no Subscription entitlement. Your organization remains on its then-current plan. Neither is a subscription and neither is ever billed.

2. Formation; no order

2.1 No checkout, no order. Nothing in these Assessment Terms is ordered or bought. You accept them by using the Baseline and the Assessment, as features of the Service under the Terms, and by creating a Baseline in your organization. No signature is required, no Statement of Work exists, and no payment instrument is taken for either feature.

2.2 One Baseline and one Assessment per organization. An organization may hold one Baseline at a time and one Assessment. Where an organization already holds one, the product says so rather than creating another; an erased organization (§11.4) may start again.

2.3 Authority. The person creating a Baseline represents that they have authority to install the tap in the application whose calls it reports and to bind the Customer whose organization it is, as stated in the Terms.

2.4 Right to decline. Recovea may decline or end a Baseline or an Assessment it cannot serve, or that breaches §4.7 or the Acceptable Use Policy, at any time, and says so on the page.

3. Price; the plan that follows

3.1 No fee. The Baseline and the Assessment carry no fee of any kind and never ask for a card. There is no price ladder, no spend-based tier, no per-section price, no deposit, no quote, no invoice, and no credit. Recovea does not ask for, and does not price on, your AI spend.

3.2 The plan is priced on its own terms, never on what was found. The Subscription the Assessment offers (§5.4) is one of Recovea's published plans at its published price, chosen by the routed-spend band the plan carries, and the offer names the plan the Assessment's own figures fall in. The price of a plan is never contingent on results, findings, outcomes, or the magnitude of anything the Assessment or the Baseline reports. A price that could move with the answer could want a particular answer; these prices cannot. Where the Assessment's figures fall under the ceiling the Free plan already caps, the offer says so and names Free.

3.3 Taxes; billing. Nothing here is taxed or billed. A Subscription's fees, taxes, billing errors, refunds and cancellation are governed by the Terms and the Refund & Cancellation Policy.

4. How both run: the passive tap

This Section describes the method used by the Baseline and by the Assessment alike, and by a Subscription's continued reporting after them.

4.1 Nothing routes through Recovea. Both observe your traffic without carrying it. You install Recovea beside the AI-provider client your application already uses; your application's calls keep going directly to your provider on your own provider account, exactly as before, and the package reports the envelope of each call to Recovea on the side, after the call returns. Recovea is not in the path of any call, does not forward, retry, delay, or fail any call, and does not receive or hold any provider API key for a Baseline or an Assessment. (For the avoidance of doubt, the BYO-Key & Provider Terms govern provider keys only where you route traffic through the Recovea gateway, which a Subscription's controls require and which neither a Baseline nor an Assessment does.)

4.2 What the tap reports. The line — the "passive tap" — reports, for each call, only the following: which provider and model served it; the provider's request or response identifier; the token counts from the provider's own usage figures; the stop reason; the number of tool calls; the HTTP status; a retry count; the latency; rate-limit headers where the provider client exposes them; the time; and the tag you configured for that client. The complete list of fields, with each field's type and permitted values, is published at recovea.ai/docs/passive-tap (the "Tap Schema"). If a field is not in the Tap Schema, it is not in what the tap sends.

4.3 What the tap never reports. The tap never reads, holds, transmits, or logs a prompt, a message, a system instruction, a completion, a response body, a tool argument, a file, an embedding, or any other content of a call. This is enforced twice: the tap's code can only serialize the Tap Schema's fields, and Recovea's server refuses any submission that carries anything outside the Tap Schema — a field it does not know, a wrong type, an out-of-range value, an impermissible character — refusing the whole submission rather than trimming it, and does not record the refused submission anywhere. Submissions above the published size limit are refused the same way.

4.4 You may read the payload before it leaves your machine. The published tap library carries a setting that prints each batch locally, as the exact bytes the endpoint would receive, and transmits nothing while it is on. Recovea states this as a term and not merely as a feature, because the promise in §4.3 is one you are entitled to check for yourself rather than take on trust. While that setting is on nothing reaches your Baseline, and the library says so.

4.5 The tag is yours, and it is the only free text. The tag is the one field you type. It is a short identifier of your own choosing for the unit of work a call belongs to (a matter number, a claim identifier, a workload name, an agent name), limited to the characters the Tap Schema permits. It is your declared data: Recovea does not infer, derive, or check it, and reports it as declared. You are responsible for not placing personal data, secrets, or content in a tag; the DPA governs any personal data a tag nonetheless carries.

4.6 The tap key. Your organization is issued one credential, a tap key with the prefix rcv_tap_, which authenticates the tap's submissions and binds them to your organization. It is minted when your Baseline is created, and the same key goes on working through the Assessment and, if you start a plan, through the Subscription — which is the whole reason there is nothing to re-integrate at any step. Recovea stores the key as a one-way keyed hash and keeps only its first twelve characters readable for display. The key is shown to you once, and Recovea keeps no clear copy of a key it has shown. The response that creates your Baseline is that one showing, and no clear copy is kept at all; if you navigate away before copying it, you rotate it in the product, which mints a new key, shows it once, and ends the old one. A tap key authenticates the tap and nothing else: it cannot read your organization, cannot route traffic, and is not an API key for your organization.

4.7 Your own calls only. You may point the tap only at calls that your own application makes on your own provider accounts for your own organization. Reporting calls made by or on behalf of another party, or on another party's provider account, is prohibited and is a breach of the Acceptable Use Policy; Recovea may end or decline a Baseline, an Assessment or a Subscription's reporting for it.

4.8 How long the tap reports, and what it answers when it stops. This is stated plainly because your own logs will show it:

• During a Baseline, the tap reports from the first accepted submission until the Baseline closes (§5.2). When the Baseline closes, the endpoint answers its submissions with HTTP 410 and the code baseline_closed, storing nothing. The published library does not go quiet for good on that answer: it stops sending, says so once, and re-checks on a slow cadence that rides your own traffic, so that if you start a plan, reporting starts again by itself, with no restart of your application and nothing to re-integrate, within about a minute of the next call your application makes. An application that is idle when you start resumes at its next call. You are told to remove nothing at that moment, because removing it is not what we want you to do and saying otherwise would be an instruction against your own interest. (Restated 2026-09-23 under ruling 81: the answer used to say "Buy the Assessment to keep reporting"; there is nothing to buy, and the sentence now names the plan.)
• On a Subscription, the tap reports for as long as your organization holds an active paid plan (a trial period counts). There is no closing instant on that path; the sections recompute, and the Assessment re-baselines each calendar month (§5.5). When a plan ends — at the end of a cancelled period, or on a refund of it under the Refund & Cancellation Policy — the endpoint answers exactly as it does at a close (HTTP 410, baseline_closed, storing nothing) and the library behaves exactly as it does then, so a plan started again resumes reporting on your next call with nothing re-integrated. (Director ruling 82.)
• On an erasure, there is no courteous answer and there is deliberately not one. The erasure deletes the stored tap key along with everything else, so the key you hold is no longer a key Recovea knows and the endpoint refuses it exactly as it refuses a key that was never issued (HTTP 401, byte-identical in every case). The library stops after three such refusals and says the key was not accepted. Recovea will not keep a working credential belonging to a customer who asked it to keep nothing, which is what a polite refusal would require.

4.9 The tap's software, and the bounds on a free tap. The tap ships as an open-source library in Recovea's published packages, under the SDK, Open-Source & Open-Spec License. Its published field set, the Tap Schema, is a published specification you may read and check before you install anything. Recovea makes no availability commitment for the tap's receiving endpoint; a submission the endpoint refuses or does not receive is not a breach of these Assessment Terms. Recovea may refuse submissions that exceed a published rate, and the two kinds of refusal are not the same. A refusal aimed at your tap key carries a wait-and-retry answer that the published library honours, so it clears itself. A refusal aimed at a network address is a bare refusal that the library cannot tell from any other failure, and it does not explain itself to you. A free Baseline also carries a daily volume above which Recovea is notified and nothing changes for you, and a total volume above which the endpoint stops storing and the page says so; both are abuse bounds far above any honest workload, are runtime settings, and are stated on the page when reached.

5. The Baseline, the close, the Assessment, the plan

5.1 Install and the one question. You install the tap, set the tag your calls will carry, and answer one question, whether clients or your own customers pay for what your AI does, which decides which section leads. Where you choose to, you may also declare your last provider invoice total, which is optional and is shown as a declared figure against the reported one. Nothing you have already told Recovea is asked for again anywhere later.

5.2 The Baseline's seven days. The Baseline's window opens when Recovea's server accepts the first submission from your tap, not before; until then your page says it is waiting. Its seven calendar days are counted in UTC from the first whole day on which your application reported at least one call Recovea could price, and the page shows the days as they pass; until that day arrives the page says so, and no close happens. If no such day has arrived within sixty days of the Baseline's creation, the Baseline closes then, with everything reported up to that point, and the page says so. It is never counted in calls. Recovea may lengthen a Baseline at no charge where too little ran during it, and will say so on the page; Recovea never shortens one.

5.3 The close, and the Assessment. When the window closes, the tap stops reporting (§4.8) and the Assessment appears in the same organization at no charge, computed from everything the Baseline reported: every section, the moves, the export and the chain head. There is nothing to buy, nothing to wait for, no delivery mark, and nothing a person at Recovea writes. The page states the day the Baseline closed and, where your application has kept calling since, says so; nothing after that day is on the page until a plan is started.

5.4 The plan. The Assessment ends in one offer: the Recovea plan whose routed-spend band the Assessment's own figures fall in, at that plan's published monthly and annual prices, and Free where the figures fall under the ceiling the Free plan already caps. A plan started from the Assessment page begins at once, is charged at checkout, and carries no trial period, because the free Baseline and the free Assessment on your own traffic were the trial; the fourteen-day trial the Terms describe applies to a plan started without a Baseline. On a plan start the tap resumes reporting (§4.8), the sections recompute on the traffic reported afterwards, and the controls the plan carries may be armed, which is the one thing that routes traffic through Recovea and is governed by the Terms and the BYO-Key & Provider Terms. Where the offer names Free, nothing is charged and nothing is started: a Free organization caps its bill by routing through the Recovea gateway on the Free plan's own terms, and the tap does not resume on Free. The Subscription itself — its fees, renewal, cancellation and refund — is governed by the Terms and the Refund & Cancellation Policy, and nothing in these Assessment Terms enlarges or narrows them. Starting a plan is your choice; the Assessment is yours whether or not you do.

5.5 The monthly re-baseline. For as long as your organization holds an active plan, the Assessment's sections recompute each calendar month against the month just ended, so the figures stay current rather than fixed at the date of the close. Without a plan the Assessment stays readable as it was at the close and does not recompute, because nothing is reported to recompute it from.

5.6 Your responsibilities. You will: (a) add the tap line to the application whose calls you want reported, with the tag set, and keep it reporting until the Baseline closes; (b) answer the install question truthfully; (c) keep your tap key confidential and rotate it if exposed; and (d) represent and warrant that you have all rights, consents, and lawful bases to report the envelope of the calls the tap reports and to declare the tags you declare (the Terms' regulated-data rules apply).

6. Access after the close; what stays

After the close the Assessment's pages, charts, computed sentences, export and chain head remain available in your organization for as long as it exists, subject to the Data Retention & Deletion Policy, whether or not you start a plan. Nothing is erased for not starting one, and no deadline is set on the choice. Nothing about the Assessment obliges you to buy anything, route any traffic through Recovea, or change your provider relationship. Whether to remove the tap line at any time is your choice; while no plan is active it reports nothing, and removing it changes nothing on the page.

7. The nature of the figures (read this twice)

7.1 Three labels, no fourth. Every figure in the Baseline and in the Assessment carries one of three labels. Reported means the figure is what your own software reported to the tap: token counts, statuses, timings, and counts of calls, as the provider's own client reported them and as your application forwarded them. Modeled means Recovea computed the figure from reported figures and a stated method — a cost figure is reported tokens multiplied by the prices in Recovea's frozen, versioned reference price list, whose version is printed with the figure; a bound is computed from a printed formula. Declared means the figure is something you typed: an install answer, a tag, an invoice total you gave us. A reported figure is not a measurement Recovea made; a modeled figure is not an invoice; a declared figure was not checked against anything. No figure in either is described as measured, verified, audited, or certified, and where Recovea's reference price list carries no price for a model, the cost figure is shown as unknown, never as zero.

7.2 Cost, never savings. The Baseline and the Assessment state what your AI calls cost and where that cost would break under scrutiny or run away without a ceiling. Neither states savings, a savings percentage, a return on investment, whether any spend was worth it, or what you would have spent under a different design; neither compares your figures to any baseline of Recovea's choosing, and neither offers a projection. The Savings Claims Substantiation Policy binds every sentence the Service computes on either, and the moves in §1.7 are stated as bounds on cost or exposure rather than as savings.

7.3 Not an audit, not advice. Neither the Baseline nor the Assessment is an audit, attestation, examination, assurance engagement, fairness opinion, or valuation, and it is not legal, tax, accounting, financial, insurance, or investment advice. Recovea is not a CPA firm, an auditor of record, a law firm, an insurer, or a broker, and no regulated professional service is provided. Where a section says a number "would hold up" or "would break," that is a computed description of the record and its gaps, not an opinion on any legal, regulatory, or contractual question. Decisions made from either — billing, pricing, vendor, architecture, budget, disclosure, or transaction decisions, and the decision to start a plan — are yours alone.

7.4 Where the invoice controls. Where a figure in the Assessment and your provider's own invoice differ, the invoice controls. Tell Recovea and Recovea will look at the arithmetic with you; where a figure cannot be reconciled because the tap did not report what would be needed, Recovea will say that instead.

7.5 No authorship, and what the pages claim. No person at Recovea writes any part of the Baseline or the Assessment; every sentence on them is computed by the Service from the figures beside it, by a method that is printed or exportable. Neither page makes a proof claim: what each states is that its figures were computed from the events your own application reported, and that you may export those events and check the arithmetic. It claims no receipt and no chain of custody over a tap event, because there is none. What it does carry is a hash chain over the tap events as Recovea stored them (§11.1): the page prints the chain's head, the export carries every link, and you can re-derive the chain from your own export with the published tool. A server-side chain proves the events were not altered after receipt, not that they were true; a proof claim beyond that on the page that offers you a plan is the one sentence this company cannot afford to write. The AI Output & No-Guarantee Disclaimer and the Ledger & Report Reliance Disclaimer apply to the Assessment as a Recovea Output, and nothing on it is a warranty.

8. Corrections

8.1 Errors in the arithmetic. You may tell Recovea at any time that a figure on the Baseline or the Assessment is wrong against §1 or §7. Recovea will correct a demonstrable error in the computation or the charts within a reasonable period and say what it changed; where a figure cannot be corrected because the tap did not report what would be needed, Recovea will say that instead. There is no review window, because nothing is delivered and nothing expires.

8.2 Reserved. (The money-back guarantee stood here until 2026-09-23. The Assessment carries no fee, so there is nothing to refund; the guarantee is retired under ruling 81 and its statement in the Refund & Cancellation Policy is retired with it. A Subscription's refunds are governed by that Policy.)

8.3 Reserved. (The consequences of a refunded Assessment stood here; there is no refund of an Assessment.)

9. Reserved

(The credit of the Assessment fee toward an annual Subscription stood here until 2026-09-23. There is no fee, so there is nothing to credit; the Section is retired under ruling 81. The annual plans' published prices are their own terms.)

10. Confidentiality; license to the Assessment; publicity

The reported and declared figures of your Baseline and of your Assessment, and the computed pages made from them, are your Confidential Information. From the close you hold a perpetual, non-exclusive license to use, reproduce, and share the Assessment internally and with your clients, professional advisors, auditors, examiners, lenders, and investors under confidentiality. That license survives an erasure as to any copy you already hold: an erasure is Recovea deleting Recovea's copy at your request, and nothing in §11.4 asks you to give back or destroy what you were licensed to keep. Recovea retains all rights in its methodology, tools, the computed-sentence templates, the Tap Schema, and know-how, and may retain learnings only as Aggregated/De-identified Data as the Terms permit. Neither party may use the other's name, logo, or the Assessment's existence or results publicly without prior written consent; any reference, testimonial, or case study requires your explicit written opt-in and complies with Recovea's claims-substantiation controls. Recovea will never state or imply that a Baseline or an Assessment "verified" anything.

11. Data the Baseline and the Assessment collect

11.1 Tap events. The submissions the tap sends are stored as "tap events": one row per call, holding only the Tap Schema's fields. By design the table that holds them has no column that can hold content. Tap events are not entries in the Recovea Ledger and are not covered by the Ledger's integrity carve-out in the Data Retention & Deletion Policy. Each stored tap event is linked into a hash chain kept per organization under the published recipe recovea-tap-chain-v1: the Baseline and Assessment pages print the chain's current head, the events export carries every link, and the published tool re-derives the chain from the export offline. The chain shows that the stored events were not altered after Recovea received them; it does not show that they were true, and it is not a receipt. On deletion they are deleted in full, links and head included (ruling 75).

11.2 Personal data. Tap events contain personal data only where you place it in a tag; the DPA governs its Processing, with you as controller and Recovea as processor, and the Privacy Notice describes the tap-event category. The tap key is a credential and is handled as the Security Statement describes. A Baseline is Processing under the DPA on the same footing as any other feature of the Service, and the fact that no fee was paid changes none of it.

11.3 Retention. Tap events, the install answer, the declared invoice total and the computed pages are retained for the period the Data Retention & Deletion Policy states for them and are deleted on request under the Terms' erasure provisions, subject to Recovea's retention of records of any Subscription transaction itself.

11.4 What an erasure removes, and what it keeps. A sanctioned erasure removes the tap events, the chain and its head, the computed figures and pages, the tag, the invoice total you declared, and your answer to the install question about whether clients or your own customers pay for what your AI does — that last one because it is a statement about how your business runs, and an erasure that left it sitting there would not be an erasure. It also revokes the tap key, which is why the endpoint afterwards refuses that key exactly as it refuses an unknown one (§4.8). What it keeps is the record of any Subscription transaction: that a plan was bought, when, for how much, and whether it was refunded, which the Terms and the Refund & Cancellation Policy reserve. A Baseline and an Assessment leave no transaction record, because there was no transaction.

11.5 Aggregation. Recovea may use Aggregated/De-identified Data derived from tap events, as the Terms define and permit, and never in a way that identifies you, your customers, or your tags.

12. Liability

For claims arising out of or relating to a Baseline or an Assessment, for which no fee is paid, the Terms' general limitation of liability applies and these Assessment Terms create no separate cap; nothing furnished at no charge carries a greater liability than the Terms allow. The Terms' mutual exclusions, uncapped matters, and gross-negligence treatment, and the DPA and BYO-Key allocations, continue to apply. Recovea represents no insurance coverage in connection with a Baseline or an Assessment absent an express written statement to you. A Subscription's liability terms are the Terms'.

13. Term; ending

A Baseline begins when you create it and closes as §5.2 states, seven calendar days from the first whole day of priced calls or sixty days from its creation, whichever comes first, or earlier if you end it; Recovea may lengthen one where too little ran, and may end or decline one at any time under §2.4. The Assessment appears at the close and remains readable for as long as your organization exists, or until an erasure. A Subscription's term is the Terms'; when it ends, the tap stops reporting (§4.8) and the Assessment stays readable as it last recomputed. Termination of your organization ends everything here; the Terms' export and erasure provisions apply to its data.

14. Precedence; changes; survival

14.1 Precedence. These Assessment Terms are part of the Agreement. For the matters they expressly address, they control over any other Recovea document that describes the Baseline or the Assessment; the Terms' order of precedence otherwise governs, and the Terms govern a Subscription. A signed Order Form or Master Services Agreement that expressly addresses the Baseline or the Assessment controls over these Assessment Terms for that customer.

14.2 Changes. Recovea may update these Assessment Terms prospectively; the version in force when your Baseline is created governs that Baseline and its Assessment. Changes are recorded in the change log below.

14.3 Survival. Sections 7, 10, 11, 12, and 14 survive the close and the end of an organization's use of the Service.

(PENDING COUNSEL: these Assessment Terms were restated in full on 2026-09-23 under founder ruling 81, which retired the fixed-fee Assessment, its guarantee and its credit, and made the Assessment a free, fully computed feature that ends in a plan offer. No customer accepted the previous version: the two purchases made against it on 2026-09-23 were the founder's own production walk, refunded and erased the same day. Counsel questions carried forward and added to: 1. the free Baseline and the free Assessment under consumer-protection framing (carried from question 7 of the previous version). A free, no-card product that collects data, produces a report and ends in an offer needs checking against the automatic-renewal and negative-option rules even though nothing renews and nothing is charged; Recovea's position is that neither applies because no payment instrument is taken and nothing converts by default; counsel should confirm; 2. NEW — the plan started without a trial (§5.4). The Terms of Service describe a fourteen-day card trial on paid plans; a plan started from the Assessment page begins at once and is charged at checkout. The Terms' trial clause needs the exception stated in terms (batch 16 carries it), and counsel should confirm that the disclosure at that checkout (the amount charged today, the renewal amount and date) satisfies the automatic-renewal rules for the state of the buyer; 3. NEW — a computed report with no author (§7.5). Every sentence is generated by the Service; no person writes or signs it. Counsel should confirm the reliance disclaimer's "Recovea Output" definition covers a computed narrative, and whether "not advice" needs restating where a computed sentence recommends a control; 4. liability for a free feature (§12, carried). No fee, so the Terms' general limitation governs both features; counsel should confirm that is the right allocation for a no-charge feature that produces figures a customer may act on; 5. the erasure's 401 (§4.8, §11.4, carried). The erasure revokes the credential, so an erased customer's key is refused exactly as an unknown key is, with no explanatory answer; counsel should confirm there is no notice obligation that the silence defeats; 6. NEW — the tap after a plan ends (§4.8). When a plan ends the endpoint answers as it does at a close and the library re-checks on the customer's own calls; reporting continues to the end of a cancelled period because the plan is active until then. Counsel should confirm nothing in the Terms' termination provisions requires anything different. Retired with this version: the checkout-as-order formation question, the thirty-days-from-delivery question, the refund-or-credit election question, the perpetual-sections question as it bore on a purchase, and the E&O/cyber gate as it bore on a delivered engagement (there is no delivery).)

15. Change log

Entity: Recovea, Inc., a Delaware corporation. Notice/registered address: 2810 N Church St STE 89986, Wilmington, DE 19802. Governing law / venue / disputes: as stated in the Terms of Service (State of Delaware; binding individual AAA Commercial arbitration seated in Wilmington, Delaware, with the Terms' carve-outs). Contact: legal@recovea.ai.