Clear scope.
Clear responsibilities.

1. How an engagement starts

MyBFchef LLC operates the RepoChicken service and is the provider under these terms. Browsing the site or sending an inquiry does not purchase an audit, accept an invoice, authorize repository access, or create a paid engagement. Service terms become part of an engagement when MyBFchef LLC and the customer expressly accept them in writing. The customer must have authority to engage the provider and authorize access to all supplied materials.

Any different or additional engagement terms must be specifically agreed in writing before payment. A later website update does not change an existing agreement or retroactively reduce the refund protection accepted for that engagement.

2. The audit scope

The standard audit covers one agreed repository snapshot, one coding-agent environment, and up to three agreed workflows. Deliverables are a context inventory, evidence-backed findings report, prioritized remediation plan with acceptance checks, and a technical review session. The written agreement must identify the core deliverables and the objective acceptance criteria used to assess whether they are complete.

The report distinguishes confirmed findings, hypotheses, and validation gaps. A supported conclusion that no actionable defect was found can be a valid finding; we do not promise a minimum number of issues. Security certification, legal advice, complete code review, implementation, and controlled before/after agent trials are excluded unless separately agreed.

3. Price, payment, and scheduling

The standard audit fee is USD 2,500 for the stated scope, not a subscription. A larger scope, and any onboarding or implementation work, is quoted in the written agreement. After both parties accept the written agreement, the total invoice is due in full before work begins. The agreement and invoice must disclose applicable taxes and any separately approved charges before payment. Work begins when the provider confirms the required access and materials have been received and starts the audit analysis. No payment or booking is collected on this website, and an inquiry authorizes no charge.

Five business days after access is a planning target, not an unconditional deadline. Confirm the delivery date in writing after reviewing repository fit, access, and capacity. A business day means Monday through Friday, excluding U.S. federal holidays. Customer delays or scope changes require a mutually documented schedule adjustment; they do not silently change the agreed deliverables.

4. Agreed-deliverables guarantee

If a core audit deliverable is missing or materially fails an objective acceptance criterion in the written agreement, email hello@repochicken.com within 7 calendar days after delivery of the audit package. Identify the deliverable, the unmet criterion, and the specific deficiency. We have 5 business days after receiving that notice to supply or correct it at no extra charge. If we cannot, we refund the full audit fee paid for that engagement.

This is a deliverables guarantee, not an unconditional satisfaction or performance guarantee. Dissatisfaction alone does not qualify. It does not promise a minimum issue count, implementation, productivity improvement, lower token costs, or agreement with every evidence-supported conclusion. A minor deficiency corrected within the correction period does not create a refund right.

The agreed materials and access are reviewed before payment. A new repository, a changed snapshot, new workflows, or additional implementation are scope changes, not missing original deliverables. A customer declining an offered review session does not make that session a missing deliverable. Corrections cannot be used to demand unrelated additional work.

Before a contractual refund is issued, the customer must confirm in writing that it has stopped using and distributing the refunded audit deliverables, will not rely on them after the refund, and has deleted copies reasonably within its control except records retained solely for legal, accounting, insurance, or dispute purposes. The customer's license to the refunded deliverables ends when the refund is issued. This does not require deletion of the customer's own code, data, or materials, and it does not limit rights that cannot lawfully be restricted.

The 7-day notice period and correction process do not waive rights that cannot lawfully be limited, including rights concerning non-delivery, fraud, or other legal remedies.

5. Access and customer responsibilities

The customer supplies an authorized, accurate snapshot and identifies material constraints, required redactions, and known access limits. Use read-only access or an agreed export whenever possible. Do not email credentials, production secrets, regulated personal information, or private source code before agreeing a suitable transfer method.

Permission to review files is not permission to execute repository code, change infrastructure, or deploy anything. Any command execution, model-provider use, agent trial, or system change needs separately agreed authorization and an appropriate environment. The customer remains responsible for backups, implementation decisions, testing changes, and production operations.

6. Confidentiality and private materials

