Terms of Service

Last updated 21 August 2026

1. What the service is

CONSTRUX.AI records project state as an append-only, hash-chained event log and computes engineering and commercial positions from it. It is a record and a calculation engine. It is not legal advice, not a substitute for a contract administrator, and not a guarantee of any commercial outcome.

2. What the calculations are and are not

Statutory positions — payment cycles, notice deadlines, adjudication timetables — are computed from the dates and terms you supply, against the rules in force for the jurisdiction you select. If the inputs are wrong, the output is wrong. Where the platform lacks a fact it does not invent one: no exchange rate is assumed, no interest rate is supplied, and a figure that depends on an unpublished rate appears in its own currency with the reason.

3. Your account and your people

The administrator of a tenancy controls who holds an identity in it and what each may do. Seats are consumed by identities, not by logins. A platform operator identity and a regulator identity consume no seat, and the operator is barred from customer delivery data by the permission model rather than by policy.

4. Packages and what they include

What each package includes is stated on Get started and enforced by the product. A trial governs, records and computes and cannot export or print. Where a limit applies, the platform states it in commercial terms rather than as a permission failure.

5. AI usage and charging

AI actions are charged in ACUs against the provider cost actually incurred, at the published multiplier. No provider is called on an empty wallet, and no charge is made without a corresponding ledger entry. Before an action runs, its cost is quoted from what that action has actually cost on your account — where it has never run, the quote says so and states the provider's floor rather than presenting a floor as a forecast.

No AI agent holds a mandate above PROPOSE. Every governance decision is taken by a person, and the event catalogue refuses AI authorship on decision events.

6. Your data

Your project record is yours. It is held in your tenancy, isolated on every read, and exportable in full on a package that includes export. We do not use your project data to train models. See the Privacy Policy for what we hold and why.

7. The record is append-only

This is a feature with a consequence you should understand before you rely on it. Nothing is edited in place and nothing is deleted; a correction is a new event and the original stays visible. That is what makes the record evidence. It also means a value entered incorrectly is corrected rather than erased, and the incorrect entry remains part of the chain.

8. Availability

Availability commitments are set in an enterprise agreement where one exists. On self-serve packages the service is provided as-is, and current state is published on Platform status.

9. Ending the relationship

You may close a tenancy at any time. On closure you may export the complete record while the tenancy is still live — export first, then close, because the export entitlement goes with the package.

This document describes how the platform behaves. Where it states a technical guarantee — chaining, redaction, tenancy isolation, notice handling — that behaviour is implemented and tested, and the corresponding test is the thing that keeps this page true.