01–15Document index15 sections
These terms define how a business may authorize Chronicle to operate, when a human remains responsible, and which messaging, provider, data, and commercial duties never transfer to an AI operator.
Acceptance and authority
By creating an account, connecting a business system, accepting an order form, or using Chronicle, you agree to these Terms for yourself and the business you represent. You confirm that you have authority to bind that business and to authorize Chronicle's access to connected channels and data. If you do not agree, do not use the service.
The service
Chronicle reads and triages inbound work, proposes replies and actions, routes work through configured policies, connects to supported messaging and calendar providers, and records operational outcomes. Available channels, connectors, capacity, workflow limits, support, autonomy, and deployment controls depend on the active plan and configured providers.
Channels are operational message and voice paths. Connectors are installable provider or account boundaries that carry those channels. The Pilot plan is supervised and pauses when its included allowance is reached. Paid plans can enable auto-send and Calendar write features, but only policy-approved actions can use them. An entitlement is not a promise that an unconfigured or unavailable provider will work.
Accounts and connected credentials
You must provide accurate account information, keep operator access secure, promptly remove access that is no longer authorized, and be authorized to connect each phone number, inbox, calendar, domain, or provider account. Activity under your account is treated as your activity unless you promptly report compromise.
Do not attempt to retrieve write-only connector credentials from the service. Disconnect a provider and rotate its credentials if you suspect exposure. Chronicle can suspend a connection that threatens another tenant, a provider, or the service.
Human approval and autonomy
Chronicle records an agent action intent and evaluates policy before automated delivery. Current policy requires human action for urgent work, fallback-routed or low-confidence output, SMS and missed-call replies, unconfirmed bookings, missing drafts, model-requested review, and accounts not configured for guardrail autonomy.
An authenticated operator can approve, edit, or reject a pending draft. You are responsible for selecting autonomy settings, defining business rules, maintaining escalation contacts, and reviewing consequential or sensitive work. Approval means you authorize the submitted action; rejection or correction can become a tenant-specific rule.
A human click is a control, not a legal safe harbor. You must still verify recipients, consent, claims, price, availability, and any legal, medical, financial, safety, or emergency implications.
Customer messaging, TCPA, and consent
You are the sender responsible for the customer relationship. Before Chronicle processes or sends a message on your behalf, you must have every lawful basis, notice, and consent required by the recipient's location, channel, message purpose, and applicable rules. In the United States this can include the Telephone Consumer Protection Act, state telemarketing laws, Do Not Call rules, and requirements for prior express or prior express written consent.
You must maintain evidence of consent, identify your business where required, observe quiet hours and frequency limits, use approved WhatsApp templates or categories when required, and honor STOP, unsubscribe, revocation, and other opt-out requests across every relevant system. Do not upload purchased, scraped, or stale contact lists.
Chronicle does not independently validate the lawful basis for a contact, reconcile every external suppression list, or guarantee that a draft meets every channel or regional rule. Human approval does not cure missing consent. For legal advice about a campaign or workflow, use qualified counsel.
Chronicle sends under your authority. Consent records, suppression, recipient eligibility, and the decision to initiate a message remain your responsibility.
Providers, webhooks, and identifiers
You may use only provider accounts and sender identifiers you own or are authorized to administer. Do not forge webhook events, bypass signature checks, reuse another tenant's identifiers, or route content through Chronicle to evade a provider's policy.
Provider signatures establish request origin, not the truth or legality of the payload. Messaging, voice, email, calendar, model, hosting, authentication, and payment providers remain subject to their own terms, rate limits, availability, and enforcement decisions.
Acceptable use
Do not use Chronicle for spam, unlawful surveillance, deception, harassment, discrimination, infringement, malware, credential theft, unsafe emergency automation, or content that violates a connected provider's rules. Do not probe another tenant, overload the service, defeat security or usage controls, reverse-engineer protected parts of the service, or misrepresent AI output as independently verified fact.
We can limit, suspend, or terminate access when reasonably necessary to protect people, providers, infrastructure, other customers, or Chronicle, or to comply with law. Where practical and safe, we will provide notice and an opportunity to correct the issue.
Data and instructions
You retain your rights in business data, rules, and customer content. You grant Chronicle the limited rights needed to host, process, transmit, and secure that data to provide the service. You confirm that you are authorized to give us those instructions.
Chronicle acts on your instructions for customer data. You are responsible for data accuracy, minimization, retention instructions, rights-request routing, and avoiding sensitive data that the workflow does not need. Our Privacy Policy explains provider, model, credential, retention, and deletion boundaries.
AI and operational limitations
AI output can be incomplete, incorrect, delayed, or unsuitable. Confidence values and classifications are operational signals, not guarantees. You must review output before relying on it for consequential decisions and keep an appropriate human escalation path.
Chronicle is not an emergency service and is not a substitute for legal, medical, financial, compliance, or safety advice. Connected providers can fail or reject actions; a logged intent or approval does not prove delivery, booking, payment, or receipt.
Plans, usage, and billing
The current commercial model includes a free Pilot allowance and paid Handler, Operation, and Enterprise plans procured through a sales-assisted process. Paid plans are invoiced and activated under a signed order form; in-product public card checkout is not enabled.
Pilot hard-pauses automated handling when its included conversation allowance is reached. Handler, Operation, and Enterprise use fair-use capacity with no application-level metered conversation overage product. Current prices, annual savings, taxes, workflow limits, channel and connector entitlements, and included features are shown at checkout or in an order form and form part of your purchase terms.
You authorize recurring charges for the selected billing period until cancellation takes effect. Failed or reversed payment can result in plan restriction or suspension. A null application cap does not remove provider, infrastructure, fair-use, or contract limits. On plan reduction, Chronicle may pause excess active workflows so the workspace stays within the new active-workflow entitlement.
Cancellation and refunds
You can request cancellation before the next renewal by emailing support@chronicles.systems from your account email. Cancellation prevents a future renewal once processed; it does not automatically refund the current period or erase data. Access ordinarily continues through the paid term unless the account is suspended for cause.
Refund eligibility, billing-error handling, annual commitments, capacity treatment, statutory rights, and request instructions are stated in the Refund Policy and any signed order form. An order form controls if it expressly conflicts with the public policy.
Chronicle ownership and feedback
Chronicle and its software, interfaces, documentation, and service design are owned by Chronicle or its licensors. These Terms do not transfer that ownership. If you provide feedback, you allow us to use it without restriction or payment, but not to disclose your confidential customer content as feedback.
Disclaimers and liability
To the maximum extent permitted by law, the service is provided "as is" and "as available" without implied warranties, including merchantability, fitness for a particular purpose, non-infringement, or uninterrupted operation. Nothing in these Terms excludes a warranty or right that cannot legally be excluded.
To the maximum extent permitted by law, Chronicle is not liable for indirect, incidental, special, consequential, exemplary, or lost-profit damages. Chronicle's aggregate liability arising from the service is limited to the amount you paid for the service during the 12 months before the event giving rise to the claim. This limitation does not apply where law prohibits it.
Indemnity
To the extent permitted by law, you will defend and indemnify Chronicle against third-party claims arising from your customer content, contact lists, lack of required consent, instructions, connected accounts, violation of provider rules, or unlawful use of the service. This does not cover claims caused by Chronicle's own willful misconduct where liability cannot be excluded.
Law, order forms, and changes
A signed order form can add commercial, deployment, support, data, governing-law, or dispute terms and controls if it conflicts with these public Terms. Otherwise, applicable law determines mandatory rights and the proper forum; this page does not invent a jurisdiction that has not been identified in your purchase.
We can update these Terms as the service or law changes. Material changes will be presented through an appropriate service or account notice when required. Continued use after the effective date constitutes acceptance to the extent permitted by law. Questions can be sent to support@chronicles.systems.
Questions / rights requests / billing
Reach our team directly for legal or account inquiries.