Privacy
Last updated: October 2026
The big promise: we don't keep your CV.
When you use our CV → US Resume converter, your CV text is sent to our AI for processing and is deleted from server memory the moment the response is returned. We do not store it on disk. We do not save it to a database. We do not cache it. We do not log it. We do not share it. It is gone.
What we do collect
- Your IP address — used only for rate limiting (max 3 CV conversions per IP per day). Not stored permanently — kept in server memory and reset at UTC midnight.
- Anonymous usage counts — we count requests for our own capacity planning. We do not track which IP requested what.
- Browser localStorage — for the Profile Vault, Tracker, and Autonomy settings (toggles like “auto-tailor on save”). This stays in your browser. We never read it from the server.
What we do NOT collect
- ❌ Your CV text — never stored anywhere after conversion
- ❌ Your name, email, phone, address (unless you save them to your Profile Vault, which is browser-local only)
- ❌ Your visa or work-authorization status — we never ask, never store
- ❌ Cookies — we don't use tracking cookies
- ❌ Analytics — we have no third-party analytics (Google Analytics, Mixpanel, etc.)
- ❌ Advertising trackers — none
- ❌ Fingerprinting — none
Where your CV goes during processing
When you click “Convert to US resume”, the request goes to:
- Our JobHew server (on Vercel) — to apply country rules + build the AI prompt
- The configured LLM provider (Google Gemini, Groq, or Z.AI — whichever you set in our environment variables). The CV text is sent to this provider for processing.
- The provider returns the converted resume. Our server passes it back to your browser.
- The CV text is then garbage-collected from server memory. Gone.
We use a single AI call per conversion, with a strict prompt that prohibits the AI from inventing facts or numbers. The provider's own data retention policies apply to their API logs — see their respective privacy policies (Gemini, Groq, or Z.AI) for those details.
About file uploads (PDF/DOCX)
Today the tool accepts only pasted text. When we add PDF/DOCX upload (planned), the promise will be the same: the file is parsed in memory, the text is sent to the AI, and both the file and the text are deleted immediately after the response is returned. We will not keep uploaded files.
About “Save” (future Supabase Auth)
We plan an optional “Save” button (free account via Supabase Auth) that would let you keep your converted resume on your own Supabase project for access across devices. This is 100% opt-in. If you don't click “Save”, we never persist your CV or resume anywhere. The Supabase database is one you create and own — we are not a data controller for it.
Your rights + choices
- Clear your browser data — the Profile Vault + Tracker live in
localStorage. Clearing your browser data removes them. - Don't paste sensitive info — keep your SSN, passport number, banking info, and other high-risk personal data out of your CV (US recruiters don't expect them anyway).
- Use a VPN if you don't want your IP tied to your CV conversions.
- Self-host — the entire JobHew codebase is yours (private GitHub repo). You can deploy your own copy with your own AI provider keys at any time.
Changes to this policy
We will update this page if we add features that change how your data is handled. The “Last updated” date at the top will reflect the most recent change.
Questions
Open an issue on the GitHub repository or contact the project owner. We respond to privacy questions promptly.