Job Data and Source Compliance

RoleProof indexes public official company career sources and public ATS-style sources where access is intended for published job discovery. Every job row should link users back to the official company or source apply page.

• No LinkedIn, Indeed, Glassdoor, ZipRecruiter, or login-required job boards.
• No CAPTCHA bypass, IP block bypass, rate-limit evasion, or automated behavior that pretends to be a person.
• No claim of partnership with employers unless explicitly authorized.

• Stored fields should be limited to title, company, location, official URL, source, dates, category, salary when exposed, and derived matching features.
• Full copyrighted job descriptions should not be displayed.
• If source text is used for matching, it should stay private, short-lived, and converted into extracted features where practical.

• RoleProof's Coach and match features are user-facing preparation tools. They should not be marketed as employer-side screening, ranking, assessment, or hiring-decision tools.
• Match numbers should be framed as user-only job-search signals computed from visible resume/project/work evidence and product rules, not as scores of the person, protected traits, legal eligibility, or hiring outcome.
• The product should not ask for or infer protected-class information for matching or Coach scoring.
• If any future employer-facing assessment feature is considered, launch should wait for legal review of employment-selection, accessibility, notice, validation, and bias-audit obligations.

• Coach output should give practical next steps and should not discourage users based on age, disability, race, sex, national origin, religion, or other protected traits.
• Resume and plan feedback should focus on visible evidence, role requirements, user-stated goals, and user-controlled edits.
• Users should be able to review, edit, ignore, or delete AI-generated content before using it outside RoleProof.

Companies can request source removal, URL correction, or metadata updates. A removal path should be handled quickly by disabling the source target and hiding affected listings.