ooto.cxthe mcp harness
connectorsthe vaultpricingfrench datamarketplaceappsdevelopersosssign increate an account→

Subscription & Usage Terms

Version 3.1 — August 29, 2026 download the PDF

Versions
  • Version 3.1 — August 29, 2026current
  • Version 3.0 — July 10, 2026
  • Version 2.0 — July 8, 2026
  • Version 1.0 — June 1, 2026

What changed

Commercial and technical facts brought up to date. The indicative €250 and €500 amounts are removed: the terms no longer carry a price grid and refer to the pricing in force published on oto.cx. Payment provider: Mollie replaces Stancer. Added VAT by customer country, the cross-reference to the terms of sale for price revision and non-payment, and two-factor authentication as an organization requirement. Trust center moved to trust.oto.zone. Fixed the version number quoted in the body of the text.

PurposeAccessAccountUsage & AgentsSubscriptionIntellectual PropertyLiabilityDataChanges

Purpose

In short: These terms (version 3.1) govern the subscription and use of oto, an automation platform connected via MCP. By using oto, you agree to them.

These terms (version 3.1) govern access to, subscription to, and use of oto — an automation platform ("toolbox") connected to your assistant via the MCP protocol (oto.cx, mcp.oto.cx).

oto is published by Otomata, a SASU registered in Marseille (SIREN 106 974 637, intra-EU VAT FR05106974637), the "Publisher", represented by Alexis Laporte — see the legal notice.

Using the service implies full acceptance of these terms. If you do not agree, please do not use oto.

Service Access

In short: Sign-up is open; an account is required to access the service.

Sign-up to the service is open; access requires creating an account. The Publisher may suspend or revoke access in case of abuse or breach of these terms.

The Publisher reserves the right to temporarily suspend access for maintenance or updates, informing users where possible.

User Account

In short: Sign in via OAuth 2.0 / PKCE through Logto. No shared password is stored. An organization may require two-factor authentication from its members.

Sign-in is performed via OAuth 2.0 / PKCE through Logto (auth.oto.ninja, self-hosted by the Publisher). No shared password is stored on our servers.

An organization may require two-factor authentication (MFA) from its members; the second factor is then requested when any user who is a member of it signs in.

You are responsible for all activity under your account. In case of abuse, the Publisher reserves the right to suspend or delete the account without notice.

You manage your account, connectors, and subscription from manage.oto.cx. To close your account and have your data erased, email alexis@otomata.tech.

Acceptable Use & Agent Supervision

In short: Normal, lawful use. You supervise your Agents: connectors can perform binding actions, so it's up to you to require human validation.

oto is provided for normal professional and personal use. You are responsible for how you use the connected tools and the data you process with them.

Agent supervision. oto lets your agents (AI assistants) call connectors that may, depending on their configuration, perform actions with real-world effects (sending a message, writing to a third-party tool, etc.). It is your responsibility to supervise your agents and to require human validation for any binding action (contractual, financial, or affecting third parties). The Publisher does not guarantee that an agent-triggered action is always preceded by validation: that control depends on your configuration and oversight.

The following are prohibited:

  • Any action intended to disrupt, circumvent, or overload the platform's operation
  • Scraping or automated extraction of the platform itself
  • Any unlawful use, or use that infringes the rights of third parties
  • Commercial resale or redistribution of the service
  • Any use contrary to the terms of the connected third-party tools

Subscription & Billing

In short: A free tier and paid subscriptions, per organization; the pricing in force is published on oto.cx and shown at the time of order. Hands-on support (time spent) is a separate service. Reasonable use ("fair use") of third-party APIs applies.

oto is offered on a per-organization subscription model: a free tier and paid subscriptions. The subscriptions offered, their scope, the number of users included where applicable, and the pricing in force are published on oto.cx and shown on manage.oto.cx at the time of order; the prices shown on the day of subscription apply.

Prices are stated excluding tax. The amount actually charged is a tax-inclusive amount: VAT is applied according to the Customer's country (French VAT at 20 %; reverse charge for a customer in the European Union outside France holding an intra-EU VAT number; out of scope outside the Union). The details are set out in the terms of sale.

