Separating a fictional teacher's public and private social presence case

What to take away

This case is fictional. It describes no real teacher, school, platform, student, or family. Rules on conduct, records, and safeguarding vary by employer and province, so a working educator follows the institution's approved systems and the advice of its privacy lead.

The starting point

Maya Torres taught science at the fictional East Shore Middle School. One account held everything:

A search for her name returned her employer, her profile photo, her hometown, public comments, and a tagged photograph outside a neighborhood cafe. Her phone number was not public, but parents reached the account through uploaded contacts.

She wanted to publish general science resources, keep family updates inside a known group, and stop contact-based discovery where the platform allowed it. School records stayed in school systems.

The boundary table

Maya and the school's privacy lead wrote this before changing a single setting.

The table did the work that a vague intention cannot. It named the channel for each kind of message, so no conversation had to be sorted out mid-term.

The public professional profile

The professional profile carried her name, subject area, broad region, a school-approved biography, and a school contact page. It listed no home city, personal email, phone number, or birthday. It listed no family members or daily schedule.

Maya read LinkedIn's own explanation of public profile visibility, which shows how selected sections appear to signed-out visitors and search tools and notes that search updates lag. That page set up the test plan below. It is not the school's policy and it promises nothing about removal from search.

Every public post had to pass three questions:

A post that failed any question did not go up.

Cleaning the personal account

Maya removed followers she could not identify, including dormant accounts that may have changed hands. She built a family list, set new posts to that list by default, and reviewed older public posts one by one, because a new default does not rewrite the audience of anything already published.

She took her employer and hometown out of the personal biography and let the professional profile carry work context. She turned off contact syncing and used the stored-contact control to delete uploads already on file.

Tags, locations, and photographs

She turned on tag approval and removed the cafe tag from her profile. She asked the original poster to drop the location, because the photo showed a recurring family routine. She knew the tag was only an association: the photograph stayed on the poster's account either way.

The family agreed not to tag her at home, at school, or while traveling. Vacation photos went up after the return. Before posting, she checked for visible addresses, school logos, tickets, and licence plates. She stripped coordinates where the platform allowed it.

Messages and school records

A short line on the professional profile sent school matters to the approved school system. Student performance, attendance, disability, conduct, and family circumstances never moved through personal direct messages.

She did not copy old parent messages into the new profile. Where a record had to be kept, she used the school's retention and migration process instead of forwarding screenshots to a personal mailbox.

Two gaps the settings screen hid

A signed-out check showed the professional photo public, as intended, but an old comment of hers on a public community page still pointed at the personal profile. She edited the comment to remove identifying detail and left the community record intact.

A trusted nonconnection then found the personal account by email address. LinkedIn's page on profile visibility on and off the service separates public-profile reach, off-service visibility, and discovery by email or phone.

Maya limited email and phone discovery where the platform allowed it and repeated the test after the stated update period.

What six weeks produced

The professional profile stayed visible with approved fields only. The personal profile stopped appearing through the tested contact route, though known connections could still find it by name under platform rules. Family posts went to the maintained list. No school communication depended on the personal account.

The cafe photograph still existed on the original poster's account after the tag and location came off. The written record said so, rather than claiming the image was gone.

Keeping it current

Maya repeated the checks at the start of each term, after a role change, and after a major platform update, using the account inventory and deletion checklist as her running list.

The school-owned account stayed inside the school's access review.

The personal account stayed outside school administration, and she kept following the conduct and safeguarding rules attached to her role.

Common questions

Did Maya need two accounts?

No. Separation was her choice, because the professional and family audiences, contacts, and records served different purposes. A single account with tight audience lists can work if the boundary table is written first.

Could parents still find the professional profile?

Yes, and that was the point. It was public by design and routed school matters to an approved channel. A public profile is not a leak when its fields are chosen deliberately.

Did removing the tag delete the cafe photograph?

No. It broke the link between the photo and her profile. The original poster still controls that image under the platform's rules, and a deletion request to that person is the only route left.

Did privacy settings replace school policy?

No. School systems, safeguarding duties, and records rules stayed in control of school activity. Platform settings only shaped what the public and strangers could see.