Security

Jobhunger is built for candidates sharing sensitive career and work-authorization information. We aim for least privilege, encrypted transport, and clear human control over submissions.

Application submission requires your review. We design workflows so Jobhunger prepares materials and fields, and you approve what goes to the employer site. We do not use your resume content for third-party advertising.

Candidate accounts may use email/password or Google sign-in where enabled. Password credentials are handled by our authentication provider. Use a unique password and keep recovery email access secure.

Portal hosts (candidate, manager, employer, admin) are separated so staff and candidates do not share the same surface by default.

We require HTTPS for Service traffic. Data stores use provider-managed encryption at rest where available. Backups and logs are restricted to operational need.

Support and operations staff access customer data only when needed to deliver the Service, investigate abuse, or respond to your request. Access is role-based. Marketing does not get unrestricted resume access.

Visa and status fields you enter are treated as sensitive profile data used for matching and planning. They are not sold. They are not a substitute for SEVIS, USCIS, or employer compliance systems.

Payment card data is processed by our payment provider. Jobhunger does not store full card numbers on its application servers.

We monitor for suspicious sign-in patterns, scraping, and other abuse. We may rate-limit, challenge, suspend, or terminate accounts that threaten Service integrity or other users.

If we confirm a security incident that affects your personal information, we will take steps required by applicable U.S. law and notify affected users when notification is required or otherwise appropriate.

Protect your credentials, review materials before submit, and log out of shared devices. Do not upload malware or attempt to probe the Service. Report suspected compromise immediately.

Email support@jobhunger.ai with “Security” in the subject line. Include steps to reproduce if reporting a vulnerability. Do not exfiltrate user data while testing.