The dev explains them all here and the justifications make sense, although they may be able to update them to finer grained permissions now, but I haven’t kept up with android development in recent years (it’s in docs/Privacy-Policy.md in their Github repo, for some reason I cannot post links to Github anymore)
I’ve been using keepass2android for nearly a decade, although I do admit it is starting to show it’s age, KeePassDX is under more active development and has a more polished interface and smoother interactions. I was merely curious if there were any other technical merits I may have missed.
To be more specific, I don’t care if my database is exposed at all, I need to sync and back it up it afterall. It is the key file I use to unlock it (combined with password) which I want to keep isolated from everything else.
This sounds like a neat feature, however I stopped using custom roms ages ago, and prefer the simplicity and security of stock android on my pixel phone, privacy from Google is of low priority for me personally.
Thanks! This is exactly the type of app I’ve been looking for, and may consider looking into it at some point if I have time, depending on how the development of both apps continues.