Great idea! I created an adjacent website that gives, shall we say, "alternative facts" about your questions. (don't know if the rules allow me to link the site so I won't).
Currently, I'm not sure if my and my loved ones' info will be up for grabs at some point to a hacker. How do you make sure that it's encrypted/secured on your end? Are the uploaded documents saved on your server or only transient while the inference is occurring?
If the ToU and Privacy Policy are available before download, it'll make it much easier for people to join. What are your promises to the user that you will NOT sell their data, etc.?
Please understand that I'm not implying that you, per se, are being underhanded, just saying out loud the questions that come to my mind.
The point about assembly programming v/s programming at all really resonated with me. Yeah, we've come a long way since punch cards and we shouldn't reminisce about them in a way that stops us from creating the products we want to create!
Some things that came to mind that you could fix quickly if you want to: You gotta publish bullet-proof privacy policy and terms of use. You also need to disclose what underlying API you're using (Anthropic, OpenAI, something else?). I'd personally stay with US API providers because of their strong "no using your data" policies. However, that could change at any moment, so you have to be careful.
Positives: Looks great! The use case particularly resonates with me, but that's not everyone's cup of tea.
Suggestion: Instead of me having to ask questions, the app should surface divergent metrics on its own. That's the unlock imho!