If you administer a free service that takes an hour a month to keep running, and suddenly you're faced with an immediate upfront time cost plus the likelihood of spending many more hours every few months responding to user requests, shutting your service down might be a rational decision when you would otherwise have kept it running.
However, I felt the need to comment on the assumption that an application that is only 5 years old would imply that it uses a tech stack that no one would care about.
How is it that after a quarter of a century of web development, that the state of the software used is so bad that people still assume that something that is a few years old is assumed to be useless?
Five years ago I was messing around with Fortran 2008. Having done so, it's not as interesting anymore. That's not a function of Fortran, which was created when my grandparents were 20-somethings, but of the time spent with it.
So the owner might be making an excuse, yes, but I don't blame them as it seems like a legit way out if they wanted to close up.
Number 2 could be an "email me if you want your account removed". This will trigger like two emails a year, and you just run a DELETE FROM command. If it becomes more, you make a page.
For numbers 3 and 4, see number 2. I expect that this won't be much either.
The page doesn't mention a single thing that would be a good reason to quit over GDPR. I think the author was looking for a reasonable-sounding exit, especially since he was operating at a loss (and apparently cared about it, since he was cooperating with Amazon to begin with).
What were the previous data protection laws in the UK anyway? In the Netherlands, none of the 4 points above are new. Our data protection law from 2001 also required all of this.