HLHyrelane
Terms

Terms for using Hyrelane

These terms describe the expected use of Hyrelane launch features, including generated drafts, reviewed autofill, browser-assisted apply, credits, and safety boundaries.

Last updated

June 13, 2026

These pages describe launch behavior for website, extension, Gmail, browser sessions, credits, payments, and deletion controls.

Open Hyrelane

Use of Hyrelane

Hyrelane helps users evaluate jobs, tailor grounded application materials, review autofill suggestions, and track outcomes.

  • Users are responsible for reviewing all generated content before use.
  • Hyrelane scores, salary insights, scam warnings, and recommendations are decision support, not guarantees.
  • Users must not use Hyrelane to submit false claims, bypass website restrictions, or scrape private data.

Generated application materials

Generated drafts must remain grounded in confirmed resume/profile evidence and user-provided context.

  • Unsupported claims should be blocked or shown as violations.
  • Prompt text and generation rules are owned by Hyrelane prompt packages.
  • The user remains responsible for final application accuracy.

Extension and assisted apply

Extension and browser automation features are human-in-the-loop workflows.

  • The extension reads current visible job/application pages only after a user action.
  • Autofill preview requires review and approved fields before filling.
  • ATS final submission remains manual unless a future contract explicitly changes it.
  • Hyrelane must not silently submit job applications.

Credits and paid actions

Hyrelane uses one universal Hyrelane Credit wallet across paid product actions.

  • Costs should be shown before credit-charging actions.
  • Basic tracker use, save job, Gmail sync, and local inline scores are 0 credits.
  • Browser-assisted apply uses 5 credits per session under the v3 launch contract.
  • Separate AI and apply credit wallets are not part of launch scope.

Safety limits

Hyrelane launch scope keeps privacy, source restrictions, and manual review boundaries in product behavior.

  • No Gmail sending.
  • No private scraping or LinkedIn restriction bypass.
  • No Chrome permission expansion outside the v3 P0 source list.
  • No unredacted sensitive data in logs, traces, analytics, or admin evidence.

Availability and changes

Hyrelane may change provider configuration, operational flags, or availability to protect users and keep the service reliable.

  • Operational flags are kill switches, not a way to remove v3 P0 scope.
  • Provider outages may affect AI, payments, Gmail, browser sessions, or analytics.
  • Users can request data deletion as described in the privacy page.