Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Demand Vendor Data Deletion Processes
Transcript
- Lucas: So there's a new line item showing up in enterprise RFPs that didn't exist five years ago. It's not about uptime, security, or even pricing. It's a clause asking vendors to certify what happens to the customer's data after the contract ends — or after a breach. Luna: You mean the data deletion clause. I've seen it pop up in a couple of our own RFPs. It used to be buried in the legal boilerplate, but now it's a standalone section with its own sub-bullets. Lucas: Exactly. And what's interesting is that it's no longer just a checkbox. Some buyers are demanding a written certification that the vendor will delete all copies of their data within thirty days of the contract termination. And they want a named individual to attest to it. Luna: A named individual? That's heavy. So they're trying to create a personal liability hook, not just corporate gobbledygook. Lucas: Right. And it's not just the big regulated industries like banking or healthcare. I'm seeing it in manufacturing, retail, even some mid-market construction firms. The driver is a combination of GDPR, the SEC's cyber disclosure rules, and just a general fatigue with data being held hostage. Luna: The GDPR right to erasure has been around since 2018 though. What changed recently that's making procurement act now? Lucas: Two things. First, the SEC's cyber disclosure rule that took effect in late 2023 forces public companies to disclose material cybersecurity incidents. That put data governance on the board's radar. Second, the Schrems II decision in 2020 invalidated the Privacy Shield, making data transfers to the U.S. legally murky. So now legal teams are actually reading the fine print. Luna: And they're realizing that deleting data isn't as simple as pressing a button. Especially if you're a multi-tenant SaaS running on a shared database. Lucas: That's the rub. Your average SaaS vendor uses a database where customer data is mixed together. To truly delete one customer's data, you need to restructure the entire database. That's why some vendors push back on these clauses, offering 'logical deletion' instead — meaning they simply disable the account and remove the data from active queries. Luna: Logical deletion is not deletion. It's hiding. And sophisticated buyers know that. Lucas: Exactly. Which is why we're seeing some RFPs demand a 'deletion certificate' — a formal document, sometimes signed by the vendor's CTO, certifying that the data has been purged from all systems, including backups, within a reasonable period. And they want the right to audit that deletion. Luna: An audit right for deletion. That's new. How do you even audit something that's gone? Lucas: You ask for a report that shows the data was wiped from the production database, the logs, the archival systems, the disaster recovery backups. Some vendors even hire third-party firms to verify. But here's the thing — most small SaaS vendors simply can't do that. They don't have the engineering resources. Luna: So this clause becomes a market filter. It's a way to weed out vendors who are building on shaky data foundations. Lucas: Precisely. And it's not just about compliance. It's about risk management. If a vendor is acquired and their data practices are messy, the buyer inherits that risk. So they're using deletion clauses to force vendors to have a clean data lifecycle from day one. Luna: Let's talk about the backup issue. Because that's where I keep seeing the language get fuzzy. A lot of vendors say 'we'll delete production data, but backups take ninety days to cycle.' The buyer is left with a question: is your data actually gone? Lucas: Right. And some vendors will try to carve out backups from the deletion obligation, arguing it's technically infeasible to purge them immediately. But now I'm seeing procurement push back with a simple question: 'Do you have a process to selectively delete from backups?' If the answer is no, that's a dealbreaker. Luna: And if the answer is yes, it's a competitive advantage. A vendor that can say 'we can purge a single customer's data from all systems within seven days' — that's a weapon. Lucas: Exactly. And it's not just about deletion. It's about the entire data lifecycle. Some RFPs now ask about data portability, too. They want the vendor to provide a structured export of all their data before deletion, so they can move to another provider if they want. Luna: Portability and deletion go hand in hand. It's like a proper breakup: you want your photos back, then you want to erase your ex from your phone. Lucas: Ha, that's a perfect analogy. And that's where the conversation gets interesting, because some vendors argue that deletion and portability are mutually exclusive. You can't export everything and then delete everything if your architecture relies on a shared data lake. Luna: But that's a vendor problem, not a buyer problem. The buyer's requirement is clear. The vendor has to figure out how to build for it. Lucas: And that's exactly what the forward-thinking ones are doing. I read about a mid-sized CRM vendor that restructured its entire data model to support per-customer encryption keys. Now they can delete a customer's data by simply destroying the key. It's elegant. Luna: Destroy the key, and the data becomes unreadable gibberish. That's a cold, clean deletion. Lucas: It's also a great talking point in a sales demo. You can literally show the procurement team: this is our deletion process, here's the audit log, here's the certificate we provide. That's the kind of thing that wins over a skeptical security team. Luna: And it's a differentiator in the RFP process. Because most vendors can't do that. They're still stuck in the 'we'll try our best' mode. Lucas: Look, if you're a builder or an operator listening, and this conversation is helpful, you might consider supporting the show. It's a small thing — if today was worth a coffee to you, the link is buy me a coffee dot com slash fexingo. It keeps this podcast ad-free and lets us keep digging into these procurement rabbit holes. Luna: Yeah, we've had a few people ask how to support us, and that's the simplest way. No pressure, but it genuinely helps us keep the lights on. Lucas: Right. So back to that deletion certificate. It's not just a piece of paper. It's a legal commitment. And increasingly, it's a dealbreaker. If a vendor can't commit to a timeline and a process, the procurement team just moves on. Luna: And it's not just about the next contract. It's about the vendor's long-term viability. If they can't handle deletion, how are they going to handle a major breach or a data subject access request under GDPR? Lucas: Exactly. It's a proxy for overall data governance. That's why I think this clause is here to stay. It's not a fad. It's the new baseline. Luna: So what practical advice would you give to a SaaS vendor who's starting to see this in RFPs but hasn't built the architecture yet? Lucas: First, don't panic. But do start auditing your own data flows. Map out where customer data lives — production, logs, backups, third-party subprocessors. Then figure out which of those can be purged on demand. Start with the easy ones, like production, and work your way to the hard ones, like offline backups. Luna: And if you can't do full deletion from backups, what do you say? Do you just lose the deal? Lucas: You have to be honest. Some buyers will accept a commitment to delete from backups within a reasonable period, like ninety days, as long as you're transparent about it. But if you try to hide it and they find out, that's a trust breach that will kill the deal anyway. Luna: So transparency is the name of the game. And maybe that's the real lesson here: the deletion clause isn't just about the data. It's about the vendor's willingness to be honest. Lucas: That's a good way to put it. And it's why I think this clause is actually a gift to the industry. It forces SaaS vendors to build cleaner, more defensible architecture. And in the long run, that's better for everyone. Luna: Yeah. It's a hidden blessing. A forced evolution. Lucas: And as a buyer, the next time you see a data deletion clause in an RFP, don't just skim it. Ask the vendor to walk you through their process. Ask for a sample certificate. If they can't produce one, that tells you something. Luna: And if they can, you might have found a partner who actually thinks about data the way you do. Lucas: Exactly. That's the takeaway. Data deletion is not a checkbox anymore. It's a reflection of a vendor's maturity. And as we've seen, the cost of getting it wrong is just too high. Luna: So what's next? Do you think we'll see even deeper scrutiny, like asking for deletion proofs in real time? Lucas: I wouldn't be surprised. The trend is toward more granular, more auditable data control. Maybe someday we'll see automated deletion reports via API. But for now, the conversation is just getting started.