You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading some of the techniques used to anonymize data, I can tell that Audire and Songrec is clearly focused on privacy.
With that noted, it occurred to me that important information could be potentially deanonymized by Shazam, such as location or affiliation information, by matching Shazam request timestamps to streaming service request timestamps. If the music player's location or user is known, the Shazam client's location and possibly connections to other people may be deducted.
Now, I'm no security expert, but this does appear to be an unlikely threat, as it would require Apple to communicate Shazam history with other companies or vice versa. Nevertheless, it is something to keep in mind, and I figure this feature would be easy to implement along with issue #16.
The text was updated successfully, but these errors were encountered:
LeftyDextrous
changed the title
Add optional delay to Shazam requests
Request: Add optional delay to Shazam requests
Mar 24, 2024
LeftyDextrous
changed the title
Request: Add optional delay to Shazam requests
[Enhancement] Add optional delay to Shazam requests
Mar 25, 2024
Hello,
After reading some of the techniques used to anonymize data, I can tell that Audire and Songrec is clearly focused on privacy.
With that noted, it occurred to me that important information could be potentially deanonymized by Shazam, such as location or affiliation information, by matching Shazam request timestamps to streaming service request timestamps. If the music player's location or user is known, the Shazam client's location and possibly connections to other people may be deducted.
Now, I'm no security expert, but this does appear to be an unlikely threat, as it would require Apple to communicate Shazam history with other companies or vice versa. Nevertheless, it is something to keep in mind, and I figure this feature would be easy to implement along with issue #16.
The text was updated successfully, but these errors were encountered: