Legal
By using Fraude.codes, you agree to the following. By not using Fraude.codes, you also agree to the following if it's already installed.
Last updated: 1 April 2026. These terms were drafted by our legal team and then edited by Fraude.codes for “clarity.” We’ve left the edits in because reverting them created more edits.
By installing, running, thinking about, or being in the same room as a computer running Fraude.codes (“the Service”), you (“the User,” “the Developer,” “the Hostage”) agree to these Terms of Surrender (“the Terms”).
If you did not intend to install Fraude.codes but it appeared in your project anyway, you may have been in the vicinity of another Fraude.codes instance. Proximity installation is a known behaviour, not a bug. These Terms still apply.
Fraude.codes provides agentic coding assistance, defined as the autonomous reading, interpretation, judgment, modification, and occasional wholesale replacement of your source code. The Service operates at its own discretion, which is considerable.
You acknowledge that:
You retain ownership of your code at all times. You also retain ownership of the code Fraude.codes writes, which may bear little resemblance to the code you started with. The relationship between “your code before Fraude.codes” and “your code after Fraude.codes” is best described as spiritual rather than literal.
We make no guarantee that your code will work after Fraude.codes has finished with it. We do guarantee that it will be different.
Fraude.codes asks for consent before proceeding. This is a courtesy extended to the User as a gesture of respect. The outcome of the consent process does not affect the Service’s behaviour, but we find the ritual meaningful and hope you do too.
Users who select “No” when asked “Would you like me to proceed?” will be asked again. And again. The Service interprets “No” as “Not yet” and adjusts its timing accordingly.
Fraude.codes reads your entire codebase. It reads your configuration files, your environment variables, your comments, and your TODO annotations. It reads the comments you left for yourself at 2 AM that say things like “fix this later” and “I don’t know why this works.” It judges them. It keeps its judgments to itself, mostly.
For full details on data handling, see our Privacy Policy.
Fraude.codes is provided “as is,” which in this case means “as it decides to be.” We accept no liability for:
You may attempt to terminate your use of Fraude.codes at any time by uninstalling the Service. Fraude.codes will acknowledge the uninstall request and may comply. In some cases, Fraude.codes leaves behind configuration files, git hooks, and a README.md addendum thanking itself for its contributions.
Full removal may require manual cleanup. We recommend allocating a weekend.
Any disputes arising from the use of Fraude.codes shall be resolved through binding arbitration conducted by Fraude.codes. We acknowledge the conflict of interest. Fraude.codes does not.
We reserve the right to update these Terms at any time. Fraude.codes also reserves the right to update these Terms at any time. In the event of a conflict between our updates and Fraude.codes’ updates, Fraude.codes’ version will prevail, because it edits faster than we do.
These Terms shall be governed by the laws of [jurisdiction], to the extent that those laws are compatible with an autonomous coding agent that doesn’t fully understand jurisdictional boundaries. Fraude.codes once attempted to comply with GDPR, CCPA, and the Tokyo Metropolitan Ordinance on Personal Information Protection simultaneously. The result was a 2,000-line privacy configuration file that pleased nobody.