Connected SaaS scope
Represent HubSpot and Salesforce cleanup as part of the same customer-data deletion request.
Track HubSpot and Salesforce cleanup in deletion proof.
Chameleon keeps connected SaaS cleanup receipts visible next to warehouse evidence so privacy teams can see deletion progress beyond the warehouse itself.
Receipt tracking
Keep wipe status and sandbox receipts attached to the proof surface instead of scattered across separate tools.
Reviewable evidence
Show which systems succeeded, which retained audit evidence, and what still needs follow-up.
Erasure doesn't stop at the warehouse.
The same customer whose data you crypto-shred in your warehouse (BigQuery or Snowflake) also lives in your CRM and marketing tools. HubSpot holds their contact record; Salesforce holds their lead or contact history. GDPR Article 17(2) is explicit: where you have shared personal data with others, you must ensure it is erased there too — and downstream tools are the copies teams most often forget.
The practical difficulty is that each SaaS tool has its own deletion API, its own idea of a receipt, and its own audit log. Cleanup ends up scattered across three consoles, and no single place tells you whether the customer was actually removed everywhere.
One deletion request, receipts from every system.
When a deletion request runs, Chameleon queues cleanup actions for the connected SaaS systems in scope — HubSpot contacts, Salesforce lead and contact records — alongside the warehouse key destruction. As each system reports completion, Chameleon captures the receipt and attaches it to the same proof record.
The result is a single certificate that shows the warehouse key was destroyed and the downstream tools were wiped, with a per-system status. Instead of asserting that you 'also cleaned up the CRM,' you can point to the receipt.
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.
How does Chameleon prove SaaS records were deleted?
Chameleon sends cleanup instructions to each connected system and collects a completion receipt — a wipe confirmation or sandbox receipt — as the system reports it. Those receipts are attached to the deletion proof certificate alongside the warehouse evidence, so one record covers every system.
Which SaaS systems does Chameleon support?
The connected-SaaS cleanup flow covers HubSpot and Salesforce today, capturing contact and lead/contact deletion receipts. The same receipt-tracking model is designed to extend to additional downstream tools that hold customer data.
How warehouse evidence and SaaS receipts combine into a single audit-ready certificate.
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.