Certificate Policy
This Certificate Policy defines what CertifiedData certifies, under what conditions a certificate is issued, and what a certificate proves to relying parties.
Version 1.0 — Effective 2026-01-01
1. Scope and purpose
CertifiedData.io operates as a certificate authority for AI artifacts. A CertifiedData certificate is a machine-verifiable cryptographic record that proves:
- A specific artifact (identified by SHA-256 hash) was generated synthetically
- Generation occurred at the stated timestamp
- The stated generation algorithm was used
- The certificate was issued by CertifiedData.io (verified by Ed25519 signature)
A certificate does not prove accuracy, usefulness, representativeness, or fitness for any particular purpose of the artifact's contents.
2. What is certified
CertifiedData issues certificates for:
- Synthetic datasets — tabular datasets generated by the CertifiedData generation engine (CTGAN, Gaussian, Light, or DP-CTGAN algorithms)
- Marketplace datasets — pre-built certified synthetic datasets distributed through the CertifiedData dataset marketplace
CertifiedData does not currently certify external datasets, model artifacts, or AI outputs not generated by the CertifiedData platform.
3. Certificate issuance
A certificate is issued automatically upon successful completion of synthetic dataset generation. The issuance process:
- The generation engine produces a ZIP artifact containing the CSV dataset and a generation manifest
- SHA-256 hashes are computed for the ZIP archive and each inner file
- A certificate payload is constructed with all required fields
- The payload is canonicalized using RFC 8785 (JSON Canonicalization Scheme)
- The canonical payload is signed with the active Ed25519 private key
- The certificate record is persisted to the CertifiedData database and made publicly available
4. Certificate validity
Certificates do not expire. A certificate remains valid as long as:
- The signing key has not been revoked
- The certificate has not been explicitly revoked by CertifiedData
Certificates issued by retired (non-revoked) keys remain fully valid and verifiable.
5. Revocation
CertifiedData may revoke a certificate if:
- The certificate was issued due to a system error or fraudulent request
- The signing key used was compromised (key-level revocation affects all certificates signed by that key)
- The underlying artifact is found to contain real (non-synthetic) personal data
Revocation status is published at the public verification endpoint. Revoked certificates return verified: false with reason certificate_revoked.
6. Relying party obligations
Relying parties using CertifiedData certificates for compliance, procurement, or governance purposes are responsible for:
- Independently verifying certificates using the public verification endpoint or local verification tools
- Checking certificate revocation status at time of reliance
- Confirming the artifact hash in the certificate matches their copy of the artifact
- Understanding that a certificate proves synthetic origin, not fitness for purpose
7. Liability limitations
CertifiedData certificates are provided as-is. CertifiedData makes no warranty regarding the suitability, accuracy, or completeness of certified datasets for any particular use. Certification proves provenance and synthetic origin — it does not constitute an endorsement of the dataset's contents or fitness for any regulatory, compliance, or operational purpose.
8. Contact
Questions about certificate issuance, revocation requests, or this policy should be directed to [email protected].