Qualified Piper AI agent: what the published documents say about AI disclosure
Everything below comes from Qualified’s own public documents, quoted with the version date of each one. It is the public half of a Vendor Claims Check: what is claimed, and what is left unsaid. It does not tell you what your own deployment is currently doing, because that depends on settings you control.
What was read, and when
| Document | Part | Version |
|---|---|---|
| Terms of Service | numbered sections 1 to 12 | effective 1 September 2022 |
| Privacy Policy | AI section | effective 25 September 2025 |
| Data Processing Addendum | service description | read 9 September 2026 |
| Trust centre | listing | read 9 September 2026 |
1 September 2022
The oldest document this page quotes
9 September 2026
The day the documents and the product were read
The day you are asked
A questionnaire, a renewal, or diligence
The first two dates are fixed and recorded. The third has not happened yet. When it does, the only thing that answers it is a record made at the second date, because by then the first may have been replaced, and the vendor’s page shows only the current one.
What the documents say
What the contract says about AI
The Terms of Service carry an effective date of 1 September 2022. I did not find, in sections 1 to 12, any reference to artificial intelligence, machine learning or chatbots. A subprocessor table printed below section 12 on the same page is outside this finding and is read separately.
The product being sold today is an AI agent. The agreement predates it.
Where AI is addressed instead
The Privacy Policy, effective 25 September 2025, addresses AI at some length, but as a data processing matter: generating content using AI, that information is not used to train generalised models, and an opt-out from profiling.
The Data Processing Addendum describes the service as a conversational platform using live chat, voice calls and chatbots.
1 September 2022
Terms of Service effective. No AI in sections 1 to 12
25 September 2025
Privacy Policy effective. Addresses AI as a data matter
October 2025
AI SDR penetration test, listed in the trust centre
9 September 2026
Documents read for this page
21 September 2026
Subprocessor table read again, finding 05 added
The documents above that address AI are dated 2025. The numbered terms, which set out who owes what to whom, are dated 2022.
Who is responsible for telling the visitor
No statement was found, in any of the documents listed above, of who is responsible for telling a visitor that they are interacting with an AI agent.
That is a statement about the public documents, not about the product or the company. Material behind an access request was not read.
What the trust centre lists
The trust centre lists SOC 2 Type II, GDPR and CCPA, together with an AI SDR penetration test dated October 2025.
No reference to the EU AI Act was found.
What the subprocessor list names
The subprocessor table printed below section 12 of the Terms of Service names five providers under generative AI: Azure OpenAI Service, OpenAI, Amazon Bedrock (Anthropic) and Google Cloud AI, each described as “Generative AI”, and Tavus, described as “Generative AI Avatar”.
So the documents do name generative AI, an avatar provider among it, in the list of who processes the data. The same set of documents does not say who tells the visitor.
Added to this page on 21 September 2026. The finding was read on 13 September 2026 and the table was read again on 21 September 2026, before this card was added. The five entries and the effective date of 1 September 2022 were unchanged on both readings.
Qualified’s right of reply
Qualified was notified twice, at legal@qualified.com, each time with five working days to comment before publication. Any comment received is published here in full and unedited.
Findings 01 to 04 were sent on 9 September 2026. No comment had been received at the time of publication on 19 September 2026.
Finding 05 was sent separately on 14 September 2026, on the same terms, with its own window closing on 21 September 2026 at 18:00 CEST. No comment had been received when it was added to this page on 21 September 2026.
Both are statements about correspondence, not about the company.
What this page does not tell you
It does not say whether Qualified is compliant, and it does not say whether you are. It does not cover material behind an access request, which was not read. Documentation changes, so this is a point in time: the version dates above are the whole claim. And it says nothing about your instance, which is usually the part that matters.
The part a public page cannot cover
A full Vendor Claims Check adds what this page cannot: the vendor’s default behaviour observed on a fresh trial account, and, if you give me the address, your own deployment observed alongside it. You end up holding a dated record of both, which the vendor’s documentation cannot give you later.
490 EUR for one vendor, five working days. Email the vendor name and you get an invoice or a card link the same day.
Email me the vendor nameNot an audit and not a certification. I am not an accredited body and do not describe myself as one. This is an independent reading of public documents. I take no fee from any vendor named on this page, and no work from them that a buyer could rely on. Nothing here is legal advice.