About a year ago, with GDPR enforcement looming, we decided to hit the brakes on EU sales because we weren’t confident enough in the third party app ecosystem’s compliance capabilities, or the EU’s ability to police the regulation effectively.
In the time since, it’s been interesting to see that:
- Few folks requested their data or the right to be deleted
- Among others, Google got hit with a GDPR fine
- The compliance ecosystem has gotten marginally better, but still not great
- Brexit (or maybe not, who knows)
- The EU’s working on a new copyright filter law (Julia Reda’s writing on that has been phenomenal)
Looking at that list, it’s not that I’m suddenly filled with an overwhelming confidence that it’s easy and cost-effective to build a product with GDPR compliance, AND to defend a company against an EU country’s GDPR inquiry. However, I do think that it’s time to start looking at what it would take to sell SQL ConstantCare® in the EU. I specifically mean to sell it though – not just what it would take to be compliant, but have a cloud product that Europeans would open their wallets for. (And I’m not even sure that’s a possibility yet, thus the post.)
As we go down that road, I’m curious about Europeans’ opinions to a few questions:
- Would your company even be open to a solution like that?
- What kinds of objections have your managers raised about cloud-based products?
- Have you tried to implement a cloud-based product, and failed? Or succeeded?
- Between Amazon’s regions (Frankfurt, Ireland, London, Paris, and Stockholm), is there one that your company absolutely insists that its data must be stored in? (Strictly speaking, EU data residency isn’t a technical requirement, but companies often have political requirements.)
Let me know what you think in the comments. I’m not making promises that we’ll sell to the EU by the end of the year – but it’s something that we’re starting to consider.