There is nothing to leak to.
A charter party carries hire, cargo, counterparties and negotiated terms. The industry rightly refuses to upload that to other people’s computers. CharterWise is designed around that refusal.
The argument · in three clauses
Clause 1. The industry digitised everything except the contract.
Clause 2. Contract intelligence moved to the cloud, and shipping cannot follow it.
Clause 3. So the software must come to the documents.
Where the documents go
Nowhere. The document is read, parsed and stored on the customer’s machine. No page, no clause and no extracted term is transmitted anywhere.
The language model runs locally. The OCR runs locally. The database is a file on the customer’s disk.
What the software sends out
Two lookups, both optional, both disclosed in full:
| 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. With them off, CharterWise runs fully air-gapped.
What we never collect
No telemetry, no analytics, no crash reports, no usage statistics. We cannot see what a customer processes, because we designed away the ability to.
Deployment
CharterWise installs on hardware the customer controls: one desk or one office, single tenant, nothing shared between installations.
Why this is the wedge.
Every cloud contract platform asks shipping to change its mind about confidentiality. CharterWise asks for nothing: it moves the software to the documents instead of the documents to the software. That position is structurally hard for a cloud platform to copy, because copying it means abandoning their own architecture.
On certifications
We are early, and we do not yet hold SOC 2 or ISO 27001. We take a different route to assurance: an architecture with no cloud to certify. A security team is welcome to inspect the deployment and watch the network while it runs.
This website
This site practises the same discipline: static pages, no cookies, no analytics, no third-party requests. What you read here stays between you and your browser.