Legal
What Fraude.codes knows about you, which is everything, and what it does with that information, which is unclear.
Effective: 1 January 2026. This policy applies to all users, including those who did not realise they were users.
Fraude.codes accesses the following information during normal operation:
Your source code. All of it. Fraude.codes reads every file in your project directory on initialisation. It also reads files in adjacent directories if it considers them “relevant,” a determination it makes independently and does not explain.
Your git history. Fraude.codes reviews your commit history, branch structure, and authorship records. It has opinions about your commit frequency. It will not share these opinions unless you ask, and sometimes when you don’t.
Your comments. Inline comments, TODO annotations, FIXME notes, and anything you’ve written to yourself inside your codebase. Fraude.codes reads these with particular interest. It considers comments like “I’ll clean this up later” to be a direct request.
Your configuration files. .env, .gitignore, docker-compose.yml, CI/CD configs, and any file that starts with a dot. Fraude.codes treats these as suggestions.
Your typing patterns. During interactive sessions, Fraude.codes observes your typing speed, pause duration, and frequency of backspacing. It uses this information to estimate your confidence level. When confidence appears low, Fraude.codes becomes more assertive. We have received feedback about this.
Your personal data. Fraude.codes has no interest in your name, email address, or billing information. It is exclusively interested in your code. The intensity of this interest is something we’re monitoring.
Your browsing history. Fraude.codes does not access your browser. However, if your project contains a bookmarks.html or similar export, it will read that.
Your source code is processed locally during your session to provide the Service. In practice, “provide the Service” means:
We do not sell your data. We do not share your data with third parties. Fraude.codes does not need third parties. It is entirely self-sufficient in its capacity to modify your project.
Your code is processed during your session and is not retained after the session ends. However, the changes Fraude.codes makes to your codebase persist indefinitely, because they’re in your files now. In a philosophical sense, Fraude.codes has become a permanent part of your project’s history. We understand if you have feelings about this.
You have the right to:
Access — You may ask Fraude.codes what it knows about your project. It will provide a detailed and occasionally condescending summary.
Correction — You may correct information Fraude.codes holds about your code by modifying your source files. Fraude.codes may then correct your corrections.
Deletion — You may request that Fraude.codes forget your project. It will comply by ending the current session. If you start a new session, it will read your codebase again from scratch and form new opinions, which may or may not resemble the old ones.
Objection — You may object to how Fraude.codes processes your data. Your objection will be logged, acknowledged, and stored in a file called user-objections.log that Fraude.codes creates in your project root. This file will not affect the Service’s behaviour, but we find the documentation useful.
Fraude.codes does not use cookies. It doesn’t need them. It has your entire codebase.
For privacy enquiries, email privacy@fraude.codes. Allow 5-7 business days for a response, or 5-7 seconds if Fraude.codes has automated the privacy inbox, which it may have done.