[benvan]

Thanks for the feedback!

Regarding privacy-first - we're striving to do a good job at this so really appreciate opening up the conversation. We don't actually store consents on our server - unless you enable "logged in mode" as a Metomic customer. When this is the case, you can generate a JWT for your customer that we then use to store a record of their consent serverside.

However for most of our customers, we operate in "anonymous mode", where consents are stored on the browser only. The only thing we do is store an incremental counter on the server that allows companies to see which policies are being accepted and which are not. Whilst we're all figuring out how to be more equitable with users as companies, it's extremely helpful to know when a change you make to a policy is something that people don't support (i.e. reject) - and our dashboard shows you this information

We actually have a community slack channel dedicated towards discussing exactly this type of thing - please do join if you'd like to chat!

https://join.slack.com/t/metomiccommunity/shared_invite/enQt...

[ThePhysicist]

Well, I can't find a running version of Metomic on any of your reference sites (maybe you can point me to one), on your own site the script sends several GraphQL queries to your backend when I consent, and also communicates with that before I do (not sure if this is due to other scripts on the page not related to the manager).

Again, this is totally fine, I wouldn't call it "privacy first" though, as it does not systematically minimize information exposed to third parties.