Warehouse is the certified claim
The signed certificate always proves what it can fully verify: key destruction in your warehouse. Nothing here weakens or dilutes that.
A bonus layer on top of certified warehouse erasure: HubSpot and Salesforce cleanup.
Chameleon's certificate proves warehouse erasure — that's the claim it can fully back. Where HubSpot and Salesforce are connected, Chameleon also sends a deletion instruction and records the receipt alongside it, so cleanup progress there is visible too, not just assumed.
Connected SaaS cleanup, tracked
When HubSpot or Salesforce are connected, cleanup receipts are captured and shown alongside the warehouse evidence — not silently assumed to have happened.
Honest about scope
A receipt means a receipt was collected. Where a system isn't connected, or a receipt wasn't returned, that's shown plainly rather than implied as covered.
Warehouse erasure is the core claim. This is what's layered on top.
Chameleon's core product is warehouse-native: discover PII, detect what's undeclared, and crypto-shred it so every warehouse copy — tables, dbt models, backups, exports — becomes mathematically unreadable. That's the claim the signed certificate makes, and it's a claim Chameleon can fully back with cryptographic proof.
The same customer whose data you crypto-shred in your warehouse may also live in HubSpot or Salesforce. Building and maintaining a real integration with every SaaS tool a customer might use is a different, unbounded engineering problem — in most organizations it's also a different team's job (sales ops owns Salesforce, support owns the help desk). Chameleon doesn't try to own that. Where HubSpot or Salesforce are connected, it sends a deletion instruction and shows you the receipt — a real, useful convenience, not the headline claim.
Warehouse erasure first, SaaS receipts alongside it.
When a deletion request runs, the Key Vault destroys the warehouse key first — that's what the certificate signs. If HubSpot or Salesforce are connected, Chameleon also queues a cleanup action for that customer's contact or lead record and captures the receipt as the system reports it.
Those receipts show up alongside the warehouse evidence so you can see SaaS cleanup progress in one place — but they're shown as exactly what they are: per-system receipts, not folded into the certified warehouse claim.
01 / Identify
Start from the customer identifier and the connected SaaS systems in deletion scope.
02 / Queue
Prepare cleanup actions for HubSpot contacts and Salesforce lead/contact records.
03 / Collect
Capture wipe results and receipts when connected systems report completion.
04 / Attach
Attach SaaS cleanup status to the deletion proof record alongside warehouse evidence.
HubSpot: wipe_succeeded
Salesforce: sandbox_receipt
BigQuery: key_destroyed
proof: certificate_issued
Salesforce: sandbox_receipt
BigQuery: key_destroyed
proof: certificate_issued
Common questions
Does GDPR require deleting data from CRMs like HubSpot and Salesforce?
Yes. Article 17 requires erasure of personal data wherever it exists, and Article 17(2) adds an obligation to inform other recipients you shared the data with so they erase it too. A CRM or marketing tool holding a customer's contact record is squarely in scope for an erasure request.
Does the signed certificate cover SaaS deletion too?
The certificate's core, cryptographically-backed claim is warehouse erasure — that's what Chameleon can fully prove. When HubSpot or Salesforce are connected, cleanup receipts are captured and shown alongside the certificate as evidence of what was attempted and reported, but the underlying compliance obligation is still one the owning teams need to track directly: sales ops for Salesforce, support or marketing ops for HubSpot. Chameleon shows you the receipt; it doesn't claim to own that obligation for you.
Which SaaS systems does Chameleon support?
HubSpot and Salesforce today, as an optional convenience layered on top of the certified warehouse product. Chameleon deliberately isn't trying to build and maintain deletion integrations for every SaaS tool a customer might use — that's an unbounded commitment, and it's not where the product's real guarantee (cryptographic warehouse erasure) lives.
How the signed warehouse certificate works, and how SaaS receipts show up alongside it.
The third-party notification obligation in Article 17(2) and what completeness requires.
How access and deletion requests reach every system that holds a customer's data.