Draft — not yet reviewed by a lawyer, and not in force.
This wording was prepared to describe what the product actually does, so that a solicitor has something concrete to work from. It is not legal advice and it does not bind anybody. Do not rely on it, publish it, or send it to a client until it has been reviewed and this banner has gone.
Terms of use
What KVAi is
KVAi is a tool for agencies working in pharmaceutical and healthcare communications. You brief specialist AI agents in your own words; they read only the shared healthcare library and the documents in the client space you are working in, and return drafts with citations.
Outputs are drafts, and that is not a disclaimer
Nothing KVAi produces is medical, legal or regulatory approval, and nothing becomes final without a named person approving it. The product is built so that this is structurally true rather than a matter of policy: a completed run stops at an approval gate, and the software itself cannot mark anything final.
Where a claim in a draft has no supporting passage in the sources retrieved, it is flagged in place rather than presented as evidenced. Those flags are for you to resolve. Approving an output with an unresolved flag is your decision and your responsibility.
You remain responsible for compliance with the ABPI Code, the EFPIA Code, and any other regulatory or self-regulatory framework that applies to your work and your market.
Your content
Documents you upload, briefs you write and outputs produced for you remain yours. We claim no ownership of them and we do not use them to train models. We process them only to run the product for you, as described in the privacy notice and the data processing agreement.
You must have the right to upload what you upload. That matters here more than in most products: client documents are usually confidential and often licensed.
Accounts
Access is per person and must not be shared. Owners and admins control who has access to a workspace and to each client space. Removing somebody ends their sessions immediately; their name remains on work they approved, because that record is the point of the approval trail.
Credits
Work is paid for from a prepaid credit balance. Credits are consumed when a run completes for the first time; sending work back for changes costs nothing, and a run that fails is not charged.
For review: whether unused credits are refundable, whether they expire, and the treatment on termination are commercial terms that need deciding rather than drafting. The product currently treats credits as never expiring, and the emails say so.
Availability
We do not currently offer a service level agreement. Long-running work happens on a queue and is designed to survive a deployment; approvals and existing outputs remain readable even when new work is paused, for example when a credit balance reaches zero.
Acceptable use
You must not use KVAi to:
- produce material you intend to publish without human review;
- upload material you do not have the right to upload;
- attempt to reach another agency's workspace, client spaces or documents; or
- circumvent the approval gate, the credit system or any access control.
Ending the agreement
You may stop using KVAi at any time. An owner can request deletion of a workspace, which starts a grace period before everything in it is removed permanently — export anything you need to keep before that date, because we cannot recover it afterwards.
Not drafted here, and needed:
Limitation of liability, indemnities, warranties, governing law and jurisdiction, suspension rights, changes to these terms, and the identity of the contracting entity. Those are the clauses that decide what happens when something goes wrong, and they should be written by a solicitor rather than inferred from a codebase.