Cryptographic deletion certificates for GDPR, CCPA, and SB 362 compliance. Independently verifiable. No trust required.
GDPR Article 17 and California's Delete Act (SB 362) require data deletion on request. Penalties run $200 per request per day. But how do you prove it happened?
Internal deletion logs are self-attestation. A regulator can't verify them independently. Screenshots and Jira tickets won't hold up under audit.
Privacy platforms like Transcend and OneTrust orchestrate deletion workflows. They don't cryptographically verify the data is actually gone.
Connect your PostgreSQL, MongoDB, S3, Redis, or Elasticsearch with read-only credentials. We verify they're read-only and reject write access.
One API call creates a cryptographic attestation. We query your systems, hash the records in memory, and immediately discard the raw data. Only hashes are stored.
Use your own tools, your own process. We're not involved. You maintain full control over the deletion.
One API call triggers re-verification. We re-query your systems. Records gone? We issue an Ed25519-signed certificate, logged in our public transparency log.
Independently verifiable. No API call needed. It's math, not trust.
import { BurnLedger } from "burnledger";
const dp = new BurnLedger({ apiKey: process.env.BURNLEDGER_API_KEY });
// Before deletion
const att = await dp.attestations.create({
subjectIdentifier: "user@example.com",
systemIds: ["sys_pg_users", "sys_s3_uploads"],
});
// After deletion
const result = await dp.attestations.verify(att.id, {
subjectIdentifier: "user@example.com",
});
// Download certificate
const pdf = await dp.certificates.download(result.certificate.id);from burnledger import BurnLedger
dp = BurnLedger(api_key="dp_live_...")
# Before deletion
att = dp.attestations.create(
subject_identifier="user@example.com",
system_ids=["sys_pg_users", "sys_s3_uploads"],
)
# After deletion
result = dp.attestations.verify(
att.id, subject_identifier="user@example.com"
)
# Download certificate
cert = dp.certificates.download(result.certificate.id)Need something else? We'll build the connector.
Records are hashed in connector memory and immediately discarded. Raw data never touches our servers, our disks, or our logs.
Subject identifiers are salted with SHA-256 using your unique customer salt. The plaintext is held in memory only during query execution.
Ed25519 signatures are standard cryptography. Any library can verify them. If BurnLedger disappears tomorrow, your certificates are still valid.
Every certificate is recorded in an append-only Merkle tree (RFC 6962). We can never deny issuing a certificate. Tamper-evident by design.
Type anything below. On the left is your data. On the right is what reaches our servers. We never see the original.
One certificate. Every jurisdiction. The protocol proves a fact — data was present, now absent — regardless of which regulation triggered the deletion.
Connect your first database in under an hour. See deletion proof in action.
Questions? Email hello@burnledger.io