CalcLockAt a glance: Verify the file you will actually attach. A setting on the original photo or a test through a different sharing route does not establish what your recipient receives.
Define what the recipient needs
Start with a specific audience and purpose: a buyer needs to see the item, a relative wants a portrait, or a colleague needs a reference image. Decide which supporting information belongs with it. Capture time may be useful; a home location or a revealing filename may not be.
Make a short list of the fields you want excluded. This turns an open-ended privacy worry into a check you can perform. Do not label a file clean merely because one location field is blank while leaving captions, visible addresses, and other identifying context unreviewed.
Prepare a separate outgoing copy
Keep the original intact and create a clearly identified sharing copy outside the vault. Finish cropping and other visual edits first so you do not inspect one version and later attach another. Use a neutral filename that still lets you recognize the intended image.
In iPhone Photos, review Options in the share sheet. Apple describes location controls and an All Photos Data option that can include the original, metadata, and edit history on supported sharing routes. Leave extra original data out unless the recipient actually needs it. Available options depend on the route and software version.
Inspect the saved file, not only the library entry
Save the prepared copy to a location you control and open that file directly. On a Mac, Preview's Inspector can show general image information and additional metadata, including location when present. Review the fields it exposes and compare them with your exclusion list.
A missing field in one viewer is not a forensic guarantee that no other metadata exists. For higher-consequence material, use a trusted metadata inspection and removal workflow appropriate to the format, or get qualified help. Do not upload a private image to an unfamiliar inspection website just to find out what it contains.
Test the transfer route without another recipient
For an unfamiliar workflow, start with a harmless sample and transfer it between your own devices or save it through the same route you intend to use. Open the received file and inspect it again. Check whether the filename, date fields, and location match your expectations.
An email attachment, an album link, and a messaging-app image are different paths. A result from one does not prove the others behave identically. If your destination offers a downloadable attachment preview before sending, inspect that exact attachment without publishing or sending it merely as a test.
Look for information the metadata panel cannot flag
Zoom out and look at the actual picture. A house number, school logo, distinctive skyline, reflection, or a computer screen can disclose context even when GPS information is absent. Then check the message you plan to write; a caption can put back the location you removed from the file.
This is also a good moment to confirm the intended audience. A carefully prepared image can still reach the wrong person through an autocomplete mistake or an overly broad sharing link. Verification of the file and verification of the destination are separate final checks.
Attach only the checked version
Move the checked copy into a small outgoing folder, or otherwise keep it distinct from originals and earlier attempts. Select that file deliberately, verify the attachment name, and review the final preview. If you replace the image, change export settings, or switch sharing methods, repeat the relevant checks.
Keep a brief note of the preparation method when you will repeat it, but avoid recording sensitive metadata unnecessarily. Software behavior can change, so a saved checklist should prompt a fresh inspection rather than become a permanent assumption that every future attachment is safe.
Questions, answered
Does turning off Location remove every kind of metadata?
No. It addresses location sharing in that workflow, not every possible field or visible clue. Inspect the actual outgoing file and review filenames, captions, edit-history options, and the image itself.