01
Connect
Use only the sources and permissions required for the agreed workflow.
Trust
Security for sensitive maritime work.
Chartera is built for teams handling fixtures, CPs, SOFs, voyage records, claims, and private desk communication.
Workflow Boundary
Clear access. Defined use. Human review.
Security is designed into how a workflow connects, processes information, and reaches the team.
02
Process
Analyze the selected commercial information for that workflow, not public-model training.
03
Review
Keep the relevant basis available so the team can check, correct, approve, or hold the work.
Core Controls
The controls buyers ask about first.
Access Control
Role-based access controls help teams restrict who can view, edit, and approve commercial work.
Review & Audit
Actions retain the relevant references and history so teams can review what changed and who approved it.
Data Residency
Deployment and hosting options can be aligned with customer regulatory and internal policy requirements.
Data Use
Customer data is processed for the agreed use of Chartera and is not used to train public models.
Deployment Review
The details are agreed before the workflow goes live.
We review the proposed data flow with each customer rather than hiding deployment choices behind a generic security statement.
See the Full Trust ModelConnections
OAuth scopes, inbox permissions, VMS access, and any custom system connection
Model Use
Model providers, subprocessors, and the data each approved workflow requires
Hosting
Deployment architecture, data residency, and customer policy requirements
Access
User roles, approval responsibilities, and who can see commercial records
Retention
How long workflow data is kept and how deletion requests are handled
Audit
The history, references, and approvals retained around material work
Common Questions
Straight answers for a first review.
We can review your infosec checklist, architecture requirements, and deployment needs directly.
Can Chartera send, delete, or modify emails through connected inboxes?
No. OAuth inbox connections use read-only access for supported providers. Chartera does not send, delete, relabel, or move emails through your account.
Is customer data used to train public AI models?
No. Customer emails, documents, messages, and voyage records are processed to support the agreed use of Chartera; they are not used to train public models.
Can customers disconnect access or request data deletion?
Yes. Connected email access can be revoked, and customers can request deletion according to the retention and deletion terms agreed for their deployment.
How can teams review AI-assisted work?
Outputs retain the relevant messages, clauses, reports, SOFs, invoices, or records so operators can check the underlying information before acting.