Review type
Manual public-source OSINT review
Sample report
Sample Individual Privacy Report
See how a manual OSINT privacy report may be structured, what types of public-source observations may be included, and how practical recommendations are presented.
Fictional sample only
This is a fictional sample report for demonstration purposes only. It does not contain real personal data, real breach findings, real search results, or real profile links.
This is a fictional sample report for demonstration purposes only. It does not contain real personal data, real breach findings, real search results, or real profile links.
Get Privacy Report — Full Individual Privacy Report
Alex Taylor
Report Dashboard
Full
Report type
Alex Taylor
Subject
WA
Region
AUD $89
Price reference
Status
Fictional demonstration sample
Prepared by
Get Privacy Report
Fictional Exposed Data Summary
3
Usernames
1
Email indicator
6
Search observations
4
Public profile observations
5
Social visibility observations
Examples
Breach indicators are fictional only
Risk assessment
Security risk assessment
This is an indicative privacy-awareness rating based on public-source visibility, username reuse, profile exposure, and data minimisation concerns. It is not a legal, credit, cybersecurity, or identity-theft risk score.
Moderate Exposure
Indicative score: 58 / 100
Sample subject details
Name: Alex Taylor
Common name: Alex T.
Location: Australia
State/Territory: Western Australia
Email: alex.example@email.com
Usernames: alextaylor88, alex.t.photo, ataylor.photo
Key risk factors
- Username reuse across platforms
- Public profile details visible without login
- Search results linking multiple parts of the person's identity
- Public email exposure indicators
- Old or outdated public references
Risk-reduction opportunities
- Review public search results
- Tighten social media privacy settings
- Separate personal and public-facing usernames
- Use unique passwords and MFA
- Remove or update outdated public profiles where possible
Recommendations
Actionable recommendations
Secure key accounts
- Enable MFA on important accounts
- Review privacy settings on major social platforms
- Check password reuse and move to unique passwords
- Avoid publishing primary email publicly
Reduce public linkage
- Review search results for name, email, and usernames
- Remove or update outdated profiles
- Separate personal and public-facing usernames
- Reduce public location, employer, school, and family details
Build a routine
- Review public footprint quarterly
- Maintain a password manager
- Use separate emails for shopping, public profiles, and private accounts
- Keep public-facing profiles intentional and minimal
Correlation
Identity correlation analysis
The more often the same username, photo, email, or biography appears across platforms, the easier it may be for someone to connect separate accounts.
Correlation risk: Moderate
Fictional observations suggest several identity fragments could be linked through repeated usernames and public profile context.
Fictional connecting clues
- Common name linked to a public profile
- Similar usernames appearing across different platforms
- Photo-related username suggesting hobby or professional interest
- Public bio details increasing context around location or work
Exposure categories
Exposed data summary
Usernames / aliases
Count: 3
Example: alextaylor88 appears similar to ataylor.photo.
Privacy note: Reduce reuse across unrelated accounts.
Email indicators
Count: 1
Example: alex.example@email.com appears in a fictional exposure indicator.
Privacy note: Avoid publishing a primary email.
Search results
Count: 6
Example: old profile snippets connect name and username.
Privacy note: Review stale listings.
Public profiles
Count: 4
Example: public bio includes broad WA location and photo interest.
Privacy note: Keep bios minimal.
Social visibility
Count: 5
Example: profile photos and tagged content are visible publicly.
Privacy note: Enable tag review.
Location/context clues
Count: 3
Example: community mentions suggest a broad region.
Privacy note: Avoid exact routines or addresses.
Search visibility
Internet search visibility
These are fictional examples and do not represent real websites or real search results.
Alex Taylor Photography Portfolio — Example result only
example.com/profile/alex-taylor
Snippet links Alex T. with photography interests and a broad Australian location.
Alex T. Community Event Mention — Example result only
demo-directory.example/events/alex-t
Snippet includes a public event mention and broad regional context.
Old Forum Profile for alextaylor88 — Example result only
sample-profile.example/users/alextaylor88
Snippet shows an older username that could connect to current public profiles.
Public Profile Snippet — Example result only
example.com/people/alex-t-photo
Snippet displays a short public bio and repeated profile image.
Recommended actions
Search full name, common name, usernames, and email periodically. Request correction or removal where platforms allow. Update or delete old profiles. Avoid exposing unnecessary contact or location details.
Profiles
Social media and profile visibility
Public profile details
Bio details may reveal interests, broad location, or contact patterns.
Public comments or old posts
Older public activity may appear without current context.
Tagged photos
Tags can connect people, events, and locations beyond your own profile.
Profile photo reuse
Repeated images can make separate profiles easier to connect.
Friends/followers visibility
Visible connection lists can expose social context.
Location or workplace clues
Small bio details can add up when combined across profiles.
Recommended actions: review who can view posts, enable tag review, hide friends or followers where appropriate, remove unnecessary bio details, and avoid sharing exact location or daily routine publicly.
Breach awareness
Data breach indicators
This fictional sample shows how breach indicators may be summarised if relevant public breach information is identified. It is not a real breach finding.
Example Marketing Platform Incident
Data type potentially exposed: email, username.
Recommended action: check account recovery options and watch for targeted spam.
Example Forum Database Exposure
Data type potentially exposed: email, username, hashed password, IP address.
Recommended action: change reused passwords and enable MFA.
Example Old Service Credential Leak
Data type potentially exposed: email, username, hashed password.
Recommended action: secure the email account first, then update affected services.
Breach awareness
A privacy report may include public breach exposure indicators where available. Customers should treat any possible exposure as a reason to improve password hygiene and MFA: use unique passwords, use a password manager, enable MFA, secure the email account first, and review recovery emails and phone numbers.
Reputation
Reputation and professional visibility
Why it matters
Search results can influence first impressions. Old public content may appear out of context, and professional profiles should be consistent and intentional. Public personal details should be minimised where they are not needed.
Recommended actions
Update professional profiles, remove outdated public bios, review old comments or posts, and create a clean intentional public presence if desired.
Priorities
Priority risk table
Username reuse across platforms
Priority: Medium
Why it matters: Makes separate accounts easier to connect.
Recommended action: Use different usernames for personal, professional, and sensitive accounts.
Public profile details
Priority: Medium
Why it matters: Can reveal location, work, interests, or contact patterns.
Recommended action: Reduce unnecessary public bio details.
Email exposure indicators
Priority: Medium
Why it matters: Can increase spam, phishing, or impersonation risk.
Recommended action: Use aliases and avoid publishing primary email publicly.
Old public references
Priority: Low to Medium
Why it matters: Can create outdated impressions.
Recommended action: Request updates or removal where possible.
Weak privacy settings
Priority: Medium
Why it matters: Posts, tags, and followers may expose more than intended.
Recommended action: Review privacy settings and enable tag approval.
Checklist
Personal Privacy Action Checklist
Start with the highest-impact actions first, then review your online footprint regularly.
Quick wins
- Secure your main email account first
- Turn on MFA for email, banking, and major social accounts
- Use a password manager
- Replace reused passwords
- Search your name, common name, usernames, and email
Social media privacy
- Review who can see your posts
- Limit public profile details
- Enable tag review
- Hide friends/follower lists where appropriate
- Remove unnecessary location details
- Review old posts and comments
Email and account security
- Use different emails for personal, shopping, and public-facing accounts
- Review account recovery options
- Check forwarding rules
- Remove old connected apps
- Avoid publishing your primary email online
Search and public visibility
- Search your name and usernames regularly
- Check image search results
- Review old directory-style listings
- Request updates or removal where appropriate
- Keep professional profiles accurate and intentional
Device and browser privacy
- Keep devices updated
- Review app permissions
- Use strong lock screen protection
- Remove unnecessary browser extensions
- Clear old saved passwords from browsers if using a password manager
- Review location, camera, microphone, and contact permissions
Data broker and directory exposure
- Identify public listings that show your contact or location details
- Use opt-out forms where available
- Keep a record of removal requests
- Recheck later because listings can reappear
- Avoid submitting unnecessary personal details to unknown websites
Family and children’s privacy
- Avoid posting school uniforms, exact locations, or regular routines publicly
- Review children’s app permissions
- Keep children’s accounts private where possible
- Teach children not to share personal details online
- Review tagged photos involving family members
Ongoing routine
- Review privacy settings every 3 months
- Search your main identifiers regularly
- Delete unused accounts
- Update passwords after any suspected exposure
- Keep a simple record of removal requests and account closures
Action plan
7-day action plan
Day 1
Search your public identifiers.
Day 2
Secure your main email account.
Day 3
Review social media privacy settings.
Day 4
Review old accounts and username reuse.
Day 5
Check public profile details and search results.
Day 6
Start removal or update requests where appropriate.
Day 7
Set up a quarterly privacy review routine.
Boundaries
What this sample does not include
No real sensitive data
No real personal data, passwords, financial records, medical records, or government ID information.
No private access
No private account content and nothing obtained through hacking or private access.
No guarantees
No real breach confirmation, guaranteed removal, or guaranteed completeness.
Get Privacy Report is an awareness and reporting service. Reports are based on publicly accessible sources and customer-supplied details only. We do not access private accounts, bypass security, remove content on your behalf, or provide legal advice.