Content and Public-Identity Review

A portfolio is deliberately public.

That does not mean every true fact about you belongs on it.

Review every public content source

Inspect:

• Home;
• About;
• project documents;
• technical journal posts;
• images/screenshots;
• downloadable files;
• repository README;
• Git commit metadata;
• generated metadata.

Remove accidental exposure

Look for:

• personal phone/address information you did not intend to publish;
• school/student identifiers beyond what is appropriate;
• private email exposure;
• credentials/tokens;
• internal hostnames/IPs from screenshots;
• private repository references;
• browser tabs/account names in screenshots;
• other people's personal information;
• copyrighted material you do not have permission to republish.

Public identity should be intentional

Your portfolio can communicate:

• what you build;
• what you are learning;
• how you solve problems;
• your interests;
• how to contact you through a deliberate channel if appropriate.

It does not need to perform a fake professional identity.

Write like yourself while keeping the audience in mind.

Source vs generated audit

A removed source value can still exist in:

• old generated output;
• Git history;
• screenshots/assets;
• an already deployed version.

If sensitive data was actually committed/published, simply deleting the current line may not be sufficient remediation. Treat secret exposure as a real incident and follow appropriate credential rotation/history-remediation guidance.

Portfolio action

Create a privacy/publication checklist and record every revision you make.

Checkpoint

Defend one thing you deliberately kept public and one thing you deliberately removed. Explain the audience/purpose difference.