Contact
CodeLint.Dev is built and maintained by Mimamsa, so messages go to a person rather than a ticket queue. Bug reports, corrections, tool suggestions and privacy questions are all welcome — and corrections to the finance and tax calculators are the ones most worth your time to send.
The only channel, and the fastest. Expect a reply within two business days; corrections and security reports are looked at sooner. There is no contact form, because a form would need to send your message through a third-party service — email keeps it between us.
support@codelint.devWhat to reach out about
Report an error in a calculator or guide
The most useful message you can send. Several tools here deal with tax, loans and investments, where a wrong formula has real consequences — so corrections take priority over everything else. Tell us the page, the inputs you used, the result you got and the result you expected. Verified errors are fixed and the page is re-dated.
Report a bug
A tool crashed, produced nothing, or behaved oddly. Include the tool, your browser and version, what you entered, and what happened. If the browser console showed an error, paste it — it usually points straight at the cause.
Suggest a tool
Missing a utility you reach for regularly? Suggestions genuinely shape what gets built next. Describe what it should do and give a typical input and expected output — that is usually enough to judge whether it can work client-side.
Privacy questions and data requests
Ask how any specific tool handles your data, or exercise a right under GDPR, UK GDPR or CCPA. Because no accounts exist and tool input is never transmitted, there is usually very little held about you — but ask, and you will get a straight answer.
Report a security issue
Responsible disclosure is welcome and appreciated. Please email rather than opening anything public, and give us a reasonable window to fix it before disclosing. See the note below for what to include.
Reporting a security issue
Email support@codelint.dev with “security” in the subject line. Useful reports include the affected URL, the steps to reproduce, and what an attacker could actually achieve. A proof of concept helps enormously.
Please test only against your own browser session, do not access or modify data belonging to anyone else, and avoid anything that would degrade the site for other visitors. There is no paid bounty programme — this is a free site run by one person — but you will get a prompt reply, a fix, and public credit if you would like it.
Worth knowing before you report: nearly every tool runs entirely in your browser, there are no user accounts, and no tool input is ever transmitted or stored. That rules out a large class of issues by design.
Things we cannot help with
- Recovering something you entered. Tool input is never sent to us and never stored, so there is nothing to recover. Closing the tab is genuinely the end of it.
- Financial, tax or legal advice. We can explain how a calculator works and fix it if the method is wrong. We cannot tell you what to do about your mortgage, your tax return or your portfolio — that needs a qualified professional who knows your circumstances.
- Third-party data disputes. Exchange rates, crypto prices and BIN records come from external providers. We can look at how the data is displayed, but not correct it at source.
- Debugging your own code. Happy to fix a tool that gives a wrong answer. Not able to act as general engineering support for the project you are working on.
Other ways to connect
For how your data is handled, see the Privacy Policy. For the terms covering use of the tools, see the Terms of Service. For who builds this and why, see About.