Skip to content
← All legal documents

Beta and Evaluation Addendum

The additional terms that apply while OakHive is in private beta, and what changes when it is not.

Applies to
Beta customers
Last updated
1 September 2026
Questions
legal@oakhive.ai

OakHive is in private beta: a working product with a small number of selected customers, not a generally available service. This addendum modifies the Subscription Agreement to say so honestly, and to be clear about which promises are reduced and which are not.

Beta is a legitimate stage, badly served by pretending otherwise. The risk in a beta is not that the vendor admits it — it is a vendor selling beta software on terms written for a mature one, then leaning on a disclaimer when something breaks. This addendum exists so nothing here is a surprise later.

1When this addendum applies

1.1This addendum applies where your Order Form identifies the subscription as a beta, pilot, evaluation or early-access engagement, and it applies for as long as that is the case.

1.2Where it conflicts with the Subscription Agreement, this addendum prevails — except where the Order Form says otherwise, in which case the Order Form does.

1.3Terms used here have the meaning given in the Subscription Agreement.

2What private beta actually means here

Concretely, as at the date of this document:

  • The product is real and interviews real people. It is not a prototype and not a demonstration.
  • The customer base is small and each engagement is individually supported.
  • The service runs on a single instance of each component by design, because interview state is held in memory during a session. That is a correctness decision. A browser interview rebuilds from the stored transcript and continues across a deployment.
  • Features arrive, change shape and occasionally get removed.
  • There is no third-party security certification — see the Security Overview, section 13.

3No service level, and why

3.1The Service is provided during beta without any service level commitment, uptime target or service credit.

3.2Section 15 of the Subscription Agreement continues to apply: support is available during business hours with a target first response of one business day. In practice a beta customer gets more attention than that, not less — but the target is what we will commit to in writing.

3.3The warranty in clause 16.2 — that the Service is provided with reasonable skill and care — is not reduced by this addendum. Neither is the security warranty in clause 16.3. Beta reduces what we promise about availability, not about care or about how your data is handled.

4The product will change under you

4.1We may change, add to or remove features during beta with less notice than clause 21.2 of the Subscription Agreement requires, and a change may occasionally be disruptive.

4.2We will tell you before a change that materially affects how you use the Service, and we will not remove a feature you depend on without discussing it with you first.

4.3Where a change materially disadvantages you, your remedy is section 7 of this addendum: leave, with the prepaid remainder returned.

5What does not change in beta

This is the important section. Everything about how your data is handled applies in full during beta. A beta is a reason to expect a rough edge in the product. It is not a reason to accept weaker data protection, and we are not asking you to.

  • The Data Processing Agreement applies in full, including the security measures in Annex II and the 72-hour breach notification.
  • Subprocessor notice and your right to object apply in full — 30 days, as usual.
  • Customer Data is never used to train models. Beta status changes nothing about that, and we will not ask you for an exception.
  • Confidentiality obligations apply in full, in both directions.
  • Data export and deletion on exit apply in full, on the timetable in section 14 of the Subscription Agreement.
  • The Acceptable Use Policy applies in full.

6Feedback

6.1We will ask for your view on how the product is working. You are not obliged to give it, and a subscription does not depend on it.

6.2Feedback you do give may be used freely, as clause 11.3 of the Subscription Agreement provides. We will not name you as its source without your consent.

6.3Feedback is not a licence to your data. Nothing in this section lets us use interview content, and we will not quote a transcript back to anyone — including in a product discussion with you — beyond what your own users can already see.

6.4Being a beta customer does not entitle us to name you publicly. Clause 22.1 stands: your name and logo need your written consent.

7Getting out

7.1During beta, you may terminate on 30 days’ written notice at any time, for any reason, and we will refund the prepaid fees for the unused remainder of the term on a pro-rata basis.

7.2This is deliberately wider than clause 13 of the Subscription Agreement, which does not allow mid-term termination for convenience. If you take a chance on an early-stage product you should be able to stop without arguing about whether we breached something.

7.3Export and deletion follow section 14 of the Subscription Agreement: a 30-day export window, deletion within 60 days.

8When beta ends

8.1We will give you at least 60 days’ notice before this addendum stops applying to your subscription.

8.2At that point the Subscription Agreement applies without modification, together with any service level agreed on a new or amended Order Form.

8.3The notice will say what changes for you commercially. If the terms on offer at the end of beta do not suit you, section 7 remains available until the addendum ends.

Questions

legal@oakhive.ai.

The rest of the pack