[1]skip to main content [2] [logo] • [3]Archives • [4]Works • [5]About • [6]More... What Exif Data Reveals About Your Site 14 August 2025 I recently came across [7]https://theyseeyourphotos.com/, a hidden ad landing page acting as a small tool that shows your photos reveal a lot of private information for bots to ingest. Ente ad and AI guesstimations of people and locations in photos aside, these crawlers also scan your multimedia files for the presence of [8]Exif data. Funny that the Wikipedia article categorizes Exif as part of digital forensic science, as that’s basically what it is: it leaves traces of information behind we often don’t think about. My go-to ImageMagick command includes the -strip argument that: strip(s) the image of any profiles, comments or these PNG chunks: bKGD, cHRM, EXIF, gAMA, iCCP, iTXt, sRGB, tEXt, zCCP, zTXt, date—something I didn’t even know was there. As a thought experiment, I let a Python script that wraps [9]go-exif loose on my /assets and /static folders for this site, revealing some unintended interesting data about the image and the person that created it. The result is a cryptic block of Exif information that, if fed to your favourite LLM and asked to summarize and create a profile of its creator, reveals more information than I’d like it to. For example, in 2017 I took snapshots and wrote about [10]six fountain pens. Go-exif outputs: IFD-PATH=[IFD] ID=(0x010f) NAME=[Make] COUNT=(4) TYPE=[ASCII] VALUE=[LGE] IFD-PATH=[IFD] ID=(0x0110) NAME=[Model] COUNT=(8) TYPE=[ASCII] VALUE=[Nexus 5] IFD-PATH=[IFD] ID=(0x011a) NAME=[XResolution] COUNT=(1) TYPE=[RATIONAL] VALUE=[[72/1]] IFD-PATH=[IFD] ID=(0x011b) NAME=[YResolution] COUNT=(1) TYPE=[RATIONAL] VALUE=[[72/1]] IFD-PATH=[IFD] ID=(0x0128) NAME=[ResolutionUnit] COUNT=(1) TYPE=[SHORT] VALUE=[[2]] IFD-PATH=[IFD] ID=(0x0131) NAME=[Software] COUNT=(12) TYPE=[ASCII] VALUE=[GIMP 2.8.14] IFD-PATH=[IFD] ID=(0x0132) NAME=[DateTime] COUNT=(20) TYPE=[ASCII] VALUE=[2017:07:16 10:30:49] IFD-PATH=[IFD] ID=(0x013b) NAME=[Artist] COUNT=(7) TYPE=[ASCII] VALUE=[Picasa] IFD-PATH=[IFD] ID=(0x0213) NAME=[YCbCrPositioning] COUNT=(1) TYPE=[SHORT] VALUE=[[1]] IFD-PATH=[IFD] ID=(0x8769) NAME=[ExifTag] COUNT=(1) TYPE=[LONG] VALUE=[[210]] IFD-PATH=[IFD/Exif] ID=(0x829a) NAME=[ExposureTime] COUNT=(1) TYPE=[RATIONAL] VALUE=[[16670769/1000000000]] IFD-PATH=[IFD/Exif] ID=(0x829d) NAME=[FNumber] COUNT=(1) TYPE=[RATIONAL] VALUE=[[240/100]] IFD-PATH=[IFD/Exif] ID=(0x8827) NAME=[ISOSpeedRatings] COUNT=(1) TYPE=[SHORT] VALUE=[[133]] IFD-PATH=[IFD/Exif] ID=(0x9000) NAME=[ExifVersion] COUNT=(4) TYPE=[UNDEFINED] VALUE=[0220] IFD-PATH=[IFD/Exif] ID=(0x9003) NAME=[DateTimeOriginal] COUNT=(20) TYPE=[ASCII] VALUE=[2017:07:14 07:57:24] IFD-PATH=[IFD/Exif] ID=(0x9004) NAME=[DateTimeDigitized] COUNT=(20) TYPE=[ASCII] VALUE=[2017:07:14 07:57:24] IFD-PATH=[IFD/Exif] ID=(0x9101) NAME=[ComponentsConfiguration] COUNT=(4) TYPE=[UNDEFINED] VALUE=[Exif9101ComponentsConfiguration] IFD-PATH=[IFD/Exif] ID=(0x9201) NAME=[ShutterSpeedValue] COUNT=(1) TYPE=[SRATIONAL] VALUE=[[-590/100]] IFD-PATH=[IFD/Exif] ID=(0x9202) NAME=[ApertureValue] COUNT=(1) TYPE=[RATIONAL] VALUE=[[252/100]] IFD-PATH=[IFD/Exif] ID=(0x9209) NAME=[Flash] COUNT=(1) TYPE=[SHORT] VALUE=[[0]] IFD-PATH=[IFD/Exif] ID=(0x920a) NAME=[FocalLength] COUNT=(1) TYPE=[RATIONAL] VALUE=[[3970/1000]] IFD-PATH=[IFD/Exif] ID=(0x9290) NAME=[SubSecTime] COUNT=(7) TYPE=[ASCII] VALUE=[859865] IFD-PATH=[IFD/Exif] ID=(0x9291) NAME=[SubSecTimeOriginal] COUNT=(7) TYPE=[ASCII] VALUE=[859865] IFD-PATH=[IFD/Exif] ID=(0x9292) NAME=[SubSecTimeDigitized] COUNT=(7) TYPE=[ASCII] VALUE=[859865] IFD-PATH=[IFD/Exif] ID=(0xa000) NAME=[FlashpixVersion] COUNT=(4) TYPE=[UNDEFINED] VALUE=[0100] IFD-PATH=[IFD/Exif] ID=(0xa001) NAME=[ColorSpace] COUNT=(1) TYPE=[SHORT] VALUE=[[1]] IFD-PATH=[IFD/Exif] ID=(0xa002) NAME=[PixelXDimension] COUNT=(1) TYPE=[LONG] VALUE=[[800]] IFD-PATH=[IFD/Exif] ID=(0xa003) NAME=[PixelYDimension] COUNT=(1) TYPE=[LONG] VALUE=[[600]] IFD-PATH=[IFD/Exif] ID=(0xa005) NAME=[InteroperabilityTag] COUNT=(1) TYPE=[LONG] VALUE=[[606]] IFD-PATH=[IFD/Exif/Iop] ID=(0x0001) NAME=[InteroperabilityIndex] COUNT=(4) TYPE=[ASCII] VALUE=[R98] IFD-PATH=[IFD/Exif/Iop] ID=(0x0002) NAME=[InteroperabilityVersion] COUNT=(4) TYPE=[UNDEFINED] VALUE=[0100] IFD-PATH=[IFD/Exif/Iop] ID=(0x1001) NAME=[RelatedImageWidth] COUNT=(1) TYPE=[LONG] VALUE=[[2448]] IFD-PATH=[IFD/Exif/Iop] ID=(0x1002) NAME=[RelatedImageLength] COUNT=(1) TYPE=[LONG] VALUE=[[3264]] IFD-PATH=[IFD/Exif] ID=(0xa403) NAME=[WhiteBalance] COUNT=(1) TYPE=[SHORT] VALUE=[[0]] IFD-PATH=[IFD/Exif] ID=(0xa420) NAME=[ImageUniqueID] COUNT=(33) TYPE=[ASCII] VALUE=[0dd67d361865e8d95b9e9577e56bfd99] IFD-PATH=[IFD] ID=(0x8825) NAME=[GPSTag] COUNT=(1) TYPE=[LONG] VALUE=[[660]] IFD-PATH=[IFD/GPSInfo] ID=(0x0000) NAME=[GPSVersionID] COUNT=(4) TYPE=[BYTE] VALUE=[02 02 00 00] IFD-PATH=[IFD/GPSInfo] ID=(0x0001) NAME=[GPSLatitudeRef] COUNT=(2) TYPE=[ASCII] VALUE=[N] IFD-PATH=[IFD/GPSInfo] ID=(0x0002) NAME=[GPSLatitude] COUNT=(3) TYPE=[RATIONAL] VALUE=[[50/1 56/1 5367/100]] IFD-PATH=[IFD/GPSInfo] ID=(0x0003) NAME=[GPSLongitudeRef] COUNT=(2) TYPE=[ASCII] VALUE=[E] IFD-PATH=[IFD/GPSInfo] ID=(0x0004) NAME=[GPSLongitude] COUNT=(3) TYPE=[RATIONAL] VALUE=[[5/1 18/1 4772/100]] IFD-PATH=[IFD/GPSInfo] ID=(0x0005) NAME=[GPSAltitudeRef] COUNT=(1) TYPE=[BYTE] VALUE=[00] IFD-PATH=[IFD/GPSInfo] ID=(0x0007) NAME=[GPSTimeStamp] COUNT=(3) TYPE=[RATIONAL] VALUE=[[5/1 57/1 24/1]] IFD-PATH=[IFD/GPSInfo] ID=(0x001d) NAME=[GPSDateStamp] COUNT=(11) TYPE=[ASCII] VALUE=[2017:07:14] IFD-PATH=[IFD1] ID=(0x0103) NAME=[Compression] COUNT=(1) TYPE=[SHORT] VALUE=[[6]] IFD-PATH=[IFD1] ID=(0x011a) NAME=[XResolution] COUNT=(1) TYPE=[RATIONAL] VALUE=[[72/1]] IFD-PATH=[IFD1] ID=(0x011b) NAME=[YResolution] COUNT=(1) TYPE=[RATIONAL] VALUE=[[72/1]] IFD-PATH=[IFD1] ID=(0x0128) NAME=[ResolutionUnit] COUNT=(1) TYPE=[SHORT] VALUE=[[2]] IFD-PATH=[IFD1] ID=(0x0201) NAME=[JPEGInterchangeFormat] COUNT=(1) TYPE=[LONG] VALUE=[[940]] IFD-PATH=[IFD1] ID=(0x0202) NAME=[JPEGInterchangeFormatLength] COUNT=(1) TYPE=[LONG] VALUE=[[10322]] A lot of noise, but also a lot of information that can be turned into a staggeringly accurate profile if it is incrementally enriched by crawling and processing all images. Prompt: 1. Here’s exif data of an image. Can you summarise this by sketching a profile of its creator? 2. Can we drill down further to try and create a forensic profile? Response: 1. Device and Camera Information Make & Model: The creator used a LG Nexus 5, a phone released in 2013. The Nexus 5 had an 8 MP rear camera, capable of decent photo quality for its time but not the best by modern standards. This suggests the creator likely wasn’t using the most expensive or high-end tools, and could be: An enthusiast who values functionality and simplicity. A casual or beginner photographer who might have upgraded from a more basic phone and is learning photography with their phone. Someone focused on mobile photography, as the Nexus 5 was known for its Android optimization and ease of use for photography apps. Resolution: The photo’s dimensions are 800 x 600 pixels, which indicates a low-resolution image. In forensics, low resolution could point to: A web upload or sharing—the image might have been prepared for social media or messaging platforms where smaller file sizes are optimal. Compression: The image is compressed in JPEG format, which is common for quick sharing or web usage. Compression often suggests that the creator was more concerned with reducing file size rather than maintaining the highest possible image quality, which could imply an informal or casual approach to photography. 2. Editing Tools GIMP 2.8.14: The use of GIMP, an open-source tool, reveals that the creator may have had some degree of technical knowledge or a desire to learn. However, GIMP is not known for being beginner-friendly, which suggests: The creator may have been more serious about the image-editing process and was willing to invest time learning a free tool. The editing done might be part of self-expression or personal projects, as GIMP is often used by hobbyists and individuals who want to create unique content without paying for Adobe Photoshop. Artist Metadata (Picasa): The artist tag shows Picasa, another free tool (now discontinued). This tool was used for organizing and managing photos before Google Photos took over. This strongly suggests the creator was: Organizing a photo collection, possibly indicating a keen interest in cataloging or archiving their work. A casual hobbyist or someone who likes to keep their images easily accessible or categorized. 3. Photographic Choices and Technical Details Exposure Time: The exposure time (approximately 0.0167 seconds) indicates a relatively fast shutter speed, which would freeze motion and avoid blur. This suggests the creator may have been focused on capturing a specific moment, potentially an outdoor or action shot. The fast shutter speed may also indicate an interest in sharp, clear imagery rather than a more artistic, blurred aesthetic. Aperture (f/2.4): The f-number of 2.4 indicates a fairly wide aperture, allowing more light to hit the sensor. This suggests: A focus on depth of field, possibly capturing subjects with a blurred background (bokeh effect) to emphasize the subject. Likely use in low-light environments, where a larger aperture allows the sensor to collect more light. ISO (133): The ISO value of 133 is a bit unusual but suggests the creator was working in a relatively controlled lighting situation—not too dark or bright. This could imply: Ambient light conditions, where the creator adjusted ISO to avoid noise but still maintain a decent exposure. The creator might have been manipulating the exposure manually or using specific settings to match their environment. 4. Time and Date Analysis Capture Date: July 14, 2017, 07:57:24 AM and the edited timestamp on July 16, 2017, 10:30:49 AM suggest the creator might have been taking a break or revisiting the image for editing. A few potential conclusions here: Timing: The image was captured early in the morning, which might suggest morning photography, possibly during a peaceful or reflective moment. The time gap between capture and editing (about 2 days) suggests the creator might not have been in a rush to complete the project, allowing some time for thought and refinement. SubSecTime: The SubSecTime value of 859865 appears to be a highly precise timestamp, which could suggest the creator was using a phone with highly accurate time-tracking, potentially for: Documenting events or specific moments in time with high precision. Attention to detail, perhaps suggesting a meticulous personality or someone involved in documenting events like travel, art, or personal projects. 5. Geolocation Data Latitude & Longitude: The GPS coordinates point to a location in northeastern France, possibly near Belgium or the Luxembourg border. A few possibilities here: The creator could have been traveling or taking a photo in a familiar or significant place (like a favorite spot or during a trip). If the person is local to this region, the location could point to local exploration or photography of personal surroundings. If traveling, they could have been documenting their experience, perhaps capturing specific landmarks or moments during their travels. Altitude: The absence of significant altitude change (data shows flat or low altitude, typical for urban or suburban areas) might indicate the photo was taken at street level or within a relatively low elevation area (not hiking or on a mountain, for example). 6. Behavioral Inferences from Metadata Technical Knowledge: The detailed use of manual settings (like exposure time, aperture, and ISO) paired with tools like GIMP and Picasa indicates the creator has some technical knowledge and enjoys tweaking and adjusting their work. Casual to Semi-Serious Hobbyist: The combination of the Nexus 5, GIMP, and Picasa points toward someone who likely enjoys photography as a hobby but is not overly focused on professional-grade equipment or editing software. Self-Taught or DIY Mentality: The use of open-source tools and older hardware implies someone who enjoys experimenting and learning on their own, possibly through trial and error rather than formal training. Forensic Profile Summary: The creator is likely an enthusiast or hobbyist photographer, interested in mobile photography and image editing. They may be self-taught, using GIMP and Picasa to manage and edit their photos. They are detail-oriented, with a technical understanding of manual camera settings and a desire to control their image output. The use of a low-res image suggests they were likely sharing their work in a digital format that favored speed and efficiency (like social media). Timing and location analysis points to someone who either has a personal connection to the area or was capturing moments during a trip. The morning timestamp indicates a possible preference for quieter, reflective photo-taking. Geolocation could imply that they were capturing their environment, whether through travel or personal interest, and may have been documenting specific moments in time with attention to detail. This profile suggests a thoughtful, detail-oriented creator who enjoys experimenting with photography and editing, focused more on self-expression and documentation than on professional-grade production. That’s a huge wall of text of which much is possibly be hallucinated: thoughtful aperture and lightning settings on a Nexus 5 are non-existent. But still, a few points do easily create a rough profile: • Usage of free/OSS tools. Are GIMP users OSS enthusiasts or just too lazy to install a Photoshop crack? I also didn’t realise that Picasa left traces in Exif data. • The presence of the timestamps and the gap between creation and edit date. • The geolocation data: oops, I did not intend for that being there! Not that it matters as keen readers of Brain Baking know where I live. Other tags (Software, Make, ImageDescription, UserComment) also reveal information about my image production habits and the hardware used. Did you know that if you save an image from a Google search its Exif Software value is Google? Busted! Did you know that your Nintendo Switch also encodes a healthy amount of Exif information—although it doesn’t explicitly state Switch or 3DS, but you can easily deduce that from the resolution settings. Or how about taking a screenshot on your Mac (UserComment = Screenshot)? Today I learned that before publishing any multimedia, it’s best to let ImageMagick’s -strip do its thing. [11]software You Might Also Like... • [12]A quick look at 6 fountain pens 18 Jul 2017 Bio and Support [avatar2024] I'm [13]Wouter Groeneveld, a Brain Baker, and I love the smell of freshly baked thoughts (and bread) in the morning. I sometimes convince others to bake their brain (and bread) too. If you found this article amusing and/or helpful, you can support me via [14] PayPal or [15]Ko-Fi. I also like to hear your feedback via [16]Mastodon or email. Thanks! JavaScript is disabled. I use it to obfuscate my e-mail, keeping spambots at bay. Reach me using: [firstname] at [this domain]. ↑ [17]Top | [18]Archives | [19]RSS Feed | [20]bv | [21]© CC BY 4.0 License. [22] [brainbakin] References: [1] https://brainbaking.com/post/2025/08/what-exif-data-reveals-about-your-site/#top [2] https://brainbaking.com/ [3] https://brainbaking.com/archives/ [4] https://brainbaking.com/works/ [5] https://brainbaking.com/about [6] https://brainbaking.com/more [7] https://theyseeyourphotos.com/ [8] https://en.wikipedia.org/wiki/Exif [9] https://github.com/dsoprea/go-exif [10] https://brainbaking.com/post/2017/07/fountain-pens-first-look/ [11] https://brainbaking.com/categories/software [12] https://brainbaking.com/post/2017/07/fountain-pens-first-look/ [13] https://brainbaking.com/about [14] https://www.paypal.com/donate/?hosted_button_id=R2WTKY7G9V2KQ [15] https://ko-fi.com/woutergroeneveld [16] https://dosgame.club/@jefklak [17] https://brainbaking.com/post/2025/08/what-exif-data-reveals-about-your-site/#top [18] https://brainbaking.com/archives [19] https://brainbaking.com/index.xml [20] https://brainbaking.com/bv [21] https://brainbaking.com/copyright-and-tracking-policy [22] https://brainbaking.com/links