TERMS
TERMS AND CONDITIONS / effective June 14, 2026

TERMS
AND CONDITIONS_

These terms govern access to Patchflow, repair credits, GitHub App delivery, and automated System repair attempts.

01Service
  • Patchflow provides bounded automated code repair attempts. A successful attempt may create a GitHub branch and pull request through the Patchflow GitHub App.
  • A repair attempt is not a guarantee that every issue can be reproduced, fixed, tested, merged, or accepted by your repository maintainers.
  • You keep final review and merge authority for every pull request.
02Accounts and Repository Access
  • You are responsible for the repositories, issue descriptions, commands, credentials, and access you provide to Patchflow.
  • You must have permission to connect the GitHub repositories you submit.
  • Do not submit secrets, production credentials, regulated data, or materials that you are not allowed to share.
03GitHub App Permissions
  • Patchflow uses a GitHub App so repository access can be granted, narrowed, reviewed, and revoked through GitHub. The app should be installed only on repositories you intentionally submit for repair.
  • The GitHub App requires repository metadata, contents read and write, and pull requests read and write permissions. These permissions are used to inspect authorized repository content, create a repair branch, commit the proposed patch, and open or update a pull request.
  • Patchflow does not need GitHub organization administration, billing, secrets, Actions secrets, environment secrets, or unrelated account-level permissions for the repair workflow.
  • You can revoke Patchflow repository access from GitHub at any time. Revocation may prevent queued or in-progress repair jobs from being delivered.
04AI and Repository Security
  • A repair request may cause authorized repository code and the issue description you provide to be read by a trusted System workflow for the limited purpose of analyzing the failure and preparing a pull request.
  • Patchflow is designed so repair execution happens through the System workflow and the connected GitHub App. The product does not require you to provide an OpenAI API key to Patchflow.
  • Patchflow does not sell submitted repository code and does not use private repository content to train Patchflow-owned foundation models.
  • Do not submit repositories containing secrets, credentials, private keys, regulated data, or code you are not authorized to process through a third-party repair service.
  • No hosted repair system can make repository access risk-free. You are responsible for deciding which repositories are appropriate to connect and for reviewing every pull request before merge.
05Caching, Logs, and Incident Handling
  • Patchflow stores compact business records such as repository URLs, job status, payment records, audit events, runner logs, and pull request links so the service can operate and support users.
  • Temporary runner work directories may contain repository source during a repair attempt. The runner workflow is expected to clean up local source artifacts after delivery, failure, or cancellation.
  • Patchflow operational logs should not intentionally store full repository diffs, full request bodies, access tokens, private keys, cookies, or secret values.
  • If Patchflow learns of an incident that materially affects repository confidentiality, integrity, or access, Patchflow will investigate, take reasonable containment steps, and notify affected users as required by applicable law and available contact information.
06Repair Credits and Billing
  • Repair credits are one-time prepaid credits used to request automated repair attempts.
  • One repair credit is consumed when a repair request is created and queued.
  • Patchflow may restore a credit when a platform or handoff failure prevents the runner from starting or delivering any useful attempt.
07Refunds
  • Unused card-paid repair credits may be refunded from the Pricing page when the credit has not been attached to a repair job.
  • Credits issued manually by an administrator, promotional credits, and credits already consumed by a repair request are not refundable through Stripe.
  • If an automation run fails without delivering a pull request, Patchflow may restore the consumed repair credit instead of issuing a cash refund.
08Acceptable Use
  • Do not use Patchflow to attack systems, bypass access controls, exfiltrate data, or process repositories you do not control.
  • Patchflow may reject, suspend, or cancel jobs that appear unsafe, unlawful, abusive, or outside the supported repair workflow.
  • Runner output is advisory software work. You are responsible for reviewing, testing, and deciding whether to merge any change.
09Disclaimers and Liability
  • Patchflow is provided as-is and as-available. We do not promise uninterrupted operation, specific repair outcomes, or defect-free pull requests.
  • To the maximum extent permitted by law, Patchflow is not liable for indirect, incidental, consequential, special, exemplary, or lost-profit damages.
  • These terms may be updated as the product moves from controlled launch to broader availability.