Each party must use the other's non-public materials only to perform or receive the engagement, apply reasonable care, and restrict access to people or service providers who need it and are subject to appropriate confidentiality obligations. Information already public without breach, independently developed, or lawfully obtained elsewhere is not confidential under this section.

Before private code is transferred, agree permitted tools and AI/model providers, access controls, retention, and deletion in writing. Do not assume an AI provider is approved or that uploaded material will be excluded from training without checking the applicable service arrangement. Public customer names, logos, testimonials, and case studies require separate permission.

If disclosure is legally required, disclose only what is required and give notice when legally permitted. The agreement should address security-incident notice and any customer-specific data-processing requirements before access is granted.

7. Ownership and permitted use

The customer keeps ownership of its code, data, and supplied materials. While the audit fee remains paid and has not been refunded, the customer may use, copy, and adapt its delivered report and recommendations for its internal business purposes, including sharing with employees and service providers subject to confidentiality.

The provider retains pre-existing templates, methods, tools, and general know-how. Any such material embedded in a paid deliverable is licensed only as part of the customer's permitted use of that deliverable. A full refund terminates the license to the refunded deliverables as described in the guarantee. Neither party acquires the other's trademarks. Any exclusive assignment or different license must be agreed in writing.

8. Changes, cancellation, and suspension

Scope changes require written agreement on work, fees, and schedule before the additional work begins. The customer may cancel for a full refund before work begins as defined in Section 3. After work begins, the fee is nonrefundable except under the agreed-deliverables guarantee, if the provider cannot complete the engagement and no alternative is agreed, by mutual written settlement, or as required by law.

If access is unsafe, unauthorized, incomplete, or outside the agreed scope, the provider may pause the affected work and explain what is needed to continue. The parties must agree a revised plan or settlement for undelivered work. A pause does not eliminate the customer's deliverables guarantee or mandatory legal rights.

9. Limits and reasonable reliance

The audit is a point-in-time professional assessment based on supplied evidence, not a promise that every issue will be discovered. Agent behavior depends on tools, models, settings, and workflows that may change. Findings should be tested before implementation; the audit is not a substitute for security, legal, or regulatory advice.

To the extent applicable law permits, neither party is liable to the other for indirect or consequential losses, and each party's aggregate contractual liability for an engagement is limited to that engagement's paid or payable fees. These limits do not restrict the express refund guarantee, payment obligations, fraud, willful misconduct, gross negligence, confidentiality breaches, infringement of the other party's intellectual property, or liability that cannot lawfully be limited. Specific risk allocation should be reviewed and accepted in the written agreement.

10. Website and inquiry privacy

MyBFchef LLC operates this static website and the RepoChicken service. The website has no user accounts, repository uploads, on-site payments, advertising pixels, or application analytics. Cloudflare hosts the site and routes incoming email to a designated MyBFchef LLC business inbox. Hosting and email providers may process technical information, such as IP addresses and delivery logs, for operation and security.

An inquiry includes information you choose to send, such as your name, email address, company, and project description. MyBFchef LLC uses it to respond, evaluate fit, and manage the business relationship. Company, repository, coding tools, and problem details are optional. Do not include sensitive repository material in an initial inquiry. Private-code processing and retention must be agreed separately.

Contact hello@repochicken.com to request access, correction, or deletion of inquiry information. Some records may need to be retained for existing engagements, accounting, disputes, or legal obligations. Any rights required by applicable privacy law remain available.

Email sent to hello@repochicken.com is forwarded to the provider's designated business inbox. Replies may come from that business email address.

11. U.S. legal framework and disputes

MyBFchef LLC is organized in Texas. These general terms are intended for U.S. business engagements. Applicable U.S. federal and state law governs according to the parties' circumstances and any valid written choice of law. This page does not select a state, court, mandatory arbitration procedure, or class-action waiver.

Contact the provider first to seek a practical resolution. This does not prevent either party from seeking available legal remedies. An unenforceable provision does not invalidate the remaining terms to the extent the law permits. The written agreement should resolve jurisdiction and any customer-specific legal requirements before work begins.

12. Questions about these terms

Email hello@repochicken.com. Keep a copy of the terms and written scope accepted for your engagement.