TKOResearch
Menu

FAQ

Practical answers before you send materials or request scope.

A diligence FAQ for buyers who need to know what TKOResearch needs, what not to send, how data handling works, and what a review does not certify.

What you receive

Concrete outputs for a specific decision.

  • Scoping checklist
  • What not to send guidance
  • NDA and data-handling expectations
  • Production access guidance
  • Report and limitation explanation

01

Common questions

What is needed to scope?

A high-level description of workflow, system type, tools, data classes, buyer decision, timeline, and desired deliverable.

What should not be sent?

Do not send secrets, credentials, regulated data, customer PII, payloads, or confidential files through the public contact form.

Is production access required?

Not always. Many reviews start with architecture, configuration, logs, transcripts, prompts, and staged access before any production access is considered.

What does TKOResearch not certify?

TKOResearch does not certify broad safety, all future versions, or systems outside the defined scope and date.

Next step

Start with the decision and the system boundary.

Request written scope