The fastest way to reach CalcTide is by email at [email protected]. Use that address for calculator bugs, editorial corrections, accessibility issues, tool suggestions, and questions about how a page works. Email is also the best option when you need to include screenshots, calculations, or source links that help us reproduce a problem.
Clear reports help more than long reports. If something on the site looks wrong, tell us exactly which page you used, what values you entered, what result you saw, and what you expected instead. If the issue is about wording rather than math, quote the sentence or section heading so we can review the right place quickly. We read submissions in batches and prioritize issues that affect correctness, safety, broken behavior, or misleading explanations.
A good bug report makes it easy to reproduce the issue without any guesswork. Most calculator problems fall into one of four buckets. Either the formula is wrong, an input is validated the wrong way, a unit conversion does not match the label, or the copy around the tool describes behavior the tool does not actually follow. The more of that context you provide up front, the faster we can verify the issue.
Screenshots are helpful when the problem is visual, but they are not a substitute for the actual inputs. If a chart overlaps text, a button disappears, or a field label gets cut off, send the screenshot. If the math looks wrong, send the inputs first and the screenshot second.
Some messages are not bugs in the technical sense. They are questions about assumptions. A page may use a standard formula that differs from a house rule, a classroom shortcut, a local practice, or a different published convention. In those cases, the best report is a methodology report. Tell us which assumption you expected, which assumption the page appears to use, and which source you believe should govern the calculation.
This matters most on finance, health, and construction pages, where two reasonable methods can produce different results. Interest can be compounded on different schedules. Body metrics can use different formulas. Material estimates can change with waste factors, densities, or job-site assumptions. We review those reports carefully because the right fix is sometimes a formula change, sometimes a clearer label, and sometimes a stronger limitations section.
We want corrections to the copy as much as corrections to the math. If a definition is unclear, an example is incomplete, an FAQ leads a user in the wrong direction, or a disclaimer needs tighter wording, send a note. Please include the page URL, the relevant section heading, and a short explanation of what feels inaccurate or hard to follow.
Helpful editorial notes often do one of three things. They point out a missing assumption. They identify a phrase that could be read too broadly on a sensitive topic. Or they catch a practical mismatch between what a real user needs and what the page currently explains. Those details matter because trust is not only about correct formulas. It is also about correct framing.
New tool requests are welcome. If you want a calculator that is not on the site yet, tell us the exact problem you are trying to solve rather than only the title you want to see. For example, "I need to compare biweekly and monthly loan payments with fees" is more useful than "please add a loan tool." The best suggestions explain the inputs people already have, the output they need, and the situation where the result would help.
If there are existing tools on other sites that handle the problem well, you can link them as reference points. That does not mean we will copy their structure or wording, but it does help us understand search intent, edge cases, and related questions. Requests tied to a broader topic cluster are especially helpful because the site works best when a tool fits into a clear category and can connect to related pages on the calculators hub or in the guides library.
If a page is hard to use with a keyboard, screen reader, zoomed text, or mobile device, please tell us. Accessibility feedback is product feedback. The same goes for form layouts that are confusing, labels that do not explain the required unit, result blocks that are hard to scan, or navigation that makes it difficult to find related tools.
When possible, include the device, browser, operating system, and a short description of what you were trying to do. "The calculate button is covered by the keyboard on iPhone Safari" is actionable. "Mobile is weird" is not. We are more likely to fix an issue quickly when we can picture the exact failure state.
CalcTide publishes calculators and explanatory content. We do not provide personal medical advice, financial advice, legal advice, tax advice, engineering sign-off, or emergency support. If your question requires a judgment about your personal diagnosis, treatment plan, lending decision, tax filing, contract, or structural safety, the right next step is a qualified professional, not an email exchange with the site.
We also do not review confidential documents or private records as a consulting service. Please do not send Social Security numbers, bank account data, full medical records, insurance IDs, tax returns, account passwords, or anything else you would not want sitting in an email inbox. If you need to show an example, redact personal details first. For most bug reports, numbers can be rounded or anonymized without making the issue harder to reproduce.
Editorially, our goal is to improve the clarity and accuracy of the site. That means we may accept a correction without adopting suggested wording verbatim. We may also decide that the right fix is to tighten a limitation note, expand an example, or state an assumption more plainly rather than rewriting a whole page around one preference.
We review messages in batches. Reports that affect factual accuracy, user safety, or broken page behavior come first. After that, we work through editorial improvements, coverage suggestions, and lower-impact UX issues. Because the site includes hundreds of pages, we cannot promise that every message will receive a detailed personal reply. Even so, well-documented reports are valuable because they help us confirm what needs attention.
If your message points to a real issue, the fix may show up as a code change, a copy revision, an updated example, a new limitation note, or a broader audit of related tools. One correction often reveals a class of similar problems elsewhere on the site. That is another reason we ask for concrete detail. A precise report does not just help one page. It can improve a whole cluster of pages.
If you email us, we will receive whatever information you choose to include in that message, such as your email address, the content of your note, and any attachments you send. Use good judgment. Send only the detail needed to explain the issue. For the general privacy rules that apply to site use, read the privacy policy.
If you want context on how we approach accuracy, limitations, and page updates before writing in, the about pageexplains the editorial and product standards behind the site. If your question is about the rules for using CalcTide, see the terms of service. Those pages answer many common questions and can help you decide what kind of report to send.
Email [email protected] with the exact URL, your inputs, the result you saw, and the reason you think something should change. Keep personal information out of the message unless it is absolutely necessary. If the issue involves health, money, law, or safety, remember that CalcTide is an educational calculator site, not a professional advisory service.