Skip to content
Jithox
Sign inNL

Trust and limits

These are the mechanisms Jithox actually ships, and — just as important — what they do not prove.

Last updated: August 2026.

Mechanisms

  • Human approval. A side-effecting action runs only after an explicit human yes. Approval binds to the exact content: workspace, approver, document snapshot, recipient, subject, body and attachment identity.
  • Immutable snapshots. What you approved is what executes. Any edit after approval produces a new identity, the stale approval is withdrawn, and dispatch refuses drifted content before any network call.
  • Exactly-once execution. Dispatch claims an idempotency key before the provider is called. A double click, a retry, a lost response or a second tab can never produce a second send.
  • OAuth and scopes. The public MCP authenticates every call with OAuth 2.1 and scopes; its five tools are read-only. A token without the right scope is refused.
  • Signed receipts. Confirmed executions and verified delivery events produce append-only, signed receipts carrying commitments instead of raw personal data.
  • Truthful provider states. Provider acceptance is never shown as delivery. Ambiguous outcomes stay ambiguous and are never retried blindly.
  • Revoke and recovery. Suppressed recipients are blocked before a new proposal is created, a corrected address requires a fresh approval, and access grants are revocable.

Verify a receipt yourself

A signed receipt is only worth something if you can check it without asking us. The public key does not travel inside the receipt you are checking — it is published separately, so fetch it once and every later verification is a local, offline computation. Signatures are Ed25519, and the key id is derived from the key itself, so a receipt cannot be verified against the wrong key by accident.

Honest limits

  • Internal testing is not an independent penetration test. An independent security assessment is planned before broad activation; it has not happened yet.
  • We do not claim SOC 2, ISO 27001 or similar certifications.
  • A signed receipt proves what Jithox executed and observed. It does not prove the legal or fiscal correctness of a document.
  • Delivery means the receiving mail server accepted the message. It does not prove a human read it, agreed with it, or will pay it.
  • An “unavailable” answer from a registry is an availability fact — never a negative business fact about you or a counterparty.

Security contact

Found a vulnerability or an incident? Write to the contact address — a human reads every report. Please leave exploit details of live customer data out of the first message.

info.jithox@gmail.com