Paid Setup Service — Acknowledgment

Nothing in this acknowledgment excludes liability for Cornilius's gross negligence, willful misconduct, or breach of confidentiality obligations under the Terms of Service.

To the maximum extent permitted by law, Cornilius provides the Paid Setup Service "as is" without any warranties, express, implied, or statutory, including merchantability, fitness for a particular purpose, or non-infringement. See also Terms of Service Section 7.

Liability for Paid Setup is subject to the limitation of liability in the Terms of Service Section 8, including the aggregate cap on amounts paid for the Cornilius subscription and/or setup fees in the twelve (12) months before the claim. By accepting this acknowledgment, you agree that disputes about Setup are governed by the limitation, indemnity, and governing-law clauses in the Terms.

Cornilius does not monitor, cap, or pay customer LLM, token, or other vendor meters. Connecting tools, playbooks, or scheduled routines during Setup does not transfer billing responsibility to Cornilius.

I acknowledge that:

1. I supply the coding agent. Cornilius is the analytics memory layer. I use my own agent (Claude, Cursor, Codex, or similar) and my own accounts — not Cornilius's.
2. I pay all third-party costs — including if Cornilius installs for me. LLM and token usage on my agent accounts, Mixpanel, BigQuery, GA4, cloud, and similar bills stay mine. This includes sudden spikes, overages, retries, long context, autonomous or scheduled agent runs, playbooks or routines that run on a cadence, and any agent use after handoff. Cornilius does not monitor, cap, or pay those meters and will not reimburse unexpected spend — even if Setup connected the tools, credentials, or playbooks that trigger usage. I cannot recover third-party invoices from Cornilius; my remedy for Setup, if any, is limited as stated in Terms of Service Section 10.2.
3. I set spend limits before Setup starts. Before Setup work begins, I confirm that spend limits or budget alerts are set on billed accounts Cornilius may connect (LLM/token, cloud, analytics), where those platforms allow them, as required by Terms of Service Section 10.2.
4. My databases and analytics tools stay my risk. I will keep backups before setup. I will not claim against Cornilius for data loss, corruption, bad queries, schema issues, downtime, or other problems in systems I own or license — even if Cornilius staff configured or queried them during setup.
5. AI and MCP have residual risk. Connecting my agent to Cornilius and to AI providers can expose information I send. Cornilius will take commercially reasonable care, meaning it will: (a) use encrypted connections for integrations where the platform supports them; (b) log access for audit during Setup; (c) restrict staff access to customer systems to personnel assigned to my Setup; (d) remove Cornilius access after handoff; and (e) not train models on my data. Cornilius cannot eliminate all risk of leak, misconfiguration, or model-provider handling, and is not liable for vulnerabilities in third-party LLM providers (for example Anthropic or OpenAI) or in customer vendor platforms.
6. No results are guaranteed. Setup and the product do not promise better metrics, revenue, or "good" analyses. Agent output can be wrong. I decide what to act on.
7. Setup is a defined job, not unlimited work. Scope is defined in a signed statement of work (SOW) or formal order. If no SOW or order form defines scope, Setup includes only the default described in Terms of Service Section 10.1 (discovery, connection guidance or configuration, initial Cornilius workspace, and handoff). It is not an MVP build, not ongoing managed analytics, and not unlimited agent time. Work outside the agreed or default scope requires a written change order before Cornilius performs it.
8. Subscription is separate. Ongoing Cornilius access follows my plan, not the setup fee.
9. Access I grant is for setup only. I will revoke or rotate all Cornilius-granted credentials within forty-eight (48) hours of setup handoff confirmation (email or documented SOW sign-off). Cornilius is not liable for unauthorized access, data exposure, LLM/token charges, or other downstream costs if credentials remain active after that deadline. I am responsible for auditing logs and access after handoff.
10. Indemnification. Customer's indemnification obligations in Terms of Service Section 9 apply to Paid Setup and are incorporated by reference, including claims arising from my data, my agent, LLM/token or other third-party vendor bills, my integrations or systems, my use outside agreed Setup scope, or my failure to revoke credentials.