just to clarify, this is a 3rd party developed tool that helps to get notifications resulting from updates to observations such as identifications and comments.
i don’t think you’re doing anything wrong yourself, but i do think there is something wrong in the workflow. however, because it’s such a small problem (just a suboptimal workflow, not an actual security issue, as far as i can tell), i haven’t spent much effort trying to track down the source of the problem. i suspect it’s somewhere in iNat’s implementation of their authorization process, but it would be hard for me to troubleshoot that without setting up a development instance of the iNat system. see https://forum.inaturalist.org/t/previously-authorized-3rd-party-apps-still-require-reauthorization/43045 if you’re interested in more details.
the parameters at the top of the page are all the filter parameters made available by the iNat API. so any additional filtering would have to happen via some kind of second pass filtering (on the client side, rather than on the server side), which is technically possible but sort of ugly to do – so i’d be reluctant to implement something like that, unless there’s a compelling reason to do so.
however, the code for the page is public, and anyone with some coding skills is welcome to adapt it for their own purposes or to offer improvements to the code via the GItHub repository.
really though, the best solution should come when iNat finally releases the new notifications system that they’ve been working on, hopefully making this 3rd party tool obsolete. see https://forum.inaturalist.org/t/notifications-on-inaturalist-please-share-your-ideas/374/202.