Batch removing personal data (inc hidden email) from iTS files 2010-05-21 18:33:10 iTunes Store files, whether iTunes Plus or ye olde 128 kbps (from before Apple stopped DRMing their audio files), contain additional metadata related to the purchase, including personal information such as the user's name and email address.My purchased files won't be going anywhere that'll make this an issue, but I see the inclusion of such information as pointless and so would like to remove it. Also, "Files with no email address inside sound superior." Call this a waste of energy, but I think it slightly less illogical than another idea suggested here recently. In the case of the 128 kbps files (which, in case it affects the ability to edit metadata, are stripped of DRM), removing all atoms besides the metadata I want to retain (using AtomicParsley) seems to do the trick. However, processing a Plus file in this way, and then checking the result with iTunes and a hex editor, reveals that my email address is still there somewhere. Even AP's charmingly-named --metaEnema option doesn't get rid of it.* The only method that I found was to totally remove the MP4 container (and add a clean one).So, I'd quite like a way to batch-process all of my purchased files (of both types) to remove all purchase information. It's probably far from optimal, but I threw together a proposed solution, which entails the following:A: 'Store' all desired metadata in filename (using foobar2000)B: Extract the raw AAC audio (MP4Box)C: Add a clean container (MP4Box)D: Tag the new M4A/MP4 file (foobar2000).In theory this shouldn't be too difficult; however IIRC in my brief tests it worked fine for a number of files, but then began to act strangely, for an unknown reason.So… Does this look about right? Does anyone have any advice, suggestions, improvements, etc.? Has anyone else even noticed and/or cared about this? Thanks.* Perhaps of interest to users here (and continuing the colonic theme) is its option --foobar2000Enema, which apparently "Eliminates foobar2000's non-compliant so-out-o-spec tagging scheme".