A public audit trail for Kled data
Every dataset available through Kled is backed by an audit trail of contributor consent, policy acceptance, provenance signals, and compensation status. Verify any asset. Review any dataset and the chain of custody.
We work with
Live receipts
Every contribution Kled accepts surfaces here within seconds. Click any hash for the full receipt.
| Event | App | Address | Activity | Date |
|---|---|---|---|---|
Compliance frameworks, and when it was last assessed.
Frameworks Kled operates under and the third-party audits that stand behind them. Each row links to the underlying audit trail.
California Consumer Privacy Act
EU General Data Protection Regulation
Independent security & privacy audit of Kled
Audit window in progress
Every receipt onchain via Trace
Audit controls
- Data minimization
We only share the minimum metadata needed for provenance confirmation.
In place - Retention policy
Retained under consent or other legitimate legal basis.
Consent-boundIn place - Right to deletion
Contributor-initiated. Asset removed from active datasets; audit record preserved.
In place - Right to access
JSON export of all data held against a contributor's account.
In place - Data residency
AWS eu-west-1 for EU contributors, us-east-1 for North America.
In place
Download
Compliance documents
Public versions are downloadable directly, content-addressed and verifiable against the same Trace ledger your team audits.
What Kled collects
File coverage
Every receipt declares the media category, MIME type, and size of the file it stands for.
Average file
301.1 KB
Files measured
31,747,537
Media categories
File formats
+16 more formats
Where contributions come from
Contributor geography
Each receipt carries the contributor's region (contributor.geo_region), bucketed here so individual contributors stay anonymous.
Top region
NA
North America
Regions
4
with located receipts
Geographic spread of contributors
North America
NA
34.5%
Southeast Asia
SEA
32.8%
European Union
EU
32.7%
Oceania
OC
0%
Weighted by receipt volume. Sub-regional resolution available per asset; never finer than country / state.
Consent receipts
Consent and policy versions
The exact terms and privacy policy each contributor agreed to at the moment of contribution, including every version that's ever appeared on a receipt.
Terms of service
Privacy policy
F.A.Q.
If your team has a question we haven't covered, your account manager can answer it, and we'll add it here.
Is Kled GDPR ready?
Yes. Kled operates GDPR-based data collection for all contributors with EU regional metadata, and exposes for consent the operative TOS / privacy policy version on every receipt.
How can a contributor revoke consent?
As outlined in our TOS and PP. Revocation produces a new lifecycle event on each affected receipt and removes the asset from active datasets. The receipt itself remains visible on Trace as a permanent audit record.
What sub-processors does Kled use?
Please see trust.kled.ai for our sub-processor list.
Why is the audit trail on a separate, public layer?
Building an audit surface in-house creates a permanent target for accusations of bias. Trace is the impartial alternative: a public, onchain ledger that customers, regulators, and contributors all check on the same terms. Kled contributes receipts to it; we don't control its visibility.
How are sensitive metadata values handled?
Sensitive signals like EXIF, GPS, IP addresses, and device fingerprints stay in Kled's own systems. Trace stores existence flags (present or absent), never the values. This preserves the integrity signal labs need without making the audit layer a deanonymization tool.
Where can I see the underlying data?
Kled does not expose the underlying assets through this portal, receipts and compliance posture only. Labs evaluating a dataset for licensing are given access through Kled's commercial channels.