Developer & API Terms of Service

Effective date: August 2, 2026

These terms cover the Casola API. If you are using the Casola consumer app rather than building on the API, the Terms of Service apply to you instead.

1. Agreement and Eligibility

These Developer & API Terms of Service (“Terms”) govern your access to and use of the Casola API and related services (the “Service”), provided by Casola. By creating an account, generating an API key, or using the Service, you agree to these Terms. You represent that you are a business or developer acting for purposes within your trade or profession, that you are authorized to bind the entity you represent, and that you and your authorized users are at least 18. These Terms incorporate the Acceptable Use Policy (“AUP”) and the Privacy Policy. Where you process personal data of your End Users through the Service, a Data Processing Addendum (“DPA”) is available on request and applies once signed by both parties.

2. Definitions

• Customer / you: the entity that has agreed to these Terms.
• End User: any individual who interacts with the Customer’s product or with avatars generated through the Service via the Customer’s product.
• Inputs: prompts, messages, reference media, and parameters submitted to the Service.
• Outputs: the AI-generated text, voice, images, or animated-avatar content returned.

3. The Service

The Service is an API that generates interactive AI avatar and companion content from your Inputs. It is a building block, not a finished consumer product. We do not provide the consumer interface, the End-User relationship, billing of End Users, or consumer disclosures. Those are yours.

Casola also operates its own consumer service on the same underlying technology, under a separate agreement with the people who use it. That service is ours to run, and the way we handle disclosure, age assurance, recording, and consumer protection there says nothing about what you must do in your own product. Your obligations under Section 5 are set by the law that applies to you as the operator, not by how our consumer app happens to be configured.

4. License

Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable license to access the Service and integrate the Outputs into your product. You may not copy, resell raw API access, reverse-engineer, scrape, or use the Service to build a competing generation model, and you may not disable, bypass, or probe the safety controls embedded in the Service.

5. Customer Obligations (Consumer-Facing Responsibilities)

Because you operate the End-User experience, you are responsible for the following, and you represent that you will implement and maintain them:

• Your own End-User terms, privacy policy, and AUP binding your End Users to rules at least as strict as our AUP, with the right to suspend and report End Users.
• AI disclosure. A clear and conspicuous notice to End Users that they are interacting with an AI system, and any applicable extended-session reminders. Our AI Disclosure page sets out what we do on our own surfaces and what we suggest for yours; it is guidance, not a substitute for your own legal advice. Applicable law includes the EU’s AI transparency rules and a growing set of US state companion-chatbot laws.
• Crisis and self-harm protocol. In-product detection and referral of at-risk End Users to crisis resources (e.g., 988 in the US), and prevention of self-harm-encouraging content in your deployment.
• End-User age assurance. Verify the age/eligibility of your End Users with measures appropriate to the risk. By default you must exclude End Users under 18; if you lawfully serve minors, you must notify us first and implement minor-specific safeguards and comply with applicable child-protection law. You may not rely on us to age-gate your End Users.
• Recording disclosure. Session capture under Section 10 is off unless you turn it on; where you turn it on, telling your End Users and collecting any consent their jurisdiction requires is yours to do. Several US states require all-party consent to record a conversation, and voice recordings are regulated as biometric data in some places.
• Consumer protection. Truthful marketing (you must not market the avatars as a substitute for professional care, therapy, or human relationships), plus your End-User billing, consents, and refunds.
• Lawful deployment. Your use case, your jurisdictions, and your End Users’ conduct.

You are solely responsible for your product and your End Users. Nothing we provide relieves you of operator/controller duties that attach to you as the party making a companion experience available to consumers.

6. Our Retained Safety Obligations

Because we generate and transmit content, we retain obligations that we do not delegate to you and that you may not interfere with:

• We screen submitted script content for prohibited content and block what we match, and we preserve evidence and report suspected child sexual abuse material to NCMEC / authorities as required by law, independent of you. Section 5 of the AUP sets out what that screening does and does not do today, including that it does not run on live conversation. Do not design around a screening layer we have not built.
• We maintain the model-level guardrails described in the AUP and may refuse, filter, or log generations to meet our legal and safety obligations.
• We may act as an independent controller for the limited personal data we process for these safety, security, and legal-compliance purposes (see our Privacy Policy).

7. Account, Keys, and Verification

You are responsible for keeping API keys confidential and for all use under your account and keys. We may require identity/business verification (KYC) before issuing or maintaining access and may re-verify at any time. Notify us promptly at support@casola.ai of any compromise.

8. Acceptable Use

Your use of the Service, and your End Users’ use of your product, is governed by the Acceptable Use Policy, incorporated here. You must flow the AUP’s prohibitions down to your End Users and enforce them.

