1. Eligibility and authority
You must be able to bind the organisation using PatchFlow and must have authority to grant access to each selected repository. Accounts and invite codes may not be transferred.
2. Service boundary
PatchFlow detects eligible npm upgrades, invokes a bounded coding agent, opens draft pull requests, and evaluates configured GitHub Checks. PatchFlow does not merge, deploy, warrant that generated code is correct, or replace customer review. Private-pilot availability and response targets are service objectives, not uninterrupted-service guarantees.
3. Customer responsibilities
- Use non-critical repositories during the pilot unless otherwise agreed.
- Maintain backups, branch protection, least privilege, required Checks, and human review.
- Review every diff, dependency licence, security impact, and test result before merge.
- Do not submit unlawful content, secrets in prompts, malware, regulated datasets, or repositories you are not authorized to use.
- Grant and revoke the separate GitHub and coding-agent integrations deliberately.
4. Customer content and generated output
You retain ownership of customer repositories and content. As between the parties and to the extent permitted by applicable provider terms and law, you may use generated patches and reports for your internal business. You grant PatchFlow a limited right to process customer content only to provide, secure, support, and measure the service. PatchFlow does not use private repository content to train a PatchFlow foundation model.
5. Confidentiality and data
Each party must protect the other party’s non-public information with reasonable care and use it only for the pilot. The privacy policy and subprocessor page describe service data handling. Additional processing terms can be incorporated into the pilot order form.
6. Fees, suspension, and ending use
Fees, included repositories, run caps, tax treatment, and pilot dates appear in the order form. Access may be suspended for security risk, misuse, non-payment, or legal necessity. Either party may end an at-will evaluation; paid-pilot cancellation terms are in the order form. Customer data is returned or deleted according to the published retention process.
7. Warranties and liability
To the maximum extent permitted by law, the private-pilot service is provided as available and without implied warranties that can lawfully be excluded. Nothing excludes non-excludable rights under the Australian Consumer Law. Neither party is liable for indirect or consequential loss. Any negotiated liability cap and exclusions are stated in the signed order form; if none is stated, use must remain an unpaid evaluation until commercial terms are agreed.
8. Governing terms and contact
The PatchFlow supplier is Bluebird Technologies Pty Ltd, ABN 57 628 676 764. The governing law, notices address, tax status, and dispute venue must be stated in each paid-pilot order form before payment is accepted. Contact hello@patchflow.run for the current order form.