Privacy and data
quodeq has no account, no telemetry and no quodeq server. This page lists exactly what leaves your machine, and where quodeq writes. The legal text, including the data processing agreement, is on the privacy page.
What leaves your machine
| Your code | Sent only to the model you choose, through that provider's CLI or API, while an evaluation runs. With a local model (Ollama, llama.cpp, omlx) nothing leaves the machine. |
| The update check | Once a day, quodeq asks pypi.org for the latest version number. The request carries no data about you or your projects. Turn it off with QUODEQ_NO_UPDATE_NOTIFIER=1 or in Settings; it is already off when CI is set. |
| A GitHub sign-in | Only if you make one in quodeq. It is stored in your system keychain, used only for github.com, and only inside the clone process. API keys for providers are stored the same way. |
| A SARIF file | Code snippets stay out of it unless you pass --with-snippets. Whatever you upload to code scanning leaves with it. |
| A shared evaluations repository | Only if you connect one. Published evaluations go to the git remote you chose and nowhere else. |
Where quodeq writes
| ~/.quodeq | Projects, runs, findings, the score cache and your settings. Delete it and quodeq starts fresh. |
| ~/quodeq/repos | Working copies of remote repositories you add by url. Change it with QUODEQ_REPOS_DIR. |
| .quodeq/ in a repository | Per-project standard overrides and dimension visibility, so a team can commit them. |
| ~/.quodeq/copilot | The dedicated GitHub Copilot profile, if you use that provider. |
This website
quodeq.ai counts page views with Cloudflare Web Analytics, which sets no cookies. Videos load from youtube-nocookie.com only when you press play.
Licence
quodeq is free software under the MIT licence. The source is on GitHub, and so is the source of this website.