> This list is an aggregation of public layoff lists where people voluntarily signed up, plus people who sign up through us.<p>You should be actively getting the consent of these people on these lists. They consented to have their info in lists created and shared by colleagues, not as part of your service.
Not trying to poop in the cereal, but take a beat before adding your name to the site; I'd be wary that this will be used to blacklist a whole lot of folks. There's a large segment of tech that doesn't see a tenure at Twitter as a positive, for example. Maybe consider hiding the company name.
This is an awesome tool and a great service you are providing!<p>One note of feedback: When I first loaded the page, all I saw were listings from Starry Internet, and when I reloaded it was just Lyft. This makes it look like you only have people from one company.<p>My suggestion would be to randomize the listing on each page load (or even bias the list towards diversity of company and role). Then people can see the depth of the people signed up and start exploring filters.
Layoffs don't suck, layoffs are great.<p>It's a quick, guilt-free way to get out of a dead-end situation without having to spend a multi-week notice period writing documentation, handing over, and pretending you'll be lifelong friends with a group of people you are sick of that don't have your back.
If I was running a successful tech company, these layoffs would be a godsend. Plenty of amazing devs let go simply to lower headcount costs. I'd be poaching this list ASAP!<p>And please, use this time to sharpen your skillset! You'll be back in the grind before you know it, so don't let this little vacation pass you by.
So recruiters can contact you? That’s called having a LinkedIn or an email address on github.<p>Recruiters are the ones being laid off the most aggressively anyway.
The data may be publicly available, but GDPR still applies, AFIAK. <a href="https://www.technologylawdispatch.com/2019/04/privacy-data-protection/processing-publically-available-personal-data-without-telling-data-subjects-the-polish-data-protection-authority-has-bad-news-for-you/" rel="nofollow">https://www.technologylawdispatch.com/2019/04/privacy-data-p...</a><p>"The main takeaway is for companies that process personal data gathered from public sources to tread carefully. Be mindful of your GDPR article 14 notification obligations. Be sure you document your processing decisions, particularly if you decide not to inform affected individuals how you process their personal data. And most importantly, be prepared for regulatory scrutiny and engagement."
You are going to get completely fucked by GDPR if you're scraping and rehosting people's personal data. This is not cool at all.<p>I recommend you shut this down immediately and email everyone on the list to apologise.