AutoPilot safety and consent

AutoPilot is designed to help you organize, rank, prepare, and route application work. It is not designed to bypass employer systems, submit unclear answers, or hide risk from you.

What AutoPilot can do

• Rank jobs against your saved resume, target roles, and profile evidence.
• Prepare a recommended next action such as tailor, review, save, skip, or apply.
• Use supported extension workflows when the browser session and field mappings are healthy.
• Record why a job was matched, skipped, blocked, or moved to review.
• Keep application state visible in the tracker and diagnostics surfaces.

What AutoPilot will not do

• It will not bypass CAPTCHA, login challenges, 2FA, suspicious-activity screens, or other security checks.
• It will not guess unknown required answers.
• It will not auto-submit when confidence is low, evidence is weak, required answers are missing, or field mapping is unclear.
• It will not claim guaranteed interviews, job offers, or universal platform support.

Consent modes

Use review-first mode when you want the system to prepare work but pause before employer-facing action. Use autonomous mode only after you understand the daily cap, supported platforms, document readiness checks, and blocker behavior.

Stop reasons

AutoPilot should stop and ask for user action when it sees:

• CAPTCHA or security challenges
• Login or 2FA prompts
• Missing required answers
• Unsupported application schemas
• Unknown field mappings
• Low match confidence
• Weak resume evidence
• Duplicate or expired jobs

Best practice

Review your saved profile, resume versions, work authorization notes, location preferences, and reusable answers before enabling any autonomous workflow. Keep sensitive answers updated and use the diagnostics page when a workflow is blocked.