1. Contract structure and parties
The supplier will be [MassTrail contracting entity—pending clearance] and the customer identified in a signed order form. The order form should identify the programme, organisations, environments, users, sources, service tier, term, fees, support coverage, data region and incorporated schedules. The signed order form and negotiated schedules prevail over a public summary.
2. The service
MassTrail provides Verify + Control + Close software and related implementation/support: registered evidence endpoints, source ingestion, technical evidence classification, deterministic controls, neutral exception workflows, maker-checker decisions, period-close snapshots, signed exports and a read-only reviewer workroom. Entitlements and implementation deliverables are limited to the order form.
3. What MassTrail does not do
- MassTrail does not audit, certify, express assurance, approve legal compliance or speak for a regulator.
- It does not certify a scale, load, material, recycling outcome, counterparty or source record.
- It does not collect, transport, store, broker, buy or sell waste and does not execute or hold customer payments.
- “Verified” describes disclosed technical evidence criteria and corroboration, not physical truth or a legal conclusion.
Customer management owns reporting criteria and final reports; any appointed practitioner owns their independent conclusion.
4. Accounts, identity and authorised users
The customer appoints authorised users and is responsible for accurate membership and role information, timely removal, compatible identity systems and protection of credentials. Users may not share accounts, bypass MFA, probe another organisation or use a device identity outside its assignment. Support access must be expressly granted, time-bound and audited except for a documented emergency process.
5. Customer responsibilities and authority
The customer must have authority to provide each source, personal-information category, device feed and counterparty record; give required notices; maintain source-system and scale/device approvals; configure its reporting policy; review exceptions; and approve the final close. It must not direct MassTrail to conceal a limitation, rewrite committed evidence or describe a low-authority capture as instrument-attested.
6. Sources, criteria and evidence authority
Source data can be incomplete, inaccurate, late or controlled by the customer or a third party. MassTrail preserves the submitted payload and provenance and applies the configured rule/version; it does not guarantee source truth. Evidence levels, independence, device health, fallbacks and unresolved limitations remain visible. Customer-specific policy must not be represented as law.
7. Corrections, close and reliance
Committed evidence and close snapshots are append-only. Corrections, exclusions, approvals and reopens create linked events or later versions. Exports carry scope, hash/signature metadata, expiry and limitations. A reviewer or other recipient must assess whether the pack is suitable for its purpose and may not infer that MassTrail has endorsed management’s report.
8. Imports, third parties and integrations
Connectors, customer systems, scales, trackers, messaging providers and counterparties remain third-party dependencies. The order form must allocate credentials, approvals, data costs, maintenance, rate limits and failure handling. MassTrail may suspend an unsafe or unauthorised connector. Third-party terms apply directly between the customer and that provider unless expressly stated otherwise.
9. Devices, tags and field installation
ProofNode or other industrial integration requires a supplier-approved read-only interface and an authorised installer. Device identity, assignment, firmware/config state, health, clock and revocation are evidence. The customer provides safe site access, power/connectivity and equipment responsibility stated in the device schedule. MassTrail does not perform legal-metrology verification or override a scale supplier’s controls.
10. Acceptable use
Users may not upload unlawful or malicious material; infringe rights; introduce malware; scrape or overload the service; test security without written authorisation; reverse engineer except where law cannot exclude it; evade tenant/role controls; fabricate identity or evidence; or use the service for an autonomous adverse decision about a person. The customer remains accountable for its users and counterparties.
11. Customer data and intellectual property
The customer retains its rights in customer data and grants the limited rights needed to host, secure, transform and return it under the contract. MassTrail retains its software, documentation, rule framework, product-neutral methods and improvements that do not disclose customer confidential information. No ownership transfers merely because a configuration, report or feedback item is used in the service.
12. Confidentiality
Each party must protect the other’s non-public business, technical and security information, use it only for the agreement and disclose it only to people/providers bound by appropriate duties or where law requires. The signed agreement must state exclusions, compelled-disclosure procedure, survival and permitted reviewer/regulator disclosure.
13. Privacy and security
The approved privacy notice, DPA and security schedule will define responsible-party/operator roles, processing instructions, sub-processors, transfers, retention, data-subject support, incident notification and audit evidence. The customer must not place prohibited/unmapped fields into the service. Security obligations are shared; no party can guarantee that an internet service will never experience an incident.
14. Availability, support and changes
Availability, maintenance, severity definitions, response targets, service credits and exclusions belong in the order form/SLA. Synthetic demonstrations carry no production SLA. MassTrail may make compatible service improvements, but a material reduction in contracted functionality or security requires the notice/remedy agreed in the contract.
15. Fees, taxes and expenses
Fees, implementation/commissioning, usage limits, expenses, VAT, payment dates, annual changes and late-payment remedies must be stated in the order form. MassTrail must not alter evidence outcomes because an invoice is disputed; suspension and data access/exit rights require a controlled process.
16. Suspension
Access may be restricted where reasonably necessary for security, unlawful use, material breach, non-payment after the contractual cure process or protection of another tenant. Where practicable the customer receives notice, scope/reason and restoration steps. Suspension must preserve committed evidence and must not silently change a close.
17. Term, termination and exit
The signed documents must specify start, renewal, termination rights and cure periods. On exit, authorised users lose access; the customer receives an agreed machine-readable export; credentials are revoked; and data is returned, retained, restricted, de-identified or deleted according to the approved schedule, legal holds and evidential obligations. Export availability and assistance fees must be explicit before signature.
18. Warranties and disclaimers
Any service-performance warranty and remedy must be negotiated. Drafting must preserve non-excludable South African rights while making clear that customer/third-party data, physical events and regulatory acceptance are not guaranteed; results depend on configured criteria and supplied evidence; and beta/synthetic features are not production services.
19. Liability, indemnities and insurance
[Counsel drafting required.] The agreement must address direct-loss caps, excluded loss, confidentiality/privacy/security carve-outs, IP claims, customer data/authority and unlawful-use indemnities, mitigation, claim procedure and required insurance. A competitor’s foreign-law cap or disclaimer is not adopted by default.
20. Law, disputes and general terms
[Counsel drafting required.] The intended baseline is South African law and an agreed South African forum/dispute process, subject to entity and customer review. The final agreement must also cover notices, assignment/change of control, subcontracting, force majeure, anti-bribery, export/sanctions where relevant, severability, waiver, relationship, entire agreement, counterparts and electronic signature.
21. Contact and version
Version: pre-launch counsel-review draft 2026-10-30. Contract, legal and security contacts remain placeholders until entity/name clearance, Information Officer registration and production support ownership are complete.