pilotfish

Pilotfish Terms of Service

Last updated: 31 October 2026

These terms are an agreement between you and Jose Silva, sole trader (empresário em nome individual), Braga, Portugal, NIF 254875394 ("Pilotfish", "we", "us"). Contact: hello@pilotfish.run.

They cover the Pilotfish GitHub App, the website at pilotfish.run and the dashboard (together, "the Service"). By installing the app, signing in or buying credits, you accept them. If you use Pilotfish for an organization, you accept them for that organization and confirm you may do so.

1. What Pilotfish does

  • When a bug report is filed, or a maintainer comments /repro, an AI agent tries to reproduce the bug. It runs inside a disposable virtual machine that clones your repository, and it posts what it found as a comment on the issue. It may ask the reporter one question and try again when they reply.
  • When you add a repository, Pilotfish first sets it up (works out how to install and build it).
  • On pull requests, Pilotfish reruns saved reproductions against the pull request's code, without AI, and keeps one comment on the pull request up to date.
  • The AI agent uses Anthropic's Claude models. Virtual machines are provided by Boat, a third-party sandbox provider. See the Privacy Notice for who handles what data.

2. Accounts

  • You sign in with GitHub. You need a GitHub account in good standing and must follow GitHub's terms.
  • You must be old enough to use GitHub, and at least 18 to buy anything.
  • You are responsible for what happens under your account and for the repository settings you choose (for example, who may trigger runs).
  • What Pilotfish can see is limited by the permissions you grant the GitHub App. You can uninstall it at any time on GitHub.

3. AI output: please read

  • Pilotfish's verdicts, scripts and comments are produced by an AI agent and can be wrong. A failed reproduction does not mean there is no bug; a successful one does not tell you the cause.
  • Comments are posted under the Pilotfish bot account on your repository. On a public repository they are public, and so is the run's page on pilotfish.run (see §6).
  • Comments written by the AI agent are labelled as AI-generated.
  • Review anything before you rely on it, merge it or run it yourself. Reproduction scripts come from issue text, which anyone can write; we run them only in disposable machines, and you should treat them as untrusted code.

4. Credits and prices

  • Runs and repository setups use credits. Each one uses at least one credit; larger ones use more, based on the compute and AI they need. The dashboard shows what each run used. Runs stop when the account has no credits left.
  • Credits belong to the GitHub account (user or organization) that installed Pilotfish. They have no cash value and can't be transferred or sold.
  • Free trial: 10 credits, valid for 30 days from the account's first run. One trial per account and per person, for GitHub accounts more than 90 days old, while we have trials left for the day. No payment needed.
  • Pro: $20 per month for 100 credits each month. Unused Pro credits do not roll over; they expire at the end of each billing month. Pro renews automatically every month until cancelled.
  • Credit packs: 40 credits for $10, valid for 12 months from purchase.
  • Credits are used soonest-expiring first.
  • Prices are before tax. VAT or sales tax is added at checkout where it applies.
  • We may change prices or credit amounts. Changes apply from your next renewal or purchase, and we'll tell Pro subscribers at least 30 days ahead. You can cancel before the change applies.

