Refund Policy
This policy is shown at checkout during the pilot and applies to every paid BranchToBrowser job.
Short version: If we took your $19 for an eligible job and we cannot ship it after 3 attempts, you get the full $19 back — automatically. You do not need to ask.
1. Automatic full refund after 3 failed attempts
If an eligible paid job cannot pass the delivery gates after 3 bounded repair attempts — meaning no verified build artifact (dist/index.html or out/index.html) and no working live link — we issue a full $19 refund automatically. It is a system action, not a support negotiation.
2. Rejected before payment = no charge, no refund needed
Eligibility runs before payment. If a repo is rejected because it is private, needs a database, needs auth or login, needs secrets, or is otherwise out of scope for v1, no charge is taken. There is nothing to refund.
3. What the failure email includes
- The gate that failed and a plain-language reason
- Whether your code was changed (and, if so, the patch summary)
- Refund status: refund ID, amount, and expected timing
- What would need to change before a resubmission could qualify
We do not send raw internal build logs.
4. Timing
Refunds are issued to the original payment method. Arrival timing follows the payment provider and your bank — typically 5–10 business days after the refund is issued. If a refund you were told about has not arrived after that window, contact pilot support.
5. Policy violations discovered after payment
If a job is stopped after payment because the submission violates the Terms — for example malware, mining, phishing, or illegal content — refund handling for that job follows the Terms. We do not promise a refund in that case on this page.
6. Delivered jobs
A job that passes all gates and is delivered (live link verified, README, patch summary, and project page provided) is a completed $19 ship. If the delivery itself is broken — for example the live link stops working inside the 90-day hosting window or a deliverable is missing — contact support and we will fix it or refund it under the pilot support commitment.
7. Contact
BranchToBrowser pilot support (broken delivery only): support@branchtobrowser.com