Bit of an existential question, but in terms of all the thousands of database schemas, there is usually justification to keep the record after a person’s death, even allowing for the possibility of fraudulent use of id. Unlike physical media, most of these datasets are considered ‘live’ data (Ironic terminology), but sometimes there can be a delay in that propogating to all copies. For example, a company will often send a copy of a contact list to a mailing house that might take a month to complete their process - generally the company wouldn’t be expected to issue a redaction.
On a technical level, it’s normally done with something like a DateOfDeath column that is null, or a boolean IsAlive/IsValid.
For less official datasets where governmental protections don’t override it, GDPR and similar laws may come into play where - unless you have a clear and stated justification for keeping the data for a limited time after your company’s relationship with that person has ceased (called ‘Legitimate interest’) then you MUST delete that data and all references to it.
But yes, fraud exists in all the ways you can think of and a lot more too. People claiming a dead relatives’ benefits, or getting credit using fake details - it’s obviously illegal and there are consequences.
Solid.
I like that you’ve done what I’ve done - considered what’s actually worth backing up and what can be replaced. So many people when selfhosting don’t make that distinction and get overwhelmed when they try to back up /everything/ - so much so they don’t bother, or half-arse it. (No 3-2-1, no periodic restores to test, no offsite or what-ifs etc)
Making that plan to save what’s important reduces the burden hugely.