Get Your Personal Info Removed From Public Library Patron Lookup and Account-Recovery Pages

Public libraries champion privacy, yet some patron lookup tools, catalog profiles, and account-recovery pages can unintentionally expose personal details. Search boxes that auto-complete your name, pages that reveal your email domain, or forms that confirm whether an account exists are small leaks that add up. This guide shows you how to identify what’s public, reduce exposure, and ask your library to remove or limit the information shown.

What’s being exposed and why it matters

Most libraries use outsourced catalog and account systems. Depending on settings, these tools might:

• Suggest your full name or username in public search or auto-complete.
• Expose parts of your email or phone number during account recovery (e.g., “We sent a code to 555-***-1234”).
• Reveal whether an account exists when someone enters your email or card number.
• Show public-facing reading lists, tags, or reviews linked to a name or handle that can be traced to you.
• Display card number prefixes that identify your library system and allow targeted guessing.

Individually these seem minor. Together they can help an attacker confirm your identity, guess recovery details, or harvest contact info for phishing. Minimizing what’s publicly displayed reduces these risks.

Quick self-check: Do these library pages expose you?

Before you ask for changes, confirm what’s exposed. Run these simple checks on your library’s site and app:

1. Search auto-complete: Type your first and last name into the catalog’s main search. See if your profile, lists, or tags appear publicly.
2. Public profile pages: If your system supports ratings, shelves, or reviews, log out and visit your profile URL to see what a stranger can view.
3. Account recovery flows: Use “Forgot PIN/Password.” Enter your email or card number. Note what the system reveals (masked email/phone, account existence).
4. Patron lookup tools: Some library pages allow staff-lookup style tools accessible to the public or offer “suggested users.” Test if your details appear.
5. Mobile app behavior: Repeat these steps in the official app; exposure can differ from the website.

Document findings with screenshots. Capture page URLs, timestamps, and exactly what appears (e.g., “Shows email as j***@example.com and confirms account exists”). This helps library staff or vendors reproduce and fix the issue.

What you can safely request to remove or change

Libraries vary, but common, reasonable requests include:

• Disable public patron auto-complete or directory-like features.
• Hide or fully anonymize public profiles, shelves, ratings, and tags.
• Turn off account-existence confirmation on recovery forms (use generic messages).
• Reduce or further mask displayed contact details (e.g., do not show phone fragments; limit to generic notices).
• Remove your name from any staff-curated public lists that included you by default.
• Clear or pseudonymize old reviews that include real names.

Most of these are configuration changes in the ILS or discovery layer (e.g., Polaris, Sierra, Symphony, Alma/Primo, Koha, Aspen, BiblioCommons). If one staff member can’t change it, a systems librarian or the vendor representative often can.

Step-by-step: Ask your library to remove or limit your info

Use the steps below for a clear, respectful request that helps staff help you.

1. Find the right contact. Look for a “Privacy,” “IT,” “Digital Services,” or “Systems” contact on the library site. If unsure, the general help desk can route your message.
2. Share specific evidence. Include screenshots and URLs of the pages showing your info (public profile, recovery confirmation, auto-complete results).
3. State your request plainly. For example: “Please hide my profile from public view and disable any public association of my reviews or lists with my account.”
4. Mention privacy standards. Point to the library’s privacy policy and the American Library Association (ALA) privacy principles that prioritize patron confidentiality.
5. Ask for a vendor configuration review. If staff say it’s a vendor limitation, request escalation to the ILS/discovery vendor for a privacy-first configuration.
6. Set expectations and follow up. Ask for a timeline and confirmation after changes are made. Re-test the pages once they reply.

Template: Email to request removal/redaction

Subject: Request to remove/redact my information from public patron pages

Hello [Library/Systems Team],

During a privacy review, I found that parts of my information appear publicly or are revealed during account recovery:

• [URL] shows [e.g., my public profile with name/initials and shelves]
• [URL] confirms my account exists when I enter my email
• [URL] displays [e.g., masked phone fragment or email domain]

For privacy and security, could you please:

