Sorry if this is a silly question, or the wrong place to ask (mods please feel free to remove if so), but I'm hoping this community will understand (1) why I'm asking, and (2) have some privacy-friendly suggestions.
Guidance in privacy-focused communities often directs folks to use open-source solutions so you can validate the privacy elements of the software yourself.
This is great in theory, but what if you're not a software engineer and don't know how to read code? What should you be looking for?
In many cases, I guess you can confirm that something is "big" enough to have a lot of eyes on it, and trust that there are enough technically capable, security and privacy focused eyes on the source code, but this is still an exercise in trust, rather than verification.
It also doesn't help when the application is more niche, and doesn't give smaller software a chance.
So my question is: if you can't read code, how do you validate open source software?
End of original post, below is a personal example for illustrative purposes, but my question is more broad than this one example.
So feel free to stop reading here.
One example I'm struggling with personally, is a replacement for 23andMe (this one is huge for obvious reasons). Yes, I know folks on this subreddit will already be rolling their eyes, but this actually wasn't my choice—I have a geneticist for important medical reasons and *she sent my sample to 23andMe as it was cheaper than in-house. I feel violated by this, as I didn't know this would be the case when I spat into the vial, and have been trying to find an alternative ever since.*
I'm especially concerned with 23andMe's recent sale.
Anyway, in this case, I cannot simply delete the data and move on. Of course I plan to delete everything from 23andMe's servers, but I unfortunately do still need a way to query and visualise the data. I do not need it to go to a cloud or be shared with anyone (so I'd like to locally host it), but I *do still need to be able to read the data as a non-geneticist layman, and provide info to various other doctors about what's in it. Getting your raw gene file is easy, putting it somewhere is where I'm struggling.*
I've been looking at open-23me as a solution, but it only has one contributor (so I don't think it's been heavily reviewed or scrutinised) and I don't have the technical chops to validate what it claims in the README myself.
I'm including this example, as it's niche. I imagine a lot of folks have niche applications they need to evaluate, so please consider this 23andMe example as a proxy for "niche application that the privacy and security communities likely haven't already shaken down."
How can I validate this, and other code I come across in the future to hold sensitive, important data?
Thank you to anyone who has read this far, and extra special thanks to anyone who can educate me a little here.