ITIT Lunchroom
Privacy and Sensitive Data Handling
Spotting Sensitive Information Before You Share It
Learn to spot personal details on your screen or in your files, and pick a safer way to share, hide, or get help before they end up in front of the wrong person.
Before you share a screen or send a file, check whether it shows someone's personal details. If it does, hide them, take them out, or just describe what's happening instead of showing it.
Last reviewed 2026-06-17 by the IT Lunchroom Editorial Team. General guidance, not professional security or legal advice.
What you will learn
I can spot sensitive details and choose a safer way to explain or escalate work.
You'll come away able to spot personal details before you share a screen, send a file, or paste an example, and to pick a safer option, like showing just one window, blacking out the private bits, or simply describing the work instead.
data classification levelssensitive data typesscreen-sharing exposureredaction and minimizationdescribe-instead-of-showleast sensitive example
Sorting information by how private it is
Some information is fine for anyone to see, and some could really hurt a person if it landed in the wrong hands. Sorting it that way tells you how careful to be. Think of a few rough levels: stuff anyone can see (like a public web page), stuff that's only meant for your group (like a team's schedule), stuff that's private to one person (like a customer's phone number and email), and the most sensitive of all (like account numbers, health details, or someone's password). Where a piece of information falls is what tells you whether you can show it, share it, or need to keep it covered up.
What counts as personal or private
Private information is anything that could hurt a person or a company if the wrong people saw it. That covers a name attached to someone's record, their phone number, email, or account number, health or money details, passwords and login info, ID numbers like a Social Security number, and plans a company hasn't announced yet. Quick rule of thumb: if you wouldn't want it shown on a screen for everyone to see, treat it as private.
How this usually slips out
Most of the time it's an honest slip, not anything sneaky. You share your whole screen on a call, and a pop-up message, an open file, or a tab in the background flashes someone's private details. Or you attach a file, or paste in a real example, that carries way more than the moment actually called for. The mistake is almost always the same: showing everything when only a small, safe piece was needed.
Moments to slow down
Slow down when a screen, file, or example has real names, account numbers, health or money details, or anything you wouldn't post out in the open. A few other red flags: sharing your whole screen when one window would do, sending a whole file when a short summary would have been enough, or copying real, live details into a chat message or a help request. Each one is your cue to trim things down to the bare minimum first.
A simple habit you can reuse
Before you share, take a second to decide how private the information is. Then pick the option that shows the least while still getting the job done: bring it down to a single window or page, black out the private parts, or just describe what's going on in words instead of showing it at all. If you can't tell whether something is safe to share, stop and ask the person who owns that information, or whoever handles tech where you are.
A worked example
Say you need help with an error on a customer's record. Instead of sharing your screen with the whole record open, close the extra tabs, cover up the name and account number, and show only the error message, or just say "it won't save one record" with no personal details at all. You got the help you needed and kept the private stuff off the screen, which is exactly the point.
Practice and evidence
Practice lets you sort sample screens and files by how private they are, and pick a safer way to share, all without touching any real records.
Write a short note (keeping it private) that says what personal detail you spotted, the safer choice you made (show just one window, black out the private bits, or describe it), and who you'd ask if you weren't sure, without writing down the personal detail itself.
Common questions
Sorting information by how private it is helps you decide what?
How carefully to handle a piece of information before sharing it. Sorting information by how much harm it could cause tells you whether you can show it, cover it up, or need to keep it protected.
You need help with an error on a screen that also shows a customer's name and account number. What is the safer choice?
Share only the error message after hiding the personal details. Showing only what you actually need, with the private parts hidden, gets the problem solved without putting anyone's personal details in front of others.
When should you treat information as sensitive?
When you would not want it on a public screen. If letting it slip could hurt a person or a company, treat it as private, even if nothing on it says "private."
What should you do if you join a video call to get help and the fastest move is to share your whole screen, which currently shows an open record with a person's name, a chat preview, and several tabs?
Share just the one window the helper needs, close or shrink anything showing personal details, and turn off pop-up messages first. Sharing just one window, with the private stuff closed, gets you the help you need while keeping personal details off the call.
What should you do if you are writing a help ticket or a training example and it would be easiest to paste a real record, complete with the customer's name and account number, to show what happened?
Describe what happened in general terms, or use a made-up example with the real names and numbers swapped out, so the point still comes across without anyone's real details. A made-up or described example makes the same point without dragging anyone's real personal details into a help request or a note.
Make it stick
Do the hands-on version of this lesson, then create a free account to save your progress. Finish a whole track and you earn a shareable certificate you can add to a résumé or job application. No payment, no catch.