Your marketing or analytics SaaS vendor is breached (e.g. PLAID KARTE, Triple Whale, bank marketing vendors): scope your data, rotate integration secrets, warn customers, and check that ex-vendor data is gone
For companies whose customer data sits in a third-party marketing, CX or analytics platform. Built from November 2026 cases where one vendor intrusion exposed data for hundreds of client companies, including some that had already left.
1. Establish what the vendor held for you2. Rotate every integration secret3. Decide on notification4. Fix the contract and the architecture
Establish what the vendor held for you
Vendor notices describe categories; you need your own list.
- Pull your data-sharing inventory for the vendor: uploaded member tables, event/tag data collected on your sites, cached identifiers
- Ask the vendor for per-company detail (PLAID promised it from Nov 24) and the exact attack window
- Include vendors you left: ask whether your data was actually deleted at contract end
Rotate every integration secret
Marketing platforms hold keys to email, CRM, ad and data-warehouse accounts.
- List every API key, OAuth grant and webhook secret you gave the vendor; revoke and reissue them
- Review the connected services' audit logs from the attack window onward for unusual logins, exports or campaign sends
- Remove the vendor's site tag or SDK while their service is down or rebuilding
Decide on notification
Legal duty usually stays with you as controller even when the vendor was breached.
- Work with privacy/legal on regulator deadlines (e.g. Japan PPC, GDPR 72 hours) from when you learned of it
- Tell customers exactly which fields were exposed and what was not, and warn about phishing that uses those details
- Prepare your call centre for questions
Fix the contract and the architecture
Use the incident to reduce what any single vendor can leak.
- Send only the minimum fields needed (pseudonymous IDs instead of names and emails where possible)
- Add deletion-at-termination evidence and breach-notice timelines to vendor contracts
- Keep integration tokens least-privilege and scoped so a stolen one can't export your whole CRM