CIPHERQUAY · LEGAL
Platform and Console Terms
Draft framework for approved business-to-business CipherQuay access.
DRAFT FOR REVIEW · 3 OCTOBER 2026 · VERSION 2026-10-03-DRAFT-1
This CipherQuay-specific draft requires operator and legal review before being treated as an approved policy or contractual commitment. Visiting this page does not execute an enterprise agreement.
Status and agreement
No public production service or authenticated customer console is available through this website. This notice is a draft framework, not an executed service agreement. Approved design-partner or pilot access must be covered by a separately signed agreement defining scope, fees if any, responsibilities and exit conditions.
Authorised use and tenant boundaries
An agreement must identify the participating organisation, authorised people, environments, permitted integrations and delegated authority. A machine must not approve itself, expand its own authority or suppress evidence. Customer credentials and confidential data must not be submitted to the public synthetic staging workspace.
Operational responsibilities
CipherQuay does not replace IAM, PAM, SIEM, DLP, EDR, model security or legal judgement. Customers remain responsible for their systems, lawful instructions and independent safeguards. Live enforcement, availability commitments, support, retention, incident handling and liability limits must be expressly agreed; none are offered by this draft.
Data, termination and rights
Any agreement must address controller and processor roles, security, exports, deletion, suspension, termination and intellectual-property licences. No licence to protected decision mechanics or patent rights arises merely from visiting the website or viewing synthetic simulations.
