I think the idea is a great one, it's unfortunate there isn't a better way (that I can think of atm) to do it, or like you said just some transparency on what they do with it. As simple as: "At the end of each day the encrypted mac addresses are completely erased from our system."
Seems like they do keep the info though, it says the Cincinnati airport kept it and used it for data analysis. In the end, I think this kind of thing most people will be okay with foregoing a bit of privacy for.
Edit: Interesting article on mobile MAC addresses down the comments: https://news.ycombinator.com/item?id=10097882#up_10098108
That doesn't make either situation okay for privacy-conscious people like you and I, but I personally feel like MAC address tracking is a relatively minor concern when it comes to privacy.
Blip, you make me laugh. You know this will raise privacy concerns and say the sweet nothings that placate the general public, but inspire no confidence in people who know what those words mean.
I'm not here to say that as a JFK traveler I'm unhappy with the privacy considerations. I just want to point out you're pretending your design is good on privacy when simple tweaks would show the security minded you gave half a shit. I don't mind this monitoring if it is limited to the uses described, your maneuvering simply makes me giggle.
A MAC may not be in whatever bucket you're calling "personal" but is certainly more personal than "non-personal" implies. Encryption is effectively a "we're doing it right" buzzword to the general public. What are your authorized uses for the data? What's your KMI? What data minimization techniques are employed? Do you purge old records? Replace the MAC with an identifier that can't be tied back to MAC once the target has left the line? Hash MACs on entry in a way that is both time-costly to bruteforce and results in a different hash every day?