adding it to [libre] would entail adding it to the blacklist,
and would prevent anyone from using the original - goe-location
is not a freedom concern, but a privacy concern; so it would go
in [nonprism]

ah okay, so is it possible to get it put in nonprism instead? is there a process to go through or is this issue enough for it to be considered?

A better option would be to move the neutered geoclue2 from nonprism-testing into nonprism and then delete all the nonprism packages that are there solely to remove geoclue2.
This would greatly reduce the maintanance load and catch ant packages that feel the need to add geoclue2 in the future. The changes to neuter geuclue2 were minor config and compile changes (no code patches) and thus it's a pretty quick and simple package to maintain.

I was not aware of a neutered geoclue2 in nonprism-testing. I agree with that as the better option, as long as it doesn't break any packages that expect the normal geoclue2 to be available

It shouldn't break anything it's just geoclue2 compiled with a bunch of location services disabled at compile time and the mozilla-api-key nulled

It's probably out of date. I put it together a ways back and due to health reasons haven't had much time to look at it.

Yeah I don't actually see it here: https://www.parabola.nu/packages/?q=geoclue2

Where can I find the PKGBUILD?

You'd have to enable the nonprism-testing repo to see the package but as it is a bit date it's probably better just to pull the PKGBUILD from:

https://git.parabola.nu/abslibre.git/tree/nonprism-testing

If you look at issue #2620 You can faollow some of the original work on it.