Home/Contact Us

Contact Us

We'd love to hear from you. Whether it's feedback, a bug report, or a tool request — reach out anytime.

Email

General inquirieshello@i-love-tools.com
Technical supportsupport@i-love-tools.com
Privacy concernsprivacy@i-love-tools.com

Tool Requests & Feedback

Have an idea for a new tool? Found a bug? Let us know and we'll do our best to make it happen.

Response Time

We typically respond within 24–48 hours on business days.

How to reach us — and what to expect

i-love-tools.com is maintained by a small independent team. We do not have a 24/7 support desk, a chat widget, or an outsourced help line — every message goes to a real person who reads it personally. That means responses are sometimes slower than you would get from a large platform, but the answers come from someone who can actually fix the problem.

Which email to use

  • hello@i-love-tools.com — general feedback, tool requests, partnership questions, anything that does not fit a category below.
  • support@i-love-tools.com — bug reports, broken tools, browser compatibility, or anything you expected to work and didn't. Including a screenshot and a description of your browser/OS speeds things up enormously.
  • privacy@i-love-tools.com — GDPR data requests, CCPA inquiries, consent revocation issues, or anything related to how data is handled. We aim to acknowledge privacy emails within 48 hours and complete formal requests within 30 days as required by GDPR.

What to include in a bug report

The most helpful bug reports answer three questions: what did you do, what did you expect, and what happened instead? Add the following details to make a fix possible:

  • The full URL of the page where the bug happened.
  • Browser name and version (Chrome 124, Safari 17.4, etc.).
  • Operating system and device (macOS 14, Windows 11, iPhone 15 iOS 17, etc.).
  • A screenshot of the unexpected state. If the issue involves a specific file, mention the file type and approximate size.
  • Any console errors visible in the browser developer tools (optional, but extremely useful).

Suggesting a new tool

We add new tools regularly based on user requests. The most likely-to-build candidates are tools that:

  • Solve a self-contained task — convert format A to format B, calculate value X from inputs Y and Z.
  • Can run client-side without uploading user data.
  • Are searched for by name (i.e., people already know they want them).
  • Don't already exist on the site in a different form.

When you write in, please describe the actual workflow you would use the tool for. A request like “convert MIDI to MP3” gets prioritized faster when accompanied by “I record demos on my keyboard, want to share with friends who don't have a synth.” The context helps us pick which of the obvious-sounding tools actually fit a real workflow.

Reporting content issues

The deep-content explanations attached to certain tools are written and reviewed by humans, but they cover technical and sometimes regulatory ground (financial formulas, health metrics, building codes). If you find an inaccuracy, an outdated statistic, or a passage that misrepresents a topic, we want to know. Email hello@i-love-tools.com with the URL and the correction — citations to authoritative sources make the fix straightforward.

Copyright and takedown requests

If you believe content on the site infringes your copyright, please send a notice to hello@i-love-tools.com with: identification of the copyrighted work, the URL of the allegedly infringing material, your contact information, and a good-faith statement that you are authorized to act on behalf of the copyright owner. We review takedown requests within 7 business days.

Press and partnerships

For media inquiries, syndication, or partnership proposals (white-labeling a tool, embedding a calculator in your site, etc.), email hello@i-love-tools.com with “Press” or “Partnership” in the subject line. We do not currently accept guest posts or paid placements within the deep-content sections.

Response time, honestly

Most emails get a reply within 1–3 business days. Bug reports with reproducible steps tend to be answered fastest because we can act on them immediately. Vague messages (“something is broken”) take longer because they require a back-and-forth to diagnose. Privacy and copyright matters are prioritized regardless of how busy the inbox is.

We do not have a phone number or postal address available for public correspondence. Everything is handled by email so that there is a written record on both sides.