Paid subscriptions are billed by the Publisher and collected via Mollie B.V., a Dutch electronic money institution licensed and supervised by the Dutch central bank (De Nederlandsche Bank). Card details do not pass through our servers. Every payment collected produces an invoice, sent by email and downloadable from manage.oto.cx.

Fair use. The service relies on third-party APIs (data, enrichment, AI models) subject to their own quotas. Use that is clearly disproportionate to the subscription taken out may be adjusted, after notice.

Support. Any hands-on service (setup, training, custom development — billed by time spent) is separate from the subscription and covered by its own quote or purchase order.

The Publisher reserves the right to change subscriptions and pricing, with prior notice and effect from the next billing cycle; the terms and the notice period are set out in the terms of sale.

The sale conditions for paid subscriptions (ordering, VAT, payment, invoicing, non-payment, term, renewal, termination) are detailed in the terms of sale, accepted at purchase together with the DPA.

Intellectual Property

In short: The oto platform remains the Publisher's property. Your data and content remain yours.

All elements of oto (unpublished source code, interfaces, text, logos, design) are protected by copyright and remain the exclusive property of the Publisher, unless otherwise stated. Some of oto's building blocks are released as open source under their respective licenses.

The data, content, and credentials you process or connect via oto remain your property. The Publisher claims no rights over them. Unauthorized reproduction or redistribution of the platform's unpublished elements is prohibited.

Limitation of Liability

In short: oto is under active deployment. The Publisher's liability for direct damages is capped at amounts you paid over the last 12 months; indirect damages are excluded; certain statutory exceptions remain uncapped.

oto is under active deployment. The Publisher uses reasonable efforts to ensure the availability and security of the service, without however guaranteeing uninterrupted availability.

Cap. To the extent permitted by law, the Publisher's total liability for direct damages is capped at the amounts actually paid by the Customer for the subscription over the twelve (12) rolling months preceding the triggering event (this cap is therefore nil for the free tier).

Exclusion. The Publisher shall not be liable for indirect damages (loss of business, revenue, data, customers, reputational harm, etc.).

Exceptions. These limitations do not apply and liability remains uncapped in the event of gross negligence or willful misconduct, personal injury, breach of a confidentiality obligation, or infringement of third-party intellectual property rights.

The service relies on third-party providers and services (notably Scaleway, Logto, Mollie, as well as API and AI-model vendors — the list of sub-processors is set out in the DPA). The Publisher is not responsible for the content or practices of these external services.

Personal Data & Security

In short: How your data is processed is described in the privacy policy and the trust center.

The processing of your personal data is detailed in our privacy policy. The allocation of responsibilities between the Publisher (processor) and the Customer (controller) is set out in a data processing agreement (DPA).

Your secrets and credentials for third-party tools are encrypted at rest (AES-256-GCM), isolated per user and partitioned per organization; the master key is kept outside the database. Details of our security measures are published on trust.oto.zone.

Versions & Changes

In short: These terms are versioned and archived. On each new version, your acceptance may be requested again. Past versions remain available.

These terms are versioned: the current version is shown at the top of the page, and previous versions remain accessible at a stable URL (e.g. /terms/v1.0), so the exact text in force on a given date can be retrieved.

The Publisher may update these terms. In case of a material change, your acceptance of the new version may be requested again at your next sign-in or subscription. A summary of changes is shown in the version changelog.

Applicable law: These terms are governed by French law. In case of dispute, the parties agree to seek an amicable solution before legal action. Failing that, the courts of Marseille, France shall have jurisdiction.

Legal NoticePrivacy PolicyTerms of SaleData Processing Agreement (DPA)
ooto.cx
otomata ecosystem
↗otomata.tech the studio↗agent.otomata.tech the agent
links
alexis@otomata.techgithubabout usdevelopersopen sourcesecuritylegal noticeprivacyterms of useterms of saledpa
oto.cx · otomata sasu · mmxxvihandmade, in marseille.open source · licence mit