>>LaLiga does not access the audio fragments picked up by the device's microphone, as they are automatically converted into binary code on the device itself. LaLiga only accesses this binary code
Audio fragments are a "binary code", usually pulse code modulation samples. In this case, JorgeGT's link[1] shows that the app is reading PCM data with Android's AudioRecord API.
If they mean that they are hashing or otherwise obscuring the data (which probably can be reversed or correlated to other data in some situation), they need to say that. This statement could be interpreted that they "only access this binary [PCM samples]", not the "[raw, analog] audio fragments".
>>If this code matches a previous control code
Maybe this is a translation issue, but they seem to be conflating "codes" representing audio patterns with identification codes such as "your IP address and the specific ID assigned by the PPP when you register". The last part also admits they are "referring to your name" that you used when registering. They are simply using a synthetic key as a proxy. This is confirmed by this function in the code[2]:
public void linkUserIds(String fluroId, String adId)
that sends a GET request specifically for the purpose of linking their "fluroId" to what is presumably some type of ad tracker id.
Audio fragments are a "binary code", usually pulse code modulation samples. In this case, JorgeGT's link[1] shows that the app is reading PCM data with Android's AudioRecord API.
If they mean that they are hashing or otherwise obscuring the data (which probably can be reversed or correlated to other data in some situation), they need to say that. This statement could be interpreted that they "only access this binary [PCM samples]", not the "[raw, analog] audio fragments".
>>If this code matches a previous control code
Maybe this is a translation issue, but they seem to be conflating "codes" representing audio patterns with identification codes such as "your IP address and the specific ID assigned by the PPP when you register". The last part also admits they are "referring to your name" that you used when registering. They are simply using a synthetic key as a proxy. This is confirmed by this function in the code[2]:
that sends a GET request specifically for the purpose of linking their "fluroId" to what is presumably some type of ad tracker id.[1] https://reversecodes.wordpress.com/2018/06/12/analizando-la-...
[2] Ibid.