Usual note that IANAL, but looks like this service is opt-in, and only relists data which is already public on a user's HN profile. If a user removes the refer

Usual note that IANAL, but looks like this service is opt-in, and only relists data which is already public on a user's HN profile. If a user removes the reference from their bio, then the user's profile will be essentially inaccessible through the service (although technically the cached version would still be on the server. Adding a check to delete the file which matches the user's hashed ID here[0] would take care of profile deletions on subsequent accesses. Failing all that, a user could request deletion and OP could delete the user's file manually. There's nothing that seems overly onerous to implement to be (at least) GDPR compliant. [0]https://github.com/padolsey/at.hn/blob/d4ca6702c558edf73665210d2525ddd31d552031/server.mjs#L207 https://github.com/padolsey/at.hn/blob/d4ca6702c558edf736652...