Hide Your Name on Public AI Model Leaderboards and Community Labs

Public model leaderboards and community labs help builders compare results, share evaluations, and collaborate. They also create a permanent record of who submitted what and when. If your real name or identifiable handle appears on these pages, you may expose more personal information than intended. This guide explains how to hide or reduce the visibility of your name, how to handle historical entries that still show your identity, and how to use safer practices going forward.

Why Hiding Your Name Matters

Leaderboards, evaluation hubs, and community labs often display contributor names, handles, avatars, and links to profiles or repositories. That can be enough to:

• Link your real identity to work or hobbies you want to keep separate.
• Reveal your activity patterns, time zone, employer, or location clues.
• Enable phishing or social-engineering attacks targeting your accounts.
• Fuel unwanted attention if your results are controversial or widely shared.

Unlike closed corporate tools, public hubs are indexed by search engines and archived by third-party mirrors. A single submission using your legal name can propagate across aggregators, newsletters, and cached snapshots.

Understand How Leaderboards and Labs Display Names

Different platforms expose identity in different ways. Before changing settings, map out how your name appears:

• Display name vs. username: Some sites show only a display name; others show both. A display name is usually changeable. A username often becomes part of permanent URLs.
• Profile picture and bio: Even if you change your name, your photo or a bio with real-world details can re-identify you.
• Submission metadata: The submission table might show the submitter, org name, or linked repo owner. Automated badges can include your handle in generated artifacts.
• Organization affiliations: Submissions under a company or team may display the org’s name. Your personal involvement can still be inferred through commit history or discussion threads.
• Public APIs and export feeds: Some leaderboards provide CSV/JSON exports. If your name appears there, it may be republished by other sites.

Immediate Steps to Reduce Exposure

If your real name is already visible, act in this order to prevent further spread:

1. Change your display name to a neutral alias: Pick a handle that does not include your legal name, initials, birth year, school, or employer.
2. Swap your profile photo for a generic image: Avoid face photos, locations, badges, or uniforms.
3. Redact your bio and links: Remove references to workplaces, cities, personal domains, or social media that name you.
4. Update your submissions: If the platform allows, edit prior entries to switch the visible submitter to an organization or neutral alias.
5. Review repository and dataset owners: Leaderboards often link to the repo or dataset owner. Ensure those owners use your neutral alias as well.
6. Check notification and activity feeds: Public activity feeds may show your older handle. Make feeds private or minimize visibility if possible.

Platform Patterns and Where to Look

You may see variations across model hubs and evaluation sites, but these checkpoints are broadly useful:

• Account and profile settings: Look for fields titled Display name, Public name, or Profile visibility.
• Privacy or visibility controls: Some platforms let you hide contributions from public listings or set them to internal or unlisted.
• Submission forms: On upload, choose the correct owner (personal vs. organization) and uncheck options that broadcast updates to feeds.
• Moderation or support channels: If a name change is restricted, request a one-time username update or display-name override.
• Export or cache notes: Documentation may confirm how long caches persist and whether support can refresh entries after a privacy change.

Create a Privacy-First Alias

A strong alias reduces reidentification risk even when details leak:

• Choose a handle without personal clues: Avoid real initials, birthdays, graduation years, or hometown references.
• Use a fresh email: Create a privacy-first email just for technical accounts. Do not forward from your main inbox if possible.
• Skip vanity domains: Linking to a personal site can tie your alias to your legal identity through WHOIS, trackers, or contact pages.
• Be consistent across platforms: Use the same neutral alias where you participate publicly to avoid cross-linking errors that reveal your real name.
• Turn off discoverability: Disable features that suggest your profile to contacts by scanning your address book or social connections.

Handling Historical Entries and Caches

Hiding your name now does not always fix the past. Older entries may still show your name in:

• Leaderboard snapshots, mirrors, and weekly summaries.
• Exported CSVs hosted by third parties.
• Issue trackers, pull requests, or discussion threads.
• Newsletters, blog posts, and social media embeds.

Use this playbook to address history:

1. Update the source record: Change your display name and profile first so new visitors see the neutral alias.
2. Request cache refreshes: Ask the platform to reindex or purge cached tables if they mirror your old name.
3. Contact mirrors thoughtfully: For third-party sites, request a redaction or replacement of your name with your alias, referencing a link to the updated source.
4. Limit deep links: If possible, rotate submission URLs to the org-owned version so older personal links lose prominence.
5. Use search removal tools: File removals for outdated or sensitive snippets where policies allow. Also request takedowns of auto-generated previews.

