But, now I’m trying to describe the main pain point, and it’s starting to feel like I built a solution without a problem. After all, does anyone else care so much about their users privacy that they would use this system and give up some of that user data? If not, and I have to change my marketing angle, doesn’t it become a solution in search of a problem?
If this is a tool you wish to sell/license/distribute, I think it might be worth taking a look at specific cohorts that would be interested in this -- namely, any business that takes a position that they care about their users should be using a more private analytic/telemetric tool - if using it at all. This is moreso true in the privacy sector but, in general, would probably relate to anything that gears more toward technically inclined users (who are aware of said data privacy issues).
It might be worth sharing usage of this to some of the privacy organizations/non profits [for free] and seeing if they would be willing to blog/talk about it to build awareness (which is reallllllllly important to help even come to a conclusion that this is fulfilling a need or is in search of a problem).
Often times we'll see companies (like amazon is an example) actually just make MVP stuff to simply see if anyone wants to use the product. Is that a solution in search of a problem -- I think more like a method of identifying whether ppl are looking for said solutions to problems.
There is a market for the product you’re describing. There are a few solutions out there. For example https://plausible.io/ — there are others.