Vendor checklist
A printable question set covering custody, models, retrieval, agents, evidence, security, recovery and exit.
Open and print →Procurement
Make the control boundary quotable.
A comparable request for proposal separates the workload, custody, acceptance, service, evidence and exit requirements. “Private,” “Swiss” or “sovereign” alone is not a specification.
Procurement sequence
- Define the decision and workload Named users, tasks, exclusions, representative material and required human review.
- Resolve the custody map Data, processing, keys, administrators, support, logs, backup and exit locations.
- Freeze acceptance Quality, citations, refusals, leakage, latency, concurrency, recovery and operational criteria.
- Request comparable evidence Exact configuration, sources, test method, dependencies, limitations and negative findings.
- Contract responsibilities and exit Owners, service boundary, change, incident, audit support, portability, return and deletion.
Public due-diligence set
Trust Centre
Current controls, shared responsibilities, regulatory orientation and explicit non-claims.
Inspect the boundary →Evidence Room
Public registries, calculations, methods and browser-local decision instruments.
Inspect evidence →Engagement ladder
How a review, pilot, production delivery, operation and exit are separately accepted.
Compare stages →Documents available only when relevant
Project-specific confidentiality, service, data-processing, security, support, acceptance and exit terms are shared progressively after fit and scope are established. This protects both parties and avoids presenting draft language as a universal commitment.
Boundary: this page and its checklists are procurement guidance, not an offer, contract, legal opinion, certification, audit report or regulatory assurance.
Red flags in any private-AI proposal
- benchmark numbers without the exact runtime, load, quality set and raw result
- “Swiss-hosted” without administrators, keys, backup, support and exit locations
- agent automation without named tool authority, budgets, human gates and stop controls
- silent model or licence upgrades
- an SLA without definitions, exclusions, dependencies and measurement
- no reusable evidence packet or tested exit path