The contract stays on your hardware.
Charter parties reveal rates, counterparties and negotiating positions. Using intelligence software should not require sending that information to somebody else’s cloud.
The argument · in three clauses
Clause 1. The contract is commercially sensitive.
Clause 2. The facts needed to test it often sit outside the contract.
Clause 3. Bring the data to the contract; do not send the contract to the data.
Where the documents go
The document is read, parsed and stored on the customer’s machine. No page, clause or extracted term is transmitted.
The model and OCR run locally. The database is a file on the customer’s disk.
The external lookup boundary
The current deployment makes two external lookups available. Both are optional and disclosed below.
| Lookup | What crosses the wire | What comes back |
|---|---|---|
| Vessel registry | A vessel name or IMO number, nothing else | Class, flag, PSC detention history |
| Route weather | Coordinates and a date, nothing else | A forecast along the route |
Both can be switched off. CharterWise runs fully air-gapped when they are disabled.
What we never collect
No telemetry, no analytics, no crash reports, no usage statistics. CharterWise has no means to see what a customer processes.
Deployment
CharterWise installs on hardware the customer controls. Each installation is single tenant and shares nothing with another.
The data can travel. The contract does not.
External information can improve a voyage working without seeing the agreement. CharterWise separates the lookup input from the contract text. The external service returns data; the local engine decides how that data interacts with the clause.
On certifications
CharterWise does not currently hold SOC 2 or ISO 27001 certification. The deployment is deliberately inspectable: a customer’s security team can review the installation and observe its network traffic while it runs.
This website
This site is static. It sets no cookies, runs no analytics and makes no third-party requests.