Security and data integrity

A verification record you can hand to an auditor.

Every calibration WLTR evaluates is captured, hashed, attributed and approved. Attributable actions, original records that cannot be altered, and a complete trail from instrument export to approved result, for every lab and every method.

Request a demoContact us

Try it

Change one number. Watch the record catch it.

When an export is uploaded, WLTR records a SHA-256 fingerprint of the original file. Edit any peak area below. The fingerprint is recalculated live in your browser, and even a one-digit change no longer matches the source record.

ICAL_COMPOUND-A_RUN0412.TXTIllustrative export
Level Nominal (ng/mL) Peak area
STD 1 1.00
STD 2 2.00
STD 3 5.00
STD 4 20.0
STD 5 100
STD 6 500
SHA-256 at upload

calculating…

SHA-256 now

calculating…

Match. This file is identical to the source record.

Attributable, end to end

Who did what, when, and why. On every record.

Every step from upload to approval is recorded against a named user. This is what an auditor sees when they ask how a calibration was accepted.

Run 0412 · Calibration record · Illustrative

Pending QA review

  1. 09:14:02A. PatelAnalystUploaded ICAL_COMPOUND-A_RUN0412.TXT. SHA-256 recorded.
  2. 09:14:03WLTRSystemReadiness checks passed. Method configuration locked.
  3. 09:14:41WLTRSystemEvery candidate model scored against the acceptance criteria. Linear, 1/x² recommended.
  4. 09:22:15A. PatelAnalystSelected Linear, 1/x². No standards excluded. Submitted for QA review.
  5. 09:22:16WLTRSystemQA Director notified. Awaiting review and signature.
QA Director sign-offR. Okafor · QA Director

Signature meaning: Approval. I have reviewed this calibration record, its exceptions and its full audit trail, and I approve it for use.

Illustrative. In WLTR, approval requires the reviewer’s own credentials, and the signature is permanently linked to this record.

Built-in controls

Every value traces back to its source.

01 · Original records

Immutable source data

Raw instrument text is captured at upload, hashed with SHA-256, and preserved unchanged. Every downstream value traces back to that original record.

02 · Controlled computation

Readiness gates and frozen methods

Readiness validations run before every computation, and method configurations are frozen once results exist, so historical results never shift.

03 · Run-type awareness

The right data in the right place

WLTR tracks run types, so verification samples such as the ICV can never silently enter a calibration curve.

04 · Review and approval

Role-separated sign-off

Calibration records are approved through role-separated QA review with a named approver, and every action is kept on a permanent audit timeline.

ALCOA+ alignment

How WLTR maps to the data integrity principles regulators use.

Select a principle to see what auditors expect and the WLTR control that supports it.

Principle

Attributable

What auditors expect

Every action tied to a named person.

How WLTR supports it

Named users, role-based access and a named approver on every record.

6 of 6 principles supported

21 CFR Part 11

Designed for labs that work under Part 11.

Labs that produce records for FDA submissions must show their electronic records are trustworthy and their signatures are controlled. WLTR provides the record-level controls those labs look for, including audit trails, named approvals and protected original records. Validating WLTR for its intended use within your quality system remains your lab’s responsibility, and we support that process with documentation on request.

Questions

Frequently asked questions

Is WLTR 21 CFR Part 11 compliant?

Part 11 compliance applies to how a regulated lab validates and operates its systems, not to software alone. WLTR provides the controls Part 11 environments rely on, including audit trails, role-separated approval and protected original records, and we support your validation with documentation.

Does WLTR alter our raw data?

No. Original instrument text is preserved unchanged with a SHA-256 hash. WLTR stores its evaluation alongside the original record.

Who can approve a calibration record?

Approval roles are configured to your SOP. Records are approved through role-separated QA review with a named approver, and every step is kept on the audit timeline.

Can we review your security documentation?

Yes. Contact us at admin@wltr.tech to request security and validation documentation for your evaluation.

Next step

See the audit trail on your own data.

Bring a recent instrument export. We will walk you through the source record, the evaluation and the approval trail.

Request a demoJoin the pilot program