The same register the marketing and legal teams work from.
The read-only view
A read-only evidence view, shared with you by the brand owner. Each claim shows the documentation on file behind it, with dates and integrity hashes, and its dated history.
Shared by the owner, not issued by us
The link is the brand owner's to issue and theirs to revoke. An invalid or revoked link resolves to a page saying the shared record is no longer available, and asking you for a fresh invite.
Nothing on the shared view is editable, and it is the same register the brand's marketing and legal teams work from. You are reading their working record, not a document prepared for you.
The register opens with its own counts
The head of the register states how many claims are on file, how many are substantiated, and how many need attention, before any individual claim is read.
A counsel workspace, not an export
On the Brand tier an operator can invite outside counsel into a read-only view. On the MSO platform that counsel workspace is shared across every brand the group runs.
This page shows the documentation evidence on file supporting each advertising claim, with the dates and integrity hashes recorded. It is a record of documentation, independently maintained by Veritura and shared with you by the brand owner. It is not legal advice, an FDA approval, a certification, or a determination that any claim is compliant or true beyond the documents cited.
What is on each claim
The claim as written, its evidence, its timeline, and its run record.
One card per claim. The wording as it ran, the status, then three blocks that are always present, including when they are empty.
Evidence on file
Each documentation record bound to the claim, with the date it is as of, whether that state is current or no longer current, and its integrity hash. A claim with nothing behind it says so: no evidence bindings on file for this claim.
The dated history of the claim, each entry carrying what changed and the reasons recorded against it. Where there is none, the record says no dated history recorded rather than showing an empty block.
Run record
The first run on file and the channels the claim ran on. Where the operator never stated a first run, the record says first run not stated by the operator, instead of leaving the field blank.
The four words a claim can carry
Two flags that can sit beside a status
- Flagged: cannot be backed as written
- Reframed to documentation language
The binder
The whole register exports as one dated and hashed substantiation binder, or one claim at a time from the claim's own card.
The same discipline on the sourcing side of the file.
Veritura preserves the order, lot, COA and source reference, release state, and visible documentation checks for the record. We do not sell the product. This is documentation evidence, not product testing or an authenticity guarantee.
Semaglutide (base) API
The document set met the configured policy. It describes the paperwork, not the medicine.
The issuing laboratory confirmed issuance through the recorded verification route.
- Order
- PO-DEMO-0413
- Lot
- LOT-7741-A
- Supplier
- Aurora Pharma Supply
- Quantity
- 250 g
- Received
- July 22, 2026
- Released
- July 23, 2026
- Passport issued
- July 23, 2026
- Methodology
- v1.0 · April 30, 2026
Documents on file
COA-7741-A.pdf · Issuing laboratory confirmed issuance through the recorded route
CoC-7741.pdf · Required identity, lot, and date fields present
SDS-SEMA-04.pdf · Current revision on file
GMP-AUR-2026.pdf · Supplied by the operator
Recorded in workspace · Container and label checked at receipt
LBL-7741-A.jpg · Lot identifier matches the certificate of analysis
What this record does not establish
- Documentation diligence only. No product was tested and no supplier was approved.
- Absence of a public-source match is not proof of absence.
- Produced under methodology v1.0, April 30, 2026.
What a Veritura record shows
- An automated read of the submitted document by a party that does not sell the product.
- A tamper-evident fingerprint you can cross-check against the original certificate.
- Documentation completeness, source chain, and reuse signals.
The checks preserved on the record
- Duplicate and reused-document signal scan
- Order, lot and COA cross-match
- Customer-safe release gate
The fingerprint, the chain, and a way to check both without us.
A record whose integrity you can only confirm by asking the party that issued it is not much use in a dispute. These are the parts you can check yourself.
The fingerprint
Every reviewed document is hashed and assigned an evidence ID, preserved in the report so the file can be reconstructed at inspection time.
The record's SHA-256 fingerprint can be recomputed in your own browser from the visible record fields, and the page shows exactly what was hashed: the fields, in that exact order. Change any field and the fingerprint changes.
Chain of evidence
The record's dated journey renders as a timeline, each entry carrying its label, its detail, and its timestamp to the minute in UTC.
The signature is re-checked on view
A Sourcing Decision Receipt is signed, and the signature is re-checked each time the page is opened. When that check fails the record says so on its face: signature check failed, do not rely on this copy.
A Sourcing Decision Receipt is a signed, patient-information-free record an operation issues for one order reference. It composes the sourcing evidence already on file at issue time: the live FDA source screen, the supplier qualification file, the certificate check, the lot watch, and the signed policy decision. It documents what was on record; it does not test a product or make a quality or regulatory determination.
What it can and cannot support
What the record carries, and what it refuses to decide.
Reports document evidence. A Veritura record is a preserved read of documentation and never a determination about a product, a claim, or a party.
What the record carries
That the documentation on file was read by a party that does not sell the product, and that the read was preserved: the dates, the integrity hashes, the dated history, and whether each binding was current or no longer current at the time it was read. Read-only, and independently maintained.
What it does not decide
Whether any claim is legal, compliant, or FDA-approved. Whether any product is safe, sterile, effective, pure, or appropriate for any use. What the law requires. Veritura does not test physical material and does not certify quality or safety.
Every fact on a record carries its origin
Four labels, never mixed, so a reader can tell who stood behind each line before weighing it.
Documentation evidence, not legal advice. We never assert a claim is compliant. Veritura holds each claim's evidence with dates and hashes, watches it, and produces it on demand; it does not determine that any claim is legal, compliant, or FDA-approved. What the law requires stays with your counsel.
Authenticity limits. A report may identify metadata, repeated file signals, links, and inconsistencies. It cannot prove document provenance unless an issuing lab or source independently confirms it.
Not a safety assessment. Veritura does not determine whether any product is safe, sterile, effective, pure, legal, or appropriate for any use.
AI may assist extraction and drafting. Delivered written diligence memos receive human QA. Self-serve checks, ClearGate decisions, and Passports are automated unless the record explicitly says otherwise, and no human sign-off is claimed on them.
What can change on a record, and what never disappears.
A record that can be quietly edited is worth nothing to the person reading it. These are the only ways a Veritura record moves.
Nothing supported is removed
Veritura does not remove supported observations because they are unfavorable. Reports are corrected when a factual error or missing source is demonstrated.
A correction is reviewed against the source
Correction requests are reviewed against the underlying source material and the methodology version used for the report.
A response attaches without erasing the observation
Where appropriate, a response or supplemental document may be attached to a report without changing the original observation.
Anyone with standing can submit one
Users, vendors, labs, or other relevant parties may submit factual corrections, supplemental documents, or responses tied to a report ID.
A correction request should carry the report ID, the specific observation at issue, and the document or source that supports the correction.
Read the boundary before you read the record.
The Trust Center carries the limitations, the data posture, and the methodology in full, and it is kept current.
Independently documented by Veritura. A record of documentation, not legal advice.