Your contract and your obligations

Selling Manivox means accepting two documents, the Terms of Use and the data processing agreement, and passing their duties on to your clients. This chapter is the plain-language version. The contracts prevail.

Your client is the data controller: it decides why calls are handled.
You are its processor: you design and run the agent for it.
Manivox is your sub-processor: it provides the infrastructure.
Your own agents, such as your reception or sales line, make you the controller and Manivox your direct processor.
The account an agent sits in, yours or a client’s, decides which case applies.

What you sign, and the brand you choose

Accepting the Terms of Use also accepts the data processing agreement. A signed confirmation copy can be generated from the Console at any time.
Manivox brand: you sell under the Manivox brand, with a licence to use it.
White label: you sell under your own brand. In the Console and the client portal, only the logo changes; the portal stays on manivox.ai.
For an interface fully under your own name and domain, build your own on the Manivox API.
Switching between the two takes 60 days’ notice.

The AI Act: who is the provider

Manivox brand: Manivox is the provider of the AI system; you and your client are deployers.
White label: you become the provider, because the system is sold under your name. Manivox gives you the information you need about its capabilities and limits.
In both cases, the greeting of every agent must say it is an AI. Setting it up is your job.
Machine-readable marking of the synthetic voice is Manivox’s job, within what telephony allows. Never switch it off.

What you pass on to each client

A contract with data protection terms equivalent to the ones you accepted.
The list of further sub-processors. Clients who use the client portal see it there; for the others, put it in your contract.
Notice that transcripts and recordings exist, and that you can access their portal with “view as account”.
The rules on recording calls in their country, and what to tell callers.
Any notice you receive from Manivox about a change of further sub-processor.

Before an agent goes live

Health or other sensitive data: flag the agent to Manivox, shorten the retention, keep the self-hosted language model, and never paste such data into Copilot.
Your own tools (your own language model, a web service, an MCP server, an external knowledge base): declare each new third party in the Console, and have your own data processing agreement with it.
Outbound prospecting: tick the consent attestation before each campaign, and keep the proof of every consent yourself.
The greeting says it is an AI, and the recording notice fits the country.

Where the data goes

In France, on infrastructure Manifone owns: language models, main voice engine, knowledge base, databases, telephony, client portal.
Speech recognition: a US company, processing in the EU, storing nothing.
Backup voice engine: used only during an incident on the main one, and it receives only the text of the agent’s replies, never the caller’s voice.
App connectors: a US integration platform with no EU hosting. No data goes there unless you set up a connector.
Copilot: an EU endpoint, and only what your team submits while building. Never live call data.

What Manivox commits to

Call data is never used to train AI models. No voice biometrics, no emotion recognition, no voice cloning.
A data breach is notified to you within 48 hours, in phases, so your client can meet its own 72-hour deadline.
99.5% monthly availability. Support picks up a ticket within 1, 4 or 8 hours depending on severity, counted in French working hours (Monday to Friday, 9:00 to 18:00).
Recordings are deleted after 7 days and transcripts after 365 days by default, and everything is deleted or returned within 30 days after the contract ends.