• Disable public patron auto-complete/directory features or remove my account from any such results.
• Hide or anonymize my public profile, shelves, reviews, and tags.
• Change recovery pages to avoid confirming account existence and reduce any exposed contact fragments.

If these require vendor configuration, would you escalate to our ILS/discovery vendor? I’m happy to provide more details or retest changes. Thank you for prioritizing patron privacy.

Best regards,
[Your Name]
[Library Card Number (last 4 only, if needed)]

Privacy settings you can change yourself

Many catalogs let you self-manage visibility:

• Profiles: Set your profile, shelves, and reviews to private. Remove your real name or photo; switch to a generic handle.
• Reading history: Turn off borrowing history or clear it so it isn’t available to be exposed if settings change later.
• Social features: Disable sharing to social platforms, following/followers, and public activity feeds.
• Communications: Opt out of nonessential notifications that may leak info in message headers or previews.
• PIN/Password: Use a unique, strong PIN and a strong account password if supported; avoid birth year, street numbers, or repeats.

Reduce account-recovery exposure

Some exposure happens during “Forgot PIN/Password.” While you can’t usually redesign that page, you can reduce what’s available to reveal:

• Use an email alias unique to your library account so the domain/user pattern isn’t obvious.
• Update to a phone number that isn’t widely listed elsewhere, or remove phone recovery if optional.
• If the system confirms account existence by email, consider switching to an alias that isn’t guessable from your name.

If the library cannot change it

Occasionally, a vendor’s current version may not support your request. When that happens:

• Ask to opt out individually: request that staff toggle privacy settings at the account level or remove your profile page.
• Request a policy workaround: staff can refrain from discussing account existence via email and use neutral language.
• Encourage roadmap escalation: ask staff to log a ticket with the vendor requesting privacy improvements.
• Minimize linked data: remove optional personal details (photo, bio, social links) that could be scraped.

Document and monitor your exposure

After changes, re-run your self-check and take new screenshots. Set a quarterly reminder to test again—vendors update interfaces and defaults can shift. Also monitor for signs of targeted phishing tied to your library account (e.g., messages referencing recent holds or overdue items).

Protect the bigger picture: identity and credit monitoring

While limiting library-page exposure helps, it’s smart to watch for broader identity risks that can arise from small leaks combined elsewhere. Consider using a credit and identity monitoring tool that alerts you to suspicious changes and potential misuse of your personal information. If you want a unified dashboard for credit, monitoring, and identity alerts, see our guide to SmartCredit for privacy, credit monitoring, and identity protection.

FAQ

Can the public see what I’ve borrowed?

Most libraries keep borrowing records confidential and purge them after items are returned unless you opt into a saved history. If you’ve enabled history or public shelves, those may display reading activity. Turn off history and set shelves private to prevent exposure.

What about kids’ accounts?

Ask staff to ensure juvenile profiles are never public and that recovery pages don’t reveal identifying details. Request the strictest masking and no public profiles for minors.

Will removing public info affect my ability to place holds or use e-books?

No. Privacy settings and profile visibility are separate from core borrowing features. You can keep everything functional while hiding public-facing elements.

Can search engines index my library profile?

Yes, if the profile is public and not blocked by robots settings. Make your profile private, remove your real name, and ask staff to request de-indexing if needed.

How long do changes take?

Simple profile privacy changes are instant. System-wide vendor configuration can take days to weeks, depending on release cycles and staff workload.

Checklist: What to do today

• Run the self-check on your library’s site and app; capture screenshots.
• Set your profile, shelves, and history to private or off.
• Update your PIN/password and remove unnecessary contact details.
• Email the library to request removal/redaction from public pages and neutral recovery messaging.
• Re-test after changes and calendar a quarterly review.

Conclusion

Public-facing catalog and recovery features can quietly reveal more than you expect—names, account existence, and contact fragments that help attackers piece together your identity. By auditing what’s visible, tightening your own settings, and asking your library to adjust vendor configurations, you can meaningfully reduce risk without losing access to the services you love. Keep records of what you find, follow up for confirmation, and monitor your broader identity footprint so small leaks don’t lead to bigger problems later.