Description of the issue:
First party pixel is blocked (has the same apex domain as the website)
Both pixel code (js) and collector domain are under the 2key.io apex domain.
I expected that cross-site tracking will be blocked, but this is not a third party pixel or a cross site tracker.
Does Brave or any browser has an exact definition of what is considered cross site tracking?
I don’t know the full details on what is parsed/not parsed, but its at least taking the generic blocks in Easyprivacy. While not “cross-site” in this case, its tracking the user and should remain blocked. I do agree we should adjust the wording on this to avoid confusion.
What is allowed to be sent?
Is there a list of actions that are allowed?
for example:
a page view
an event
I am talking only about the action itself, not the rest of the parameters that are being collected by the script.
Any documentation I can take a look at?
is the EasyPrivacy.txt list enough?
There is still a lot of grey, undefined area (At least for me).
It would be nice, and time-saving if there would be any developer docs for these kinds of issues.