Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataPath: Filters that stop a discovered value from being considered an instance of the respective property #46

Open
baltpeter opened this issue Sep 11, 2023 · 1 comment
Assignees

Comments

@baltpeter
Copy link
Member

baltpeter commented Sep 11, 2023

Sometimes, a tracker will transmit something like idfa: none. Currently, this would be detected as an IDFA transmission, which is obviously wrong.

I think we'll need filters to prevent that. Maybe it's easiest if we can either specify a positive (onlyIf: \d+) or negative (notIf: none) regex?

@baltpeter
Copy link
Member Author

One question we still have to discuss: Do we want to filter out transmissions like idfa: 00000000-0000-0000-0000-000000000000? For my research, I always considered them as IDFA transmissions since the app/tracker was clearly trying to transmit this information but just happened to not succeed because the OS blocked it.

But in the context of TrackHAR, I'm leaning towards a stricter definition of a transmission. Legally speaking, I'm not sure whether trying (and failing) to read information from a user's device would trigger Art. 5(3) ePD. But in any case, we cannot claim that an ID was transmitted if the "ID" was just zeros. And we do always say that we would rather under- than overmatch.

baltpeter added a commit that referenced this issue Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant