Skip to main content
MathKit

Contact

Found a bug in a calculator? Want a new tool? Tell us — feedback directly shapes what gets built next.

What to include in a bug report

Three things make a report actionable in one pass: the calculator name, the exact numbers you entered, and what you expected versus what appeared. If the page showed a red validation message (for example a field rejecting 0 or a non-integer), include how the input was written. A screenshot is helpful but not required.

What this address is for

  • Wrong or unclear results — the highest-priority mail we get.
  • Wording corrections in FAQs, guides or worked examples.
  • Tool requests — describe the math problem you keep reaching for.
  • Privacy questions, including anything about ad scripts or analytics.

What happens after you write

The mailbox is read in batches, not minute-by-minute — a reply usually lands within a few days. Fixes ship as site updates you can see directly on the page you reported. Nothing you send is added to any marketing list; the mail is used for the reply and, if relevant, the underlying fix. Nothing is transmitted from the form itself — it opens your own email client with the fields filled in, so the message leaves your device only when you press send, on your own account.

Or email us directly at[email protected]