I'm going to guess that collecting / organising the data is a problem.
Data Protection laws, and I believe the GDPR is the same, aren't interested in just stuff you've got, for example if you write a blog, and you mention that you saw Jim at the weekend and his sister is apparently pregnant, these laws do not consider that you've got a database there with a single row ("Jim's sister" "Pregnant") which needs to be treated as PII and have Subject access requirements etc. You're not really collecting pregnancy status data about women, you just have a blog post.
Whereas if I build a scraper, and I search thousands of blogs and correlate stuff to build a Postgres DB with "Jim's sister" "Pregnant" as one of dozens of rows, that is the sort of thing these laws care about.
So I can imagine that likewise "Here are radio signals I am receiving" looks like public information, no big deal, whereas "Here is a database of records I gathered by studying the past 24 hours of radio signals" is different.
Data Protection laws, and I believe the GDPR is the same, aren't interested in just stuff you've got, for example if you write a blog, and you mention that you saw Jim at the weekend and his sister is apparently pregnant, these laws do not consider that you've got a database there with a single row ("Jim's sister" "Pregnant") which needs to be treated as PII and have Subject access requirements etc. You're not really collecting pregnancy status data about women, you just have a blog post.
Whereas if I build a scraper, and I search thousands of blogs and correlate stuff to build a Postgres DB with "Jim's sister" "Pregnant" as one of dozens of rows, that is the sort of thing these laws care about.
So I can imagine that likewise "Here are radio signals I am receiving" looks like public information, no big deal, whereas "Here is a database of records I gathered by studying the past 24 hours of radio signals" is different.