Terms of Service
These Terms of Service describe the framework under which Armada Inc. and Armada S.A. de C.V. ("Armada") deliver Genesis, our Micro-Sovereign AI system, to a client ("Client"). They are a summary of how we work. They are not the contract. Each engagement is governed by a written agreement signed by both parties: a Discovery agreement, then a statement of work, then, where applicable, a managed operations agreement. Where these terms differ from a signed agreement, the signed agreement governs.
1 · The phases
An engagement runs in gates. Each gate is a decision point, and the next phase begins only if the previous one produced what it promised.
- Discovery. Four to six weeks with the people who own the process. The deliverable is one process, the number we will chase, what a pass means, and the priced project. The Client keeps that document whatever it decides next.
- Phase 0. A defined period of live work on the Client's own hardware, purchased in the Client's name, measured against the number agreed in Discovery. If it passes, the build is quoted against that number. If it does not, the Client keeps the hardware and the documents.
- The build. Install, train, measure, expand. Scope, timetable and acceptance are set out in the statement of work.
- Managed operations. Armada keeps the system updated, watched and running under a separate retainer, for as long as the Client wants it.
2 · What the Client owns
The Client owns the hardware, its own data, the outputs produced from its own data, and any configuration, prompts, workflows and documents created specifically for it and identified as Client deliverables in the statement of work. Ownership of the hardware passes on payment, in the Client's name, from day one.
3 · Hardware, at cost
Armada purchases hardware in the Client's name and passes it through at cost. Armada does not apply a margin to hardware, at any phase, ever. Manufacturer warranties pass to the Client. Armada is paid for the consulting, the build, the operation of the system, and the seats on Bridge, as set out in the signed agreement.
4 · Data, and the wall around it
Genesis runs on hardware inside the Client's premises. Client data, prompts, documents and model outputs are processed on that hardware and are not transmitted to Armada, to any model provider, or to any other third party, except where the Client explicitly instructs a connection to a system it has chosen.
Armada does not use Client data to train models for any other client. Armada personnel access Client systems only with the Client's authorisation, under the confidentiality and security terms of the signed agreement, and each access is recorded.
Where Armada processes personal data on the Client's behalf, it does so as a processor on the Client's documented instructions, under the data processing terms of the signed agreement.
5 · The record, and what it is not
Every action taken in the system, by a person or by an agent, is sealed and dated in a record the Client's auditor can verify independently, without Armada. The record is designed to remain lawfully erasable, because the law sometimes requires erasure.
The seal is evidence of what happened and when. It does not make any document fiscally, legally or contractually valid. Validity is determined by the competent authority and by applicable law, not by Armada and not by the record.
6 · Agents, and the person at the gate
Agents execute defined steps in a defined process. A person authorised by the Client remains at the gate for every decision the statement of work identifies as material. An agent does not decide alone, and an agent does not represent itself as a human being.
The Client remains responsible for its own operational, regulatory and contractual obligations, including the accuracy of records it files with any authority. Armada builds the system that does the work; it does not assume the Client's obligations.
7 · What Armada keeps
Armada retains all rights in ARC, Bridge, the agent framework, its methods, tools, templates and know-how, including improvements to them, and grants the Client a licence to use them for the Client's own internal business for the term of the agreement.
Process knowledge, meaning what Armada learns about how to build a class of agent, stays with Armada. Client data never crosses that boundary. The distinction is written into the signed agreement.
8 · Service levels and dependencies
Availability targets, response times, maintenance windows and escalation paths are set out in the managed operations agreement. Delivery depends on the Client providing site access, power, network, system credentials, named process owners and timely decisions. Where a dependency is late, timetables move by agreement.
9 · Fees, term and termination
Fees, currency, invoicing and payment terms are stated in each signed agreement. No price is quoted on this website; every engagement is sized to the Client after Discovery.
Either party may terminate for material breach that is not cured within the period stated in the agreement. On termination the Client keeps its hardware, its data and its Client deliverables; Armada removes its software and its access. Provisions that by their nature survive, including confidentiality, ownership and liability, survive termination.
10 · Warranties, liability and law
Armada warrants that it will perform with the skill and care of a competent professional in its field, and in accordance with the statement of work. Except as expressly stated in the signed agreement, and to the fullest extent the law allows, Armada gives no other warranty, express or implied.
Liability is capped and allocated as set out in the signed agreement. Neither party is liable for indirect or consequential loss. Nothing excludes liability that cannot be excluded by law.
Governing law, jurisdiction and dispute resolution are stated in each signed agreement. In the absence of a signed agreement, section 9 of the Terms of Use applies.
Questions about these terms: daniel@armadatech.ai · See also the Terms of Use and the privacy notice.