Following on from my last post about Dropbox changing my photos, I noticed a new exif field of “Image Unique ID” embedded by Dropbox in the image.
This ID would allow Dropbox to track unique files across their storage estate to avoid duplication. Equally it could used to track the original file and who uploaded it from a cropped version posted online, especially if law enforcement turned up with legal papers and demanded access.
Think about leaked documents or protest photos, yes it’s good practise to strip the meta data out but not everyone does.
This again comes back to what Dropbox and it’s camera upload feature is doing and is it documented anywhere?
Note Google Photos does not embedded any tracking data in the exif of the image I tested by uploading and downloading it.
The hash for IMG_7082 is 8af323e74def610b0000000000000000 which looks like a 128bit hash but with only the first 64 bits populated. I’ve tried a number of hash tools on various parts of the original but they don’t match the unique ID. I have tested just the pure image data from original and Dropbox modified images.
Reverse engineering the hash function isn’t the real issue here, the real question is why has this ID been added?