|
|
|
|
|
by pzo
1116 days ago
|
|
The idea would be not to store those data on server only process it and keep anonymous data or even only aggregated.
Some processing maybe could be done also on the client or payslip user name masked after verifying it matches passport holder locally before sending to server. Other option using blockchain with open source repo. I know a lot of HN users are in theory very distrustful about anything new but in practise still: - using VPNs (even paid one don't guarantee your data is safe) - tor - open source password managers (w/o reading source code) - Dropbox etc - compiling random open source code first without reading - having no issue telling hour rate or daily rate recruiter on linkedin when asked and attaching resume. So what's so very sensitive in payslip if you already providing this kind of information to any recruiter? |
|
Domestic violence victims who are trying to avoid being found? People seeing political asylum? Anyone who wants to maintain privacy? There's a number of reasons you would not want this information in pastebin.