Work through your own account section by section. Note which profile parts you have made private, then separately check your user-entered status and anything you published before: making a profile private hides profile sections, but a status may remain public and previously public resources are not recalled. Remove sensitive wording from your own status and record older public work as history you cannot un-publish with a privacy setting alone. This is an inventory habit, not a switch that erases the past.
Find public social profile clues with our TraceSeek app.
Start with two separate lists
Treat this as two inventories, not one privacy toggle. On the first list, write down the profile sections you control on your own account and whether each is private or visible. On the second list, write down what sits outside those sections: your user-entered status text and any resources that were public earlier. Making a profile private hides profile sections, but it does not hide every previously public resource, and a user-entered status may remain public. Keep the two lists apart so you do not mistake a private profile for a clean slate. [GitLab Docs: public profile, account ID and owner settings]
- List profile sections you have set to private.
- List your status text and any previously public resources separately.
- Mark each item as owner-controlled, public-by-design, or previously public history.
Check the status field as self-written text
Your status is something you wrote, so it belongs in your own cleanup, not in a claim about what a platform hides. Open your profile while signed in and read the status line as a stranger would. Remove any self-written details you no longer want visible. Treat editing the text itself as the protective step, because the checked facts only establish that a status may remain public even when profile sections are private; deciding which details are sensitive is your judgment. [GitLab Docs: public profile, account ID and owner settings]
- Rewrite or clear status text you no longer want visible.
- Re-read the new wording as if you were a stranger.
- Note the date you changed it.
Old public work is history, not a setting
Resources that were public earlier are not recalled by making the profile private. Commit history, older public projects, and anything already copied or indexed can outlive a visibility change. Do not claim a privacy switch erases project history; instead, record the older public items on your inventory and decide item by item whether the exposure still matters to you. Where you cannot change something, write unavailable and stop at that boundary rather than guessing. [GitLab Docs: public profile, account ID and owner settings]
- Record older public projects and commits as history on your list.
- Decide whether each still matters; where you cannot act, write unavailable.
- Do not describe a privacy change as erasing project history.
Separate email and identity fields
Your profile email and your commit email are different settings, and an automatically generated private commit email is available for future work. That does not retroactively erase older public commits, so check both surfaces on your own account. The same care applies to external social-account fields, which can hold identifiers such as a Discord user ID or a GitHub username rather than a display name. Review those fields as identifiers you chose to publish. [GitLab Docs: public profile, account ID and owner settings]
- Compare profile email and commit email settings.
- Note older commits that still carry the earlier address.
- Read external account fields as identifiers, not display names.
Contributions and presence are not proof
Owners can show private contribution actions without publishing all underlying project information. Read a contribution graph as a summary of activity, not a real-time presence or identity record. This matters when you audit your own footprint: a quiet graph or a private section is not evidence that someone is absent, and a visible graph is not proof of current activity. Keep observations, their limits, and your decisions in separate columns so the audit stays honest. [GitLab Docs: public profile, account ID and owner settings]
A worked inventory (hypothetical)
Suppose an owner has hidden several profile sections but left a status naming a city and a weekly routine. Their older public project still shows early commits under an address they no longer use. Note that GitLab.com and independently hosted instances are separate account contexts, so confirm which host you are reviewing. The hypothetical worksheet below keeps each observation next to its limit and the practical next step. [GitLab Docs: public profile, account ID and owner settings]
| observation | limit | next step |
|---|---|---|
| Profile sections set private | Does not hide previously public resources | List older public projects as history, not as fixed |
| Status names a city and weekly routine | Status may remain public despite private sections | Edit the status text down to neutral wording |
| Older commits use an earlier email | Private commit email applies going forward only | Record the older commits as history; decide if action is possible |
A couple more questions
Does making my GitLab profile private hide my status and old projects?
No. A private profile hides profile sections, but a user-entered status may remain public and previously public resources are not recalled. Edit the status text yourself and record old public work as history.
Can I erase older public commits with a private commit email?
No. An automatically generated private commit email is available for future work, but it does not retroactively erase older public commits. List them as history and decide item by item.
What if I cannot change something I find?
Record it as unavailable and stop at the access boundary. Use the platform's current official help for that surface, or ask a co-maintainer you already know for a voluntary link, without treating silence as proof of anything.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.