--
title: "Should You Delete Work-Related Tweets After Leaving a Job?"
description: "- Posts with company secrets or internal project codenames, even if they feel irrelevant now."
tags: ["should", "delete", "work", "related"]
canonical_url: https://digital-footprint-health.shop/blog/delete-tweets-after-leaving-job
- Posts with company secrets or internal project codenames, even if they feel irrelevant now. - Emotional posts criticizing the former employer or manager, easy for a new employer to find.
Two types you can keep. - Pure skill-sharing that names no one and leaks nothing. - Neutral farewell posts that show professionalism.
Why offboarding is the cleanup window. Content posted while employed changes context completely after you leave. A careless project share can be reread as a leak during a non-compete or background check; a rant can surface when you apply for the next job.
Offboarding cleanup steps. - Export the archive and search for the former company name, project codenames, and client names. - Grade each hit by "does it leak" and "is it negative".
Watch the non-compete window closely. If you signed a non-compete, old tweets after leaving carry double risk. The former employer may keep watching your public account through the restricted period, hunting for proof you work for a rival, or reading an old project share as a leak.
The part worth keeping: If you signed a non-compete, old tweets after leaving carry double risk. Full write-up is on the source blog.
Top comments (0)