Skip to content

Trust & governance

Built for regulated use. Honest about what is not certified.

ClinDaddy is built to 21 CFR Part 11 and GxP standards, with CDISC conformance, deterministic execution, independent QC and explicit human approval. No third-party certification or audit is claimed.

01 · Built for regulated use

Designed to the controls a regulated submission expects.

ClinDaddy is built to 21 CFR Part 11 and GxP standards, with the controls that posture depends on: audit trail, e-signatures, role-based access and versioning.

Study data is handled under CDISC conventions at design time — CDASH-aligned field identifiers and codelists — so the study starts close to the standards its submission will need.

Validation documentation is available on request under NDA. We do not claim a third-party certification or audit that has not taken place.

  • Audit trail, e-signatures, role-based access and versioning
  • CDASH-aligned design; SDTM, ADaM and Define-XML downstream
  • Validation documentation available under NDA

21 CFR Part 11 · GxP · CDISC

  1. 0121 CFR Part 11Audit trail, e-signatures, access control, versioning.
  2. 02GxPValidated development and change control.
  3. 03CDISCCDASH at design; SDTM, ADaM and Define-XML downstream.
  4. 04Human approvalExplicit, attributable sign-off.

02 · Deterministic execution

The model drafts. The engine executes.

Generative AI assists with interpretation and specification generation — the parts of the work that involve reading and structuring language.

Deterministic engines execute those specifications. The AI does not fabricate final clinical numbers.

An interpretation can be reviewed, corrected and re-run. A number produced by a language model can only be trusted or distrusted.

  • AI output is always a reviewable artifact, never a final value
  • Deterministic processing is repeatable and produces the same result
  • Specifications are the boundary between interpretation and execution

AI → Specification → Deterministic engine → Clinical output

  1. 01AIReads and interprets language.
  2. 02SpecificationA reviewable, editable artifact.
  3. 03Deterministic engineExecutes the approved specification.
  4. 04Clinical outputProduced by defined processing.

03 · Independent QC

Production and QC are separated on purpose.

Production computation and QC computation are intentionally separated.

The goal is to avoid the failure mode where QC reproduces the same implementation and agrees with the same bug — a second run of the same code is not a second opinion.

Independent QC re-implements the computation, then compares results. Cross-artifact QC extends that check across datasets, specifications and outputs.

  • QC re-implements the computation rather than re-running it
  • Downloadable SAS, R and SQL QC code at each step
  • Differences are surfaced for review, never silently reconciled

Source data → Production and independent QC → Compare → Review

Source data

Collected clinical data

Production

Executes the approved specification

Independent QC

Re-implements the computation

Compare

Differences surfaced, never silently reconciled

Review

A person resolves what the comparison found

04 · AI governance

Models never make the final decision.

AI drafts; a qualified person reviews and approves. Every AI suggestion is logged in the audit trail and remains editable.

The model layer is separable from the pipeline, so the provider behind a given pass can change without redesigning the workflow.

Sponsor data is handled under the terms set out during evaluation; data-handling and hosting details are shared under NDA.

  • Models never make final decisions
  • Every AI output is reviewable and logged
  • Provider-swappable model layer

AI draft → Human review → Correction → Approval → Audit log

  1. 01AI draftEditable, reviewable, logged.
  2. 02Human reviewA qualified person reads and corrects.
  3. 03ApprovalA named person signs off.
  4. 04Audit logAppend-only record of the decision.

Human approval

A person presses approve. The system records who, when and why.

Production and independent QC converge on a reconciliation step. A named reviewer sees both results, resolves the difference, and only then is the output submission-ready.
  • Approval is an explicit act by a named person
  • Every AI proposal and reviewer edit is written to the audit trail
  • QC differences are surfaced for review, never reconciled silently
Illustration of a reviewer at a console comparing production data with independent QC, then pressing an approve control for a regulatory submission.
Illustration. Production and independent QC reconcile; approval is the human act that releases the output.

Validation

Documentation is available under NDA.

Validation documentation, security details and hosting controls are shared during evaluation rather than summarized as a marketing claim.

Tell us what your quality or procurement process needs and we will route the request to the right person.

Request validation documentation

Please do not send confidential study data through the website.

  • NVIDIA Inception Program member

Programs

ClinDaddy is a member of the NVIDIA Inception program and AWS Activate.

Limits

What we do not claim.

A trust page is only worth reading if it also states its limits. These are ours.

  • 01

    We do not claim third-party security certifications or regulatory approval. None are held.

  • 02

    We do not publish customer names, testimonials or measured customer results before they exist.

  • 03

    Validation documentation is shared under NDA rather than summarized as a marketing claim.

Next step

Bring your governance questions to the demo.

Validation approach, audit trails, QC independence and human approval are fair questions to ask before anything else.