9. Fees and Billing

Usage is billed based on consumption (e.g., tokens, generation-seconds, requests) at the rates on our pricing page or your order form. Fees are exclusive of taxes. Disputed amounts must be raised within 30 days. We may change pricing on 30 days’ notice. There is no subscription or recurring-plan component to API access today; if we introduce one, its renewal and cancellation terms will be set out here before it takes effect.

10. Session Capture

Capture is off by default. A live session records nothing unless you ask for it. To turn capture on for a session, pass recording: true when you create it. The switch is per session, not per account, so you decide session by session.

recording: true is refused (403 recording_not_allowed) on the anonymous demo tier, on zero-data-retention workspaces, and where recording is not enabled for your account. A refusal means the session runs without capture, not that it is unavailable.

observability is the deprecated predecessor of recording and still works: observability: true turns capture on exactly as recording: true does, and observability: false both keeps capture off and suppresses that session’s session-tagged logs. Where both are sent, recording decides capture. Capture and session-tagged logs are separate things — turning capture off does not by itself silence the logs.

While capture is on, the following applies:

• What is captured. The End User’s microphone audio for each conversational turn, video clips of the avatar’s replies, and a whole-session recording. Logs tagged with the session id are written independently of capture and are suppressed by observability: false.
• What it is for. Your debugging and support, and our providing the Service to you. We process this material as your processor, on your instructions.
• What it is never used for. We do not use captures from your sessions to train, tune, or evaluate any Casola model, and we do not use them to improve the Service for anyone else. That is the default on every tier and plan, and it changes only where you instruct us otherwise in a separate agreement signed by both of us.
• Retention. Captures are deleted 30 days after the session, automatically. A DPA may set a different period.
• Deletion on request. Ask at privacy@casola.ai to have a session’s capture deleted sooner, or all of them.
• Your disclosure duty. See Section 5. Capture records an identifiable person’s voice; where you turn it on, telling them is your job, not ours.

Safety and legal-compliance records under Section 6 are outside this section, as described in the Privacy Policy.

11. Intellectual Property

We and our licensors own the Service, models, and platform. As between you and us, and subject to these Terms and the model licenses, you own your application and may use the Outputs your integration generates. You grant us the limited rights in your Inputs and Outputs needed to operate the Service, maintain safety, and comply with law (see our Privacy Policy for personal data).

12. Confidentiality

Each party will protect the other’s non-public information disclosed under these Terms and use it only to perform under these Terms, excluding information that is public, independently developed, or rightfully received from another source.

13. Data Protection

Where we process personal data of your End Users on your behalf, you are the controller and we are the processor. Such processing is governed by our Data Processing Addendum (“DPA”), which we will execute on request. Our handling of your own (business) personal data is described in the Privacy Policy. The third parties we use are listed at Subprocessors.

14. Warranties and Disclaimers

The Service is provided “as is” and “as available” without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that Outputs are accurate, appropriate, or lawful in your jurisdiction, or that the Service will be uninterrupted or error-free. You are responsible for evaluating Outputs before using them.

15. Indemnification

You will indemnify and hold harmless Casola and its affiliates from any claim, damage, or expense (including reasonable legal fees) arising from your product, your deployment, your marketing, your End Users, or your breach of these Terms or the AUP.

16. Limitation of Liability

To the maximum extent permitted by law, neither party will be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or lost profits, revenue, or data. Our total aggregate liability will not exceed the fees you paid us in the 12 months before the claim. Carve-outs for your indemnity obligations, breaches of the AUP, and liabilities that cannot be limited by law.

17. Suspension and Termination

We may suspend or terminate access for breach of these Terms or the AUP, security risk, non-payment, or legal requirement. For severe violations (including the absolute prohibitions in the AUP) suspension may be immediate and without notice. On termination, your right to use the Service ends; data is handled per the Privacy Policy and any DPA you have executed with us, except records we must retain for legal, safety, or evidentiary purposes.

18. Governing Law and Disputes

These Terms are governed by the laws of the State of California, without regard to conflict-of-law rules. The parties will attempt to resolve disputes informally via legal@casola.ai for 30 days, then by binding arbitration administered by JAMS under its Comprehensive Arbitration Rules, seated in Santa Clara County, California, except that either party may seek injunctive relief in court.

19. Changes; Notices; Contact

We may update these Terms; we will notify you of material changes before they take effect. Notices to you go to your account contact. Questions: legal@casola.ai. Safety: safety@casola.ai. Registered address: Casola, 440 N. Wolfe Rd, Sunnyvale, CA 94085.