Contact Tool Fly

Report a Tool Fly problem

If a tool does not behave as expected, send the exact tool name or page address and describe the result you expected compared with what happened. A short sequence of steps is often the most useful information: what you selected, which button you pressed, and what appeared afterward. If an error message is shown, include its wording. You can also mention your browser and device model if you know them.

Please do not attach private source files, identity documents, or confidential information. For a file-processing issue, first try a small non-sensitive sample. Tell us the approximate file type and size instead of sending the original. This helps us investigate while keeping your material on your device.

Before you send a report

1. Refresh the page once and retry, if doing so will not discard unsaved work.
2. Check that the selected file type and output option are supported by the tool.
3. Write down the steps and any visible error before clearing data or closing the page.
4. Send only the details needed to reproduce the issue; never include passwords, payment information, or access codes.

Request a tool or feature

Tool requests are most actionable when they describe a real task rather than only a desired tool name. Explain what you need to accomplish, what makes the current approach slow or difficult, and what a useful result should contain. If you have an example file, describe its general format but do not send confidential or copyrighted material that you are not allowed to share.

Useful details can include input formats, output formats, the device or browser where you would use it, whether it must work offline, and any accessibility needs. A focused request helps us assess whether it can run safely in the browser, whether it requires a backend, and what limitations should be disclosed. Sending a request does not guarantee that it will be built or provide a delivery date.

Privacy and data handling questions

Many Tool Fly utilities run locally in your browser, but some features make network requests. For example, contact messages are sent for email delivery and Text to Speech sends text to its configured backend. The Privacy Policy explains these distinctions, browser-local storage, and external font requests.

If your question concerns data you entered, tell us which feature you used and roughly when. Do not paste sensitive text into a new message just to identify it. We do not have a general visitor account portal from which you can download all activity, and we cannot remotely erase data stored only in your browser profile. Clear local site data through your browser settings to remove saved local preferences or drafts. Messages already delivered to email may remain in provider systems.

What happens after sending?

The contact form sends the email address, selected topic, and message to the configured backend for email delivery to toolfly8@gmail.com. A successful confirmation means the backend accepted the message for delivery; it does not guarantee that a reply will arrive by a particular time or that an email provider will not filter it. If the form reports a delivery error, you can email the address directly.

We review reports and requests as time and project priorities allow. We may ask a clarifying question if a report is difficult to reproduce. We do not promise a specific response time, resolution, feature release, or support level. Please avoid submitting the same request repeatedly; one clear message with the relevant details is easier to review.

Do not use this form for emergencies or time-critical support. It is not monitored as an emergency channel and should not be used to report an immediate threat to personal safety.

Accessibility and other feedback

If you encounter a keyboard, screen-reader, contrast, zoom, or other accessibility barrier, tell us the page or control involved and what assistive technology or browser you were using, if you are comfortable sharing it. A description of the barrier is more useful than personal medical information, which we do not need.

You can also send general feedback about confusing instructions, missing formats, language support, or workflow improvements. We appreciate specific, constructive examples, and we use them to understand where the site can be clearer. There is no need to share personal data to give feedback.