Every material conclusion keeps its source, scope, freshness, limitations and consequence attached.
ClaimWhat is being asserted?
EvidenceWhat supports or challenges it?
Applicable scopeWhich offering, route, region and terms?
ConfidenceHow strong and current is the evidence?
Practical consequenceWhat changes for this workload?
Start with the decision in front of you.
Find my options
Describe the capabilities, safeguards, regions, terms and operating conditions you need. See which offerings clear them, fail them, or still lack enough evidence.
Compare my shortlist
Focus on the differences that matter to your situation: conditions, exclusions, evidence strength, unresolved questions and useful next checks.
Illustrative record — not a provider finding
See what a qualified answer looks like.
Structured values help with comparison, but they never replace the dated source and the conditions that make a claim true.
Claim
Customer inputs are not used to train shared models.
Evidence state
Provider-stated
Scope
Example enterprise API plan, direct route, stated region.
Qualification
The public statement does not establish every retention exception or upstream processor. Contract review is still required.
Consequence
Promising enough to investigate; not sufficient alone to clear a mandatory confidentiality requirement.
What the research will not hide.
Provider statement, signed commitment and independent observation are different evidence states.
Price, route, region, plan, configuration and observation date can all change the answer.
Contradicted, stale, unassessed and unknown findings remain visible.
No opaque overall score substitutes for requirements and trade-offs.
The first release is public and account-free.
Explore the research method and an illustrative record here. Accounts, grants and the member research desk are deferred.