This document is not yet in force and binds no one. The passages highlighted in yellow are gaps the company still has to fill, including the liability cap, which is the most critical clause and the one that most depends on a lawyer.
Terms of Service
These Terms describe what Appilots delivers, what the Customer configures, and where each side’s responsibility lies. They were written from how the product actually works: the billing model, the agent architecture and the integrations that exist today.
1. Acceptance
These Terms govern use of Appilots, operated by «legal entity name», company number «no.» (“Appilots”, “we”). By creating an account or using the service, you (the “Customer”) agree to them. If you accept on behalf of a legal entity, you represent that you have authority to bind it.
2. What Appilots does, and what that implies
Appilots provides an AI agent that operates inside the Customer’s application. The Customer installs our SDK, declares which screens and actions the agent may reach, and the agent then interprets end-user requests and performs real actions in that application: navigating, filling forms, pressing buttons.
This is not a chatbot that returns text. The agent acts. The three sections that follow exist because of that.
3. The Customer’s control over what the agent can do
The Customer defines the agent’s scope: which screens exist, which actions are permitted, which require explicit end-user confirmation before running, and the spending cap per project.
That configuration is the Customer’s sole responsibility. Appilots has no way of knowing which actions in the Customer’s application are sensitive, irreversible or financially significant. It is for the Customer to mark as requiring confirmation every action whose improper triggering would cause harm, including, without limitation, payments, transfers, deletions, sends and contractual changes.
«Recommendation: keep an explicit list in the product of the categories the Customer must review at integration time, and require acceptance of it during onboarding.»
4. Probabilistic nature and limits of liability
Language models are probabilistic. They make mistakes, misread intent and can produce incorrect results even when correctly configured. That is a characteristic of the technology, not a defect of the service.
The Customer acknowledges that:
- the agent may misinterpret an end user’s request;
- the agent may perform an action other than the one intended;
- confirmation and recovery mechanisms reduce but do not eliminate that possibility;
- it is for the Customer to test the agent’s behaviour in its application before releasing it to end users, and to keep confirmation controls proportionate to the risk of each action.
Appilots is not liable for the consequences of actions performed by the agent inside the Customer’s application, except where they result from a proven failure of our own infrastructure.
«The central clause and the one that most needs a lawyer. In Brazil, limitation of liability has restricted effect, especially where there is a consumer relationship at the end of the chain. Set a cap (usually the amount paid over the last 12 months) and check enforceability.»
5. AI providers
Conversation content is sent to external model providers (OpenAI, Anthropic or compatible), in two modes:
- Own key (BYOK). The Customer configures its own key. The relationship with that provider is the Customer’s, under that provider’s terms, and Appilots is not responsible for that provider’s availability, pricing or policy.
- Managed mode. Appilots provides model access and passes the cost through according to the plan. We may change which model is used by default, provided equivalent quality is maintained, giving «notice period» notice.
An outage or policy change at an external provider may affect the service and is outside our control.
6. Plans, billing and refunds
Billing is per completed mission, according to the plan, in US dollars (USD), processed by Stripe. A mission is counted when it completes successfully, per the criterion described in the product documentation.
- Subscriptions are charged at the start of each cycle; per-mission overage is measured and charged according to usage in the period.
- Plan changes take effect from the following cycle, unless stated otherwise at the time of purchase.
- Cancellation can be done at any time from the billing portal and takes effect at the end of the current cycle. There is no pro-rata refund of the period already paid, except where the law requires one.
- Accounts in arrears may have new runs blocked after «N» days of non-payment, with prior warning.
- Applicable taxes and currency conversion fees are borne by the Customer.
«Check the right of withdrawal under art. 49 of the Brazilian Consumer Code if there are individual (non-business) customers. And confirm the non-payment blocking period against what the code actually does.»
7. Acceptable use
The Customer may not use Appilots to:
- violate applicable law or third-party rights;
- operate an application whose purpose is fraud, deception or harm;
- circumvent technical limits, quotas or billing mechanisms;
- run load tests, scans or abusive automation without prior written authorisation;
- resell or present the service as its own product, absent a specific agreement;
- submit specially protected categories of data (health, biometrics, racial origin, religious belief, data of children and adolescents) without a specific contract providing for that processing.
We may suspend an account that breaches this section, with notice where possible and immediately where there is risk to third parties or to the integrity of the service.
8. The Customer’s responsibilities towards its own users
The Customer is the controller of its end users’ data and is responsible for:
- informing its users that an AI agent operates in the application;
- obtaining the necessary legal bases, including for sending content to AI providers abroad;
- reflecting in its own privacy policy what our Privacy Policy states;
- handling data subject requests: Appilots assists, but acts under instruction.
9. Intellectual property
Appilots retains all rights in the platform, SDK, documentation and brand. The Customer retains all rights in its application, its data and the content that passes through.
We grant the Customer a non-exclusive, non-transferable and revocable licence to use the SDK for the term of the contract. Publicly distributed packages are governed by the licence stated in the repository.
We do not use Customer data to train models of our own.
10. Availability
We use reasonable efforts to keep the service available, but we offer no SLA on self-service plans. Scheduled maintenance will be announced where possible.
«Do not promise an availability figure until there is measurement and an operational commitment behind it. Infrastructure alarms exist today, but there is no defined SLA and no service credit for downtime. If enterprise is sold with an SLA, that becomes a separate contractual annex.»
11. Term, termination and data return
Either party may terminate at any time. We may terminate immediately in the event of a breach of these Terms, prolonged non-payment or a legal requirement.
On termination, the Customer has «period» to export its data. After that period, data is deleted in line with the retention policy described in our Privacy Policy, save for what the law requires us to keep.
12. Changes to these Terms
Material changes will be announced by email «notice period» in advance. Continued use after they take effect constitutes acceptance. If the Customer disagrees, it may terminate before they come into force.
13. Governing law and jurisdiction
These Terms are governed by Brazilian law. The courts of «city/state» are chosen, to the exclusion of any other.
«If there are customers outside Brazil, consider arbitration or an alternative forum.»
14. Contact
«email» · «address»
Companion document: Privacy Policy