Isn't that a problem, like "let's get rid of Google and all the evildoers because they know too much about us" then "oh we realize we created another one which knows too much about us"?
I get where you're coming from, and this is something I've been thinking a lot about.
It would be possible to not save the map, and then use some kind of hashing to infer user ids for each site. I chose not to do this, to be able to guarantee no collisions. This might be silly, though. But the thought of people with colliding user ids makes me giddy.
The data stored looks something like this:
{
"ids": {
"example.com": {
"07c5c163-875f-424c-a659-a4f99e74eb12": "default"
},
"other-example.com": {
"ab38b2a6-d560-43d3-b2a3-9148cd91d1b4": "default"
}
}
}
Worth noting is, that there is no personally identifiable information (PII) here.
But we have to have the discussion if this is "too much" data to keep about a user. AFAIK this is the bare minimum of data needed, to be able to guarantee no collisions of user ids. If there is another way to do it, we should do that!
