HLHyrelane
Refund policy

Credits, refunds, and billing corrections

Hyrelane uses one universal credit ledger. Refund behavior must be tied to verified payment evidence, idempotent ledger transitions, and whether the paid action completed meaningful work.

Last updated

June 13, 2026

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

Open Hyrelane

Hyrelane Credits

Hyrelane Credits are the single launch wallet for paid actions such as analysis, application kit regeneration, resume export, inline LLM score, autofill preview, watcher run, weekly plan, referral finder, outreach draft, and browser-assisted apply.

  • Credit costs should be visible before the user runs a paid action.
  • Credits are reserved, committed, refunded, or granted through the universal ledger.
  • There are no separate AI credits and apply credits.

Automatic credit refunds

A reserved credit should be refunded when the paid action fails before meaningful work completes.

  • Analysis, application assets, watcher runs, and browser sessions use idempotent reserve and refund paths.
  • If a browser-assisted apply session fails before a meaningful fill attempt, reserved credits should be refunded.
  • If a session reaches review-ready or fills approved fields, the action may count as completed even if the user chooses not to submit.

Payment refunds

Razorpay is the India-first launch gateway. Refund handling must match provider evidence and the Hyrelane credit ledger.

  • Payment credits are granted only after verified provider-side evidence.
  • Refunds must reverse credits accurately and remain idempotent.
  • Manual admin corrections require an allowlisted operator, a reason, and audit evidence.

Non-refundable situations

Some completed actions may not be refundable because Hyrelane already spent credits on the requested workflow.

  • Completed analysis, generated assets, exported resumes, and reviewed browser sessions may consume credits.
  • Salary estimates and scam screening are decision-support signals, not guaranteed outcomes.
  • Choosing not to use a generated draft after review does not automatically reverse a completed credit action.

How to request help

Users should contact support with the account email, approximate time, action type, and payment reference when available.

  • Do not send raw resume text, Gmail bodies, passwords, or private application pages in support messages.
  • Support and admin tools should use redacted evidence by default.
  • Refund decisions should preserve the one-wallet credit ledger.

Disconnection and deletion

Refund requests are separate from privacy deletion requests.

  • Users can disconnect Gmail and delete snippets from privacy controls.
  • Users can request account deletion, which queues data cleanup for user-owned records.
  • Payment, credit ledger, and audit records may be retained only where legally or operationally required.