Privacy policy

A resume is one of the most personal documents most people produce. It carries your name, contact details, employment history, education and often your location. This page describes what RoleFit does with that information, written to match how the software actually behaves rather than to cover every legal eventuality.

• Account details. Your email address and a hashed password. Passwords are hashed with bcrypt and are never stored or logged in readable form.
• Resume content. The file you upload, the text extracted from it, and the structured parse of that text.
• Job descriptions. The text you paste, and the requirements extracted from it.
• Generated documents. The PDF and DOCX files produced for you.
• Operational records. Timestamps, which actions occurred, and a truncated IP prefix (a /24 for IPv4, /48 for IPv6) for abuse prevention. Full IP addresses are not retained.

Resume text, job description text, contact details, passwords, session tokens and API keys are never written to application logs. The logger redacts these fields at every nesting level, and replaces any long free-text value with a length summary rather than a truncation — a truncated resume is still personal data.

Whether your resume is sent to a third-party AI provider depends on how this deployment is configured, and the application tells you which engine produced your result.

• In the default rule-based mode, no resume content leaves the server. Terminology alignment, filler removal and relevance reordering run locally.
• When a provider such as Anthropic or OpenAI is configured, the resume text and job description are sent to that provider to produce rewrite suggestions, subject to that provider's own terms and retention policy.

API keys are held server-side only and are never exposed to the browser.

Your data is kept while your account exists, so you can return to previous analyses and documents. Deleting a resume removes it from the product immediately. Deleting your account removes your resumes, versions, job descriptions, analyses, optimization runs, change records and generated documents, and deletes the stored files behind them. That control is in Settings, and it does not require contacting anyone.

Access is enforced per user at the data layer: every query is scoped to the account making it, so one user cannot reach another's resume even with a valid identifier. Sessions are httpOnly cookies, state-changing requests are origin-checked, uploads are validated by byte signature rather than filename, and stored objects use server-generated keys that contain nothing user-supplied.

Questions about this policy can go to abideen5036@gmail.com.