Submission Hygiene to Prevent Future Leaks

Leaderboards often ingest metadata automatically. Protect your identity before you upload:

• Strip name-bearing metadata: Remove author names from model cards, dataset READMEs, config files, and documentation headers.
• Sanitize commit history: Use a privacy-safe username and email in commits. Avoid amending public history unless the platform supports it safely.
• Review model cards and evaluations: Replace personal pronouns and signatures with neutral team language.
• Use organization ownership: Submit under an org where the visible contact is a role account (e.g., maintainer@) rather than a person.
• Avoid embedding name in artifact names: Don’t include your legal name or initials in file names, tags, or run IDs.

Risk Scenarios to Watch

Even careful users can be re-identified. Common pitfalls include:

• Cross-posting: Announcing results on personal social media ties the alias back to you.
• Unique writing style: Bios or model cards that mirror your blog tone can be matched across platforms.
• Time zone and cadence: Regular submission times can reveal location or employer schedule.
• Organization overlap: Listing the same affiliation on LinkedIn and on the lab profile creates an obvious link.

Safer Collaboration Options

When you need to work publicly but minimize exposure, consider these approaches:

• Org-first workflow: Publish under a team or community organization where individual contributors aren’t listed on the leaderboard row.
• Role accounts for contact: Use a generic role email for issue triage and submissions.
• Private testing before public release: Run preliminary evaluations in private or internal sandboxes to avoid creating public drafts with your name.
• Minimal public profile: Keep only essential info visible: neutral alias, generic avatar, and a role contact link.

How to Ask Platforms for a Redaction

If self-service changes aren’t enough, a concise, respectful request helps. When contacting support:

• Prove account control: Message from the email attached to the account or the linked organization.
• Be precise: Provide direct URLs of leaderboard rows, profiles, and API endpoints where your name appears.
• Request specific action: Ask for a display-name update on historical entries, cache purge, or substitution with your alias or organization name.
• Reference privacy grounds: Explain that you’re seeking to reduce personal-information exposure; avoid legal threats unless necessary.
• Follow up on mirrors: Ask if the platform can nudge official mirrors or refresh syndicated feeds.

Search and Monitor for Reappearing Mentions

After you change your name, monitor for resurfacing references:

• Search variations: Try old handles, your full name, initials + project terms, and cached copies.
• Set alerts: Use search alerts for your name and alias so you catch new mirrors or posts.
• Track profile changes: Revisit your profile and key submissions after platform updates to ensure settings didn’t revert.
• Monitor for identity misuse: If exposure included email or other identifiers, watch for phishing and account takeover attempts.

If your personal details were widely exposed or linked to sensitive financial accounts, continuous monitoring can help you catch misuse early. Consider pairing privacy steps with credit and identity alerts through a reputable monitoring service such as SmartCredit to be notified of unexpected activity tied to your identity.

Checklist: Hide Your Name Without Losing Access

• Change display name and avatar to neutral choices.
• Redact bio and remove links to personal sites and social profiles.
• Submit under an organization or role account when possible.
• Sanitize metadata in model cards, READMEs, and artifacts.
• Use a privacy-first email and disable discoverability features.
• Request cache refreshes and redactions for historical entries.
• Search for old handles and file removal requests where appropriate.
• Monitor for reappearance in mirrors, exports, and newsletters.

Frequently Asked Questions

Can I fully remove my name from a leaderboard?

Sometimes. If the platform stores submissions as immutable records, they may only allow a display-name update or alias substitution, not a full deletion. Ask support about redaction options and cache updates.

Will changing my username break links?

It can. Some platforms use the username in URLs. If you change it, older links may fail or redirect. Consider creating an organization and transferring ownership instead, which keeps your personal identity out of view while preserving links.

Do private profiles affect existing public submissions?

Often no. Public submissions can remain visible even if your profile is private. You’ll usually need to edit each submission’s visibility or request help from support.

What about team submissions?

Team or organization submissions can reduce your personal exposure, but verify that member lists, commit authors, or discussion threads don’t still show your real name.

Conclusion

Hiding your name on public model leaderboards and community labs is achievable with a few focused actions: adopt a neutral alias, sanitize your profile and artifacts, shift submissions to an organization, and request redactions where needed. Follow up by scanning for historical references and setting alerts so you catch reappearances quickly. With steady hygiene and a privacy-first workflow, you can keep contributing while limiting how much of your personal identity is attached to public records.