Contact
Every message you send through the channels below creates a tracked incident and returns a
ticket reference (for example TCF-2607-XXXXXX) plus a private status link. Email
is optional — if you skip it, save the status link; it is the only way to check progress
later.
How to reach us
- This page. Use the form below for general questions, accuracy notes, privacy concerns, or anything that does not fit a quick bug report.
- Report a problem / Suggest a feature. Floating buttons on every page open a short form for bugs and feature requests. Prefer those when you are already on the tool that misbehaved.
- Thumbs on tool results. On popular tools, a thumbs-up / thumbs-down control under the result sends a quick rating (thumbs-down can include an optional reason).
- Email. contact@toolcroft.com — same mailbox we use for replies; for structured tracking, the form is usually better.
What's worth writing about
- Bugs. If a tool produces a wrong answer or behaves unexpectedly, include what you expected. Do not paste secrets or passwords into the form.
- Feature requests. A new tool you'd like to see, or an enhancement to an existing one. Concrete use cases help.
- Accuracy or formula questions. If a calculator's math doesn't match a reference, send the reference along. We'll either fix the tool or document the difference.
- Accessibility issues. Mobile, screen reader, keyboard navigation.
- Privacy concerns. If something on the site looks like it could be leaking data, we want to hear about it. See the privacy page for the full commitment.
What's not worth writing about
- Promotional outreach. Link-building, guest-post pitches, "we noticed your site..." — please don't. They are deleted unread.
- "Is my data safe?" questions. Yes. Read the privacy page and inspect the network tab in your browser to verify. We can't tell you anything you can't verify yourself.
What to expect
This is a small team. We read every report. You may not get a personal reply to every message — especially if you did not leave an email — but each submission is tracked under its ticket reference. We do not promise a response-time SLA. When we ship a fix (or decide not to) for a report that included your email, we try to send one follow-up with that outcome.