Skip to main content
Say hello

We’re here to help.

Questions, feedback, ideas, bug reports. Everything reaches the same inbox and gets a human reply.

Kaltask is operated by Alkyrie (“we”, “our”, “us”), the parent company that runs this site. Support email lives on the parent domain (alkyrie.com) so a single team handles inquiries across all of our properties and you get the same response time regardless of which tool you arrived through.

Get in touch

Operator

Alkyrie, operator of Kaltask

Response time

24 to 48 hours on business days

Monday to Friday, 9am to 5pm Pacific

Quick feedback

What to write about

Pick the bucket that fits your message. We do not use a ticket system, so the more specific your subject line, the faster the right person picks it up.

Technical support

A tool failing to load, a button that does nothing, a chart that does not render, an export that downloads an empty file. Tell us which tool, which browser, and what you saw on screen.

SLA: Response within 24 to 48 hours on business days.

Incorrect calculation

You ran the math by hand or in a spreadsheet and got a different answer. Include the inputs you used, the result the tool gave you, the result you expected, and the source you trust for the correct value.

SLA: Treated as the highest-priority bug class. Triage within one business day; root-cause and fix on the schedule the bug allows.

Feature request

A tool you wish existed, an input we are missing, an output that would make an existing tool more useful, a comparison view we have not built. The clearer the use case, the more likely we can pick it up.

SLA: Acknowledged within 48 hours. Build decisions take longer because they trade against other work in the queue.

Content correction

A glossary definition that is outdated, a formula that uses an old constant, a category description that no longer matches the tools in it. Cite the page URL and the specific line that needs fixing.

SLA: Updated in the next deploy after we verify the source you cited.

Press, partnership, integration

Coverage requests, embedding a tool, an API for a tool that does not have one, a co-branded calculator. Tell us what you are building and what success looks like.

SLA: Routed to the right person within 3 business days.

Legal, privacy, security

Privacy requests under GDPR or CCPA, data subject access requests, security disclosures, intellectual property concerns. Use a subject line that starts with "Legal", "Privacy", or "Security" so it skips the general queue.

SLA: Acknowledged within 5 business days; substantive response within 30 days (45 days for CCPA requests, with notice).

How to write a bug report that gets fixed

The single hardest part of fixing a tool bug is reproducing the problem on our end. A reliable repro turns a multi-day investigation into a multi-minute fix. The following six items, in order, give us everything we need:

  1. The exact URL of the tool you used (copy from the browser’s address bar).
  2. The inputs you entered. Cut and paste the values rather than describing them; small differences in formatting matter.
  3. What the tool produced as a result.
  4. What you expected the result to be, and the source you are comparing against (textbook, spreadsheet formula, official table, another reputable site).
  5. Your browser and version (Chrome 134 on Windows 11, Safari 18 on iPhone, etc.). The browser’s About page shows this.
  6. Any error messages visible in the browser’s developer console, if you know how to open it. This step is optional but extremely helpful when the bug is a JavaScript failure.

Screenshots help. So does a short screen recording if the bug is timing-dependent or the steps are hard to describe in text. There is no upload limit you will hit through the contact form; attach what makes the problem easiest to reproduce.

What we will and will not do

We answer every legitimate message from a real person. Routine support, bug reports, feature requests, and corrections all get a human reply, not an auto-responder.

We do not run a paid support tier and we do not offer custom development through the public contact channel. Partnership and integration discussions go through the dedicated bucket above. We do not provide tax, legal, medical, financial, or professional advice over email; the tools are general-purpose utilities and the results carry the disclaimers documented on each tool page and in our Terms of Service.

If you ask a question we cannot answer, we will say so plainly and point you toward a source that can. We do not guess at answers in domains we are not qualified to speak on.

Other ways to reach us

  • - the floating feedback button on every page. Best for one-liner reactions and quick bug reports.
  • Methodology - how we source formulas and verify each tool before release.
  • About - what Kaltask is, what counts as a tool, and what we will not do.
  • Privacy Policy - the specific data we collect, the partners we use, and how to opt out.
  • Terms of Service - usage rules, accuracy disclaimers, and limitation of liability.
  • Tools directory - the full library, organized by category.