How Chartera reads email
Supported inbox workflows use read-only access or forwarding-based intake. Chartera does not send, delete, relabel, or move email through a connected account.
Trust center for source-linked maritime work
Chartera is built for teams handling fixtures, CPs, recaps, SOFs, voyage records, invoices, claims context, and private desk communication. This page summarizes how data enters the system, what remains reviewable, and what procurement teams should inspect first.
Where control stays with the desk
Trust is practical: source material stays visible, outputs remain reviewable, and commercial decisions do not leave the desk without source context.
Source-linked by design
Outputs retain traceable source references.
Human in control
Commercial decisions stay reviewable before use.
Read-only intake
Supported inbox workflows avoid send, delete, relabel, or move actions.
Audit and deletion
Security review covers scopes, retention, and deletion workflow.
Desk control model
Chartera prepares the packet. The desk makes the call.
This is the trust point buyers should inspect: Chartera can narrow the review work, but the commercial call remains an explicit desk step.
Prepared by Chartera
Classify the packet, assemble TC or voyage context, expose missing evidence, and show the desk item.
Checked by the desk
Confirm the match, correct the record, ask for clarification, escalate, approve, or hold it back.
Carried into the file
Keep the source trail, review state, and desk decision attached to the operational record.
Controls buyers usually ask about first
These are the trust topics that matter before a maritime team connects operational data or routes fixture, laytime, claims, or document work through Chartera.
What is processed
Approved workflows may process emails, attachments, documents, operational records, parsed outputs, and source references needed for review.
How AI is used
AI assists classification, parsing, summarization, and context assembly. It is not positioned as a replacement for human commercial review.
What remains reviewable
Outputs should preserve source references, review state, and the evidence trail behind cockpit items, contract records, and operational artifacts.
Data lifecycle
Customers can revoke connected access and request deletion according to agreed retention terms. Deployment-specific details are reviewed with each customer.
Security review packet
OAuth scopes, subprocessors, deployment expectations, data hosting, model-use policy, and deletion flow can be reviewed during procurement.
Procurement quick sheet
This is not a substitute for a customer security review. It is the public baseline a buyer can send to security, procurement, or legal before requesting the full review packet.
Email access
Read-only or forwarding-based intake for supported workflows; no send/delete/relabel/move behavior through connected inboxes.
Processed records
Emails, attachments, documents, operational records, parsed outputs, and source references used for approved workflows.
AI usage
Classification, parsing, summarization, and context assembly with desk review retained for commercial decisions.
Source trail
Outputs are designed to retain source references and workflow context before operational use.
Security review
Provider scopes, subprocessors, deployment model, hosting expectations, and deletion workflow are reviewed with customers.
Procurement questions
Can Chartera operate inside our connected inbox?
For supported inbox workflows, Chartera uses read-only access or forwarding-based intake and does not send, delete, relabel, or move emails through the connected account.
Is customer data used to train public AI models?
No. Customer data is processed for approved workflows and is not used to train public models.
Can we disconnect access?
Yes. Connected access can be revoked, and deletion can be requested according to the customer's retention and deletion terms.
What should our procurement team review first?
Start with email access model, data handling, model-use policy, deployment expectations, source-reference behavior, subprocessors, and deletion workflow.