Privacy

Amvio is used by two groups of people, and they are treated differently. Customers are the companies that install Amvio in their product and sign in to this dashboard. End users are the people who talk to Amvio inside a customer's product.

For end-user data, the customer is the controller and Amvio is the processor: it is their product, their relationship, and their instructions. Amvio does not use one customer's data to answer anyone else's questions.

Your name and email address, the organisation and workspace you create, everyone you invite, and everything you configure — what your product does, who uses it, how far Amvio may act on its own, and where handoffs go.

Also whatever you point it at as knowledge: documentation pages it crawls, files you upload, and text you paste.

Conversations, in full — every message either side sent, and what Amvio did about them.

Identity, but only when the customer supplies it. Amvio has no way to know who anyone is unless the customer's own servers tell it, via a signed call carrying their account and user identifiers and optionally a name and email. Without that call, sessions are anonymous and stay that way.

Screen recordings and audio, where the customer has enabled them. Amvio can capture a session's screen and voice to understand what someone is struggling with. This is off unless a customer turns it on, and it is the customer's responsibility to tell their users it is happening and to obtain any consent their jurisdiction requires.

What Amvio infers from all of the above: which pages people get stuck on, which questions the documentation does not answer, sentiment, and signals that an account is at risk.

Amvio runs on third-party infrastructure and sends data to it in the course of working: a database and authentication provider, a hosting provider, a web-crawling service for indexing documentation, and large language model providers, which receive conversation content and relevant knowledge in order to generate a reply.

Amvio does not sell data, and does not share it with anyone outside the providers needed to deliver the service.

Conversations, memory and derived signals persist for as long as the workspace exists — durable memory across sessions is what the product is for, so this is not incidental retention.

Deleting an account removes its profile and its membership of every organisation.

End users should contact the company whose product they were using; that company controls the data and can act on it. Customers can contact Amvio directly.