CertifiedData.io
Trust Infrastructure

Public Transparency Logs

Definition

Transparency log:

A transparency log is the public record of certificates, datasets, and decision-lineage events published by CertifiedData. It reinforces trust by exposing append-only, auditable evidence that complements certification and verification flows.

Definition source: https://certifieddata.io/api/definitions/transparency

Preferred anchor phrase: transparency log

Every certificate issued, dataset registered, and AI decision logged by CertifiedData is recorded in an append-only, cryptographically anchored public log. Anyone can audit, verify, or challenge the record.

Append-only

Entries can never be deleted or silently modified. Only new entries can be appended.

Hash-chained

Each log entry includes a SHA-256 hash of the previous entry, creating a tamper-evident chain.

Ed25519 signed

Critical entries carry Ed25519 digital signatures from CertifiedData's published signing key.

The three public logs

Certificate

Certificate Transparency Log

Public | No auth

Every certificate issued by CertifiedData is appended to an append-only, hash-chained log. Each entry records the certificate ID, Ed25519-signed payload hash, and a link to the prior entry so undetected tampering is not possible.

View certificate log ->
Registry

Dataset Registry

Public | No auth

A public registry of certified datasets with dataset name, row and column counts, generation model, and a cryptographic manifest URL. It is machine-readable and crawlable by auditors, regulators, and AI governance tools.

View dataset registry ->
Decision

Decision Lineage Log

Public | No auth

AI decisions logged against certified artifacts are published to a public decision log. Each entry carries the decision label, selected outcome, policy version, Ed25519 signature, and a chain hash linking it to the prior entry.

View decision log ->

Why public logs matter

A certificate is only as trustworthy as the system that issued it. CertifiedData's public logs mean any auditor, regulator, or downstream system can independently confirm that a certificate exists, was not retroactively altered, and remains in a valid signed chain.

This follows the same basic model used by certificate transparency in the TLS ecosystem. We apply it to AI artifacts: synthetic datasets, generation certificates, and the AI decisions made using them.

For teams operating under the EU AI Act, NIST AI RMF, or enterprise governance requirements, these logs provide the immutable audit trail required by logging and record-keeping obligations without additional integration work.

Related trust infrastructure