Assurance posture
Implemented application controls, described without borrowed trust marks.
This record describes implemented application controls. Chronicle does not claim a third-party certification or independent audit on this page.
Trust & security
Your front desk. Your rules. Clear safeguards.
Customer conversations deserve clear boundaries. Chronicle checks proposed actions before delivery, holds sensitive work for your team, and records the decisions behind each step.
How a reply reaches a customer
- 01Proposed actionRecorded
- 02Policy resultEvaluated
- 03Human decisionWhen required
- 04Delivery attemptAfter approval
Consequential stops remain human decisions
00–08On this page9 sections
Safeguards at a glance
What protects your customer conversations.
Every tile below is an implemented architectural boundary. There are no unverified compliance badges or borrowed ratings on this page.
- Authority gateCTRL-01
Policy runs before transport. Consequential stops remain human decisions.
- Operating principle
Autonomy is earned at every boundary. A control surface never claims an audit or certification it has not completed.
Chronicle trust standard / implemented controls - Write-only secretsAES-256-GCM
Customer-owned connector credentials are size-validated, encrypted before database storage, and never displayed again.
- Tenant isolationRLS Scoped
Authenticated Clerk session resolved to business entity; database tables enforce business scope with no public access.
- Ingress integritySigned webhooks
Cryptographic signatures or shared secrets verified for phone, messaging, email, and voice ingress before accepting work.
- Data boundary
Customer conversations are processed solely to operate the service. Chronicle does not build a shared training corpus across tenants.
Chronicle data policy / strict tenant isolation - Boundary holdFail-closed
Urgent, fallback-routed, or unapproved actions stay pending for authenticated operator review.
Control sourceApplication behavior
Human approvalPolicy enforced
CertificationNot claimed
Last reviewed16 July 2026
Security boundaries / 03 controls
Provider calls must prove origin.
Precise product boundaries, without certification badges or blanket guarantees.
Layered control object
Ingress → ownership → credential
01 / Verified ingressProvider signature or shared secret
02 / Tenant scopeSigned-in Clerk user → business
03 / Write-only secrets
AES-256-GCM before database storage
Invalid requests → rejectedGoogle OAuth tokens → removed on disconnect
CTRL-04
Tenant scope
Business ownership is checked
Authenticated control-plane APIs resolve the signed-in Clerk user to a business and scope records to that business. Database tables use business identifiers and row-level security with no public policies; privileged server access remains responsible for enforcing ownership.
CTRL-05
Write-only secrets
Connector credentials are bounded
Customer-owned connector credentials are validated, encrypted with AES-256-GCM before database storage, and never displayed again by the control surface. Server provider keys stay in deployment environment variables; Google OAuth tokens are tenant-scoped and removed on disconnect.
CTRL-06
Verified ingress
Ingress calls must prove origin
Configured phone, messaging, email, and voice ingress validates a cryptographic signature or shared secret before processing. Routes reject invalid requests, and route-specific body limits and event identifiers reduce unbounded or duplicate work.
Audit trail / CTRL-03
The operating trail is retained.
Chronicle records inbound work, triage metadata, action intent, policy outcome, delivery attempts, and key human or configuration actions with an actor and timestamp. This is an operational audit trail, not an external assurance report.
Operational record
Activity record anatomy
- 01Inbound workRecorded
- 02Triage metadataRecorded
- 03Action intentRecorded
- 04Policy outcomeRecorded
- 05Delivery attemptsRecorded
- 06Key human or configuration actionsActor + timestamp
Operational audit trail / not an external assurance report
Data controls / CTRL-07
Use is limited to operating the service.
Conversation content is used to triage, draft, deliver, and improve rules for the same business. Model providers receive the content needed for inference under their API terms; Chronicle does not build a shared training corpus from customer conversations.
Data boundary
Conversation content / bounded uses
Input
Conversation content
Content needed to operate the service
Operational use
- 01Triage
- 02Draft
- 03Deliver
- 04Improve rules
For the same business
Provider boundary
Model providers
Content needed for inference / under their API terms
Shared training corpus
Not built from customer conversations
Shared responsibility / read before deployment
A control surface cannot replace your authority.
Tenant-scoped application access, outbound policy gates, provider-ingress checks, operational records, and the security of Chronicle-controlled systems.
Lawful collection and messaging, TCPA and channel consent, contact lists and opt-outs, approval settings, connected-account access, and review of AI output before relying on it.
Delivery, availability, and their handling of data under the terms you or Chronicle have with them. Provider failure can delay or prevent an action.
Security report
Coordinated disclosure
Found a vulnerability?
Send reproduction steps, affected surface, and potential impact to security@chronicles.systems or support@chronicles.systems. Please avoid accessing data that is not yours and allow a reasonable remediation window before public disclosure. PGP key available upon request.