Utah Lawsuit Update - Stolen Documents I think it is important to give the public an update on our Utah lawsuits.
How would dirty dough get that information from your database? How poorly did you encrypt and safeguard your data? How after was the data accessed? What have you learned and changed to protect your data going forward? If the store data and recipes were accessed, what other data assets were compromised? How did your team not notice this was done and from hire out when/what went missing? Did dirty dough collaborate with anonymous to get your recipes and store schematics, yet leave customer data completely unaffected? Seems convenient that an ex dirty dough employee would turn this information in to you guys though. Whew…. They must’ve been just sharing that data Willy nilly internally huh? So if this data was accessed, apparently without your knowledge, when will we hear of Crumbl customer data “breaches”?
Hola Graeme! Interesante contenido gracias por compartirlo! Aquí te dejo uno nuestro que puede complementar tu punto de vista https://www.rootstack.com/en/blog/when-should-you-consider-outsourcing-software-development/, espero sea útil! https://www.rootstack.com/en/blog/when-should-you-consider-outsourcing-software-development/
Dirty Dough - so it’s not just a clever name?
Should have started here. This would have been more reasonable. Now, I already lost a lot of respect for Crumbl and while data theft is terrible, I just think it's mud slinging time to fix your name...
Well…. sounds like they are on brand!
This post makes me want a cookie.
You know, those "Keebler Elves" make some pretty good cookies and for a whole lot less "Dough"... not to mention the bakery at my local "Macey's" too...
With this info, Dirty Dough seems aptly named. 🫢
Event & Meeting Planner
2yThis is way too much drama for cookies. A thing that has been made by grandmothers for many moons. 😂