Security
Built around the record.
Implemented today: account access
Checks, evidence, certificate claims, API keys and entitlement are resolved from the authenticated session’s account membership. Account ownership is never accepted from a URL, a request body or a tool argument. A record belonging to another account is indistinguishable from one that does not exist.
Implemented: Append-only history
Completed checks, their evidence and submitted certificate claims cannot be edited or deleted; the database rejects the attempt. A correction is a new record, so what was known when a load was booked survives.
Implemented: Deterministic evidence states
Application code, not model output, sets verification state, comparison status, source outcomes and review findings. Language models may explain evidence; they cannot create or change it.
Implemented: Credential handling
API keys are displayed once at creation, stored only as a hash, and can be revoked. Connector access is scope-limited and rate-limited. Source credentials are stripped from any URL before it is stored or displayed.
Implemented: Error logging
Failures are logged as an error name and a bounded message. Submitted certificate values are not written to logs.
Not implemented
The optional ChatGPT certificate pilot accepts bounded PDF, PNG and JPEG attachments through ChatGPT file references. The original files are processed temporarily and are not retained. Jibletto does not provide malware scanning or document-authenticity verification. There is no security certification, no independent audit, no formal incident response process and no published retention or deletion policy. The API and MCP connector remain in development and are not verified in production.
Reporting a concern
Reply to any Jibletto sign-in or service email to reach the team. Please do not include passwords, API keys or carrier documents in a first message.