October 3, 2026 · 7 min read

Sharing Your Kids' Photos: What to Check in 15 Seconds

What a photo of a child gives away, what to check before you send it, and how parents, teachers and clubs keep sharing without the scare stories.

Grandparents want the photos. The class newsletter needs a shot from sports day. The team chat wants the match pictures. "Never post anything" is advice everybody ignores, because it is unlivable. What works is a short list you run every time, so the decisions stop being decisions.

What a photo of a child gives away

• A location, from GPS metadata: the house, the park you always use, the school gate.
• A routine, from a series. One photo is nothing. Twenty build a timetable — same uniform, same playground, same day each week.
• A school or club, from a logo on a jumper or a sign behind them.
• A full name, from a caption, a surname on a kit, a certificate held up to the camera, a label on a bag.
• An age and a birthday, from the picture and the words around it.
• A medical or personal detail the child never chose to share and cannot unshare in fifteen years.

Scale the response to the audience. A message to family is not the same act as a public post. Treating them identically is how people end up either paranoid or careless.

The fifteen-second check

• Look at the frame, not the faces. House numbers, street signs, school crests, address labels, a laptop screen with something personal on it.
• Read your own caption. The words usually give away more than the picture.
• Ask who can actually see this: a private group of relatives, a school platform, or the open internet. Three different audiences deserve three different files.
• Strip the metadata on anything going beyond people you know — especially anything sent as a file rather than posted through an app.
• For public posts, prefer photos from behind, from a distance, or somewhere unidentifiable. You keep the memory and lose the map reference.
• Ask the child, once they are old enough to have a view. Older kids often say no, and that is their call.

For teachers, clubs and anyone posting about a group

Publishing other people's children is a different job with different obligations. Be systematic, not careful-ish.

• Know your consent position before you take the photo. Most schools and clubs hold a list. Check it, and check it again every year.
• Keep names and faces apart. A photo with no names, or names with no photo, is a far smaller disclosure than both together.
• Never pair a child's full name with an identifiable location. That combination is the one that bites.
• Strip metadata on everything you publish. Club and school photos get downloaded, forwarded and reposted miles beyond the original audience.
• Downscale before publishing. Around 1600 pixels looks fine in a newsletter and is less useful to anyone doing something you would not like.
• Use the organisation's own platform where there is one. A closed system beats a public page for the same photo.
• Have a removal route. Someone will ask for a photo to come down, and "we don't really have a process" satisfies nobody.

What the platforms do and don't do for you

Most big platforms strip most metadata from public posts, so GPS is mainly a worry on the other routes: email attachments, chat files sent as documents, forum uploads, shared drives, and newsletters built from original files. Those keep everything. And stripping metadata does nothing about what is visible in the picture or written underneath it — which, as above, is usually the bigger leak.

There is also the tool itself. Uploading a folder of photographs of children to a website you know nothing about, in order to protect those children, is a bad trade. Skrubly's cleaner, compressor and background remover run entirely in your browser: read off your own disk, never uploaded, never stored on a server, never seen by anyone else. Prove it in a minute — load the page, switch the wi-fi off, clean a photo anyway. It works, because the file has nowhere to go.

Where that stops: the TikTok downloader sends the link you paste to our server and a third-party provider fetches the video server-side. Your files never travel, a public URL does. And the site is ad-supported and processes ordinary technical data such as IP address and pages visited, as the privacy policy explains.

Two habits worth more than any tool

• Turn off location for the camera app, or at least know whether it is on. A photo that never recorded coordinates cannot leak them, and you will miss the feature less than you think.
• Keep the sending copy and the keeping copy separate. Archive the full original with all its data if you like it; send a downscaled, stripped version. Two jobs, two files — conflating them is where most mistakes come from.