5. Payment, cancellation, refunds

  • Payments are handled by Stripe through Stripe Managed Payments. Your purchase is "Sold through Link": Stripe's affiliate is the merchant of record, charges you, issues receipts and invoices, and handles tax. Stripe's and Link's terms apply to the payment.
  • Cancel Pro at any time from the billing page in the dashboard (Stripe's customer portal) or in your Link account. Pro then stays active, with its credits, until the end of the month you've paid for, and isn't renewed.
  • Refunds and the 14-day withdrawal right: see the Refund Policy.
  • If a payment is refunded, the credits it bought are taken back. If a payment is disputed (chargeback), its credits are taken back; they return if the dispute is decided in your favour. A chargeback that is lost, or one filed as fraud, cancels Pro immediately on the card involved, without refund.

6. Your content

  • "Your content" means what Pilotfish reads from your repositories (code, issues, comments, pull requests) and what it produces for you (verdicts, scripts, logs, comments).
  • You keep all rights to your content. You give us permission to use it only to run and improve the reliability of the Service for you: to copy your repository into virtual machines, send the relevant parts to our AI provider, store run records, and post comments on your repository.
  • Public run pages: for runs on public repositories, pilotfish.run shows a page with the run's evidence (not the raw script or AI transcript). We may feature such runs as examples. Maintainers can hide a run from its public page and from the examples in the dashboard; anyone can ask us to remove one.
  • No training: we don't use your content to train AI models, and neither does our AI provider under its commercial terms.
  • If you are a business and your content includes personal data, the Data Processing Terms in the annex apply.

7. Acceptable use

Don't use Pilotfish to:

  • break the law, or GitHub's or Anthropic's usage policies;
  • attack, probe or overload the Service, its virtual machines or other systems, or try to escape a virtual machine;
  • mine cryptocurrency, send spam, or run unrelated workloads in the virtual machines;
  • trigger runs on repositories you don't have the right to use it on, or flood repositories with comments;
  • deliberately feed it content meant to manipulate the agent into harmful actions (for example, prompt injection aimed at other users);
  • get around credit limits, trials or payment (for example, with multiple accounts);
  • resell the Service or build a competing dataset from its output without our written permission.

We may limit, pause or stop runs, or suspend an account, that breaks these rules or puts the Service or others at risk. Where we can, we'll tell you first and give you a chance to fix it.

8. Availability and changes

  • The Service is new and provided as it is. We work to keep it running but don't promise it will always be available, fast, or error-free.
  • We may change or remove features. If a change materially reduces what you paid for, we'll tell you and you may cancel and get a refund of the unused part.
  • We depend on GitHub, Anthropic, Boat, Stripe and our hosting provider. If they fail or change their terms, parts of the Service may stop working.

9. Liability

  • We aren't liable for indirect or consequential loss, lost profits, or lost data, or for decisions you make based on AI output.
  • Our total liability for any claim is limited to what you paid us in the 12 months before it arose, or $50 if you paid nothing.
  • Nothing in these terms limits liability for intent or gross negligence, death or personal injury, or anything else that can't be limited by law. If you are a consumer, you keep all rights that the law of your country gives you and that can't be waived.

10. Ending the agreement

  • You can stop at any time: cancel Pro, uninstall the GitHub App, and ask us to delete your data (see the Privacy Notice).
  • We can end the agreement with 30 days' notice, or right away for a serious breach of these terms. If we end it without your fault, we refund unused paid credits.
  • On ending, unused credits lapse (except as refunded above) and we delete your data as the Privacy Notice describes.

11. Changes to these terms

We may update these terms. For material changes we'll give at least 30 days' notice in the dashboard and on this page. If you don't agree, you can stop using Pilotfish before they apply; continuing means you accept them.

12. Law and disputes

  • These terms are governed by Portuguese law. If you are a consumer living in another country, you also keep the mandatory protections of your country's law and can bring claims in your home courts.
  • Please contact us first: hello@pilotfish.run. We reply within 15 working days.
  • Consumers in Portugal can use the electronic complaints book (livroreclamacoes.pt) or an alternative dispute resolution entity: CIAB, the consumer arbitration centre for the Braga region (ciab.pt).

13. Contact

Jose Silva · Braga, Portugal · NIF 254875394 · hello@pilotfish.run

Annex: Data Processing Terms

These apply when you are a business (or other organization) using Pilotfish on repositories whose content includes personal data, and you are the controller of that data. They are meant to meet Article 28 of the GDPR. If they conflict with the rest of the terms, these win.

  1. Roles. You are the controller and we are your processor for personal data in your content (§6). We are a separate controller for account, billing and website data (see the Privacy Notice).
  2. Instructions. We process that data only to provide the Service as described in these terms and as you configure it, unless the law requires otherwise (in which case we'll tell you if allowed).
  3. Data and people. Types: GitHub usernames and ids, issue and comment text, code and commit metadata, and anything personal inside them. People: your maintainers, contributors and issue reporters. Duration: while you use the Service, then deletion as in item 9.
  4. Confidentiality. Anyone we let process the data is bound by confidentiality.
  5. Security. Isolated, disposable virtual machines for each run; encryption in transit; GitHub user tokens encrypted at rest; only a hash of session cookies stored; least-privilege access to production; error reports stripped of request data and personal data.
  6. Subprocessors. You authorize the subprocessors listed at pilotfish.run/privacy#subprocessors. We'll announce changes there at least 14 days ahead; you may object, and if we can't resolve it, end the agreement with a refund of unused paid credits. We bind each subprocessor to data protection terms like these.
  7. Transfers. Where a subprocessor is outside the EEA, we rely on an adequacy decision (including the EU–US Data Privacy Framework) or the EU Standard Contractual Clauses.
  8. Help. We help you answer data subject requests, and with security, breach notification and impact assessments, as far as reasonable for the Service. We tell you of a personal data breach affecting your data without undue delay, and within 72 hours of becoming aware of it.
  9. Deletion. When you uninstall the app from a repository or account, we delete its content within 30 days, except what the law requires us to keep. You can ask for an export first.
  10. Audits. We give you the information needed to show compliance with this annex, on written request, once a year (or after a breach). Audits beyond that are at your cost and by agreement.