Privacy-First Public Resumes
Privacy-First Public Resumes (2026-07-13): Public downloads are privacy-safe PDFs, email/phone stay private by default, and recruiters request contact for you to approve.
Feature area: Privacy-First Profiles
On this page
This release covers Privacy-First Public Resumes Version 2.4.0, shipped 2026-07-13. Status: shipped. No breaking changes.
Summary
Your public profile can still offer a downloadable resume — without exposing your personal contact details by default. Honestify now keeps an original resume for your assistant, serves a privacy-safe public PDF to visitors, and lets recruiters request contact that only you can approve.
Sharing a profile used to mean choosing between helpfulness and privacy. Recruiters need a PDF; candidates do not want email, phone, or home address on the open web. This release separates those concerns.
What Changed
Privacy-safe public PDF
NewVisitors download a sanitized resume; your original stays private for the assistant.
Email & phone controls
NewPrivate by default. Set either field public only when you want the assistant to share it.
Contact requests
NewRecruiters request contact from chat; you approve or reject from the Privacy tab.
Share-on-approve fields
ImprovedConfigure which email and optional phone are sent when you approve a request.
- Dual resume storage — Original PDF for your account and AI indexing; generated public PDF for visitor downloads.
- Always-private address — Street / home address is masked on the public resume and never offered as a public assistant field.
- Contact-request flow — Name, company, work email, optional LinkedIn, and a short reason; transactional email to both sides.
- Public contact injection — When email or phone is Public, the assistant uses your configured share values — not whatever happened to appear in resume text.
Why We Built It
Public AI profiles work best when recruiters can download a resume and ask follow-ups. That only scales if candidates trust that personal contact details are not broadcast by default.
We designed privacy as a product surface — settings, sanitized downloads, and an explicit approve path — rather than hoping the model “remembers” not to leak a phone number from a PDF.
User Impact
| Audience | How you benefit |
|---|---|
| Engineers / candidates | Share a live profile and optional PDF without putting personal contact on the open web by default |
| Recruiters | Still get a professional PDF when download is enabled; request contact when details are private |
| Profile owners | Clear Privacy tab: visibility toggles, share-on-approve fields, and an inbox of contact requests |
| Platform | Privacy Policy and Terms updated for dual resumes, contact requests, and share fields |
Relevant skills: typescript, react, system design, prompt engineering.
Technical Highlights
- Resume text scanning masks email, phone, and address when building the public PDF (
@react-pdf/rendereron Vercel) ProfileVisibilitystores email/phone/resume modes; address is always treated as hidden for public surfacescontactShareEmail/contactSharePhoneon the user record — used for approve emails and for LLM injection when fields are public- Assistant answers redact private contact fields; public fields are injected as authoritative
PUBLIC CONTACT DETAILS - Contact-request APIs with owner approve/reject and Resend transactional mail
Database migrations are additive (visibility, contact requests, share fields). Existing uploads keep working; public PDFs regenerate from the stored original when needed.
Before
Privacy-First Public Resumes: before vs after
Before
Enabling resume download meant visitors received the uploaded PDF, including whatever contact details were on the page.
After
Visitors get a privacy-safe public PDF. Email and phone stay private unless you opt in. Recruiters can request contact; you decide what to share.
How to use it
- Upload your resume in the dashboard (as before).
- Open Privacy — leave email/phone private, or set them public if you want the assistant to share your configured values.
- Set Share on approve email (defaults to your account email) and optional phone.
- When a recruiter requests contact, approve or reject from the same tab.
Review the latest Privacy Policy and Terms for how contact requests and public resumes are described.
Future Improvements
What we are building next
- Owner preview of the public PDF side-by-side with the original
- Richer contact-request history and filters
- Optional city/region sharing without street address
Known limitations
- · Public resume layout is regenerated from parsed text, not a pixel-perfect clone of every custom PDF
- · Phone is only shared when you enter it in Share on approve
Feedback welcome: Use in-app feedback if a public PDF misses a section or over-redacts something you meant to keep.
Related Features
This update connects to other Honestify work:
- Related updates: resume upload support, public AI profiles, AI resume parsing
- Guides: software engineer resume, building a personal brand, ATS resume guide
- Research: most common resume mistakes, resume writing best practices, most shared profiles on Honestify
- Practice questions: walk me through your resume, tell me about yourself, why should we hire you
Create your own AI profile
Upload your resume, add expertise, and share a profile link beside LinkedIn so recruiters can ask follow-up questions before the interview.