Contact
Contact channel and review time
For bug reports, tool suggestions, content questions, or any other question related to FunnyTools, email btcson66@gmail.com. If the issue is something other users might benefit from tracking, or you'd rather have the discussion be public, you can also open an issue directly at https://github.com/btcson66-rgb/funnytools-win/issues.
General maintenance and content-correction messages are usually reviewed within 3 business days. Issues that need reproduction, comparison against an official source, or actual development work can take longer — sometimes a few weeks — and because this is a small-scale operation, an individual reply is not guaranteed for every message, though every message is read.
What to include when reporting a bug
When reporting a bug, include the tool page URL, the approximate inputs you used (fictional data is fine — you don't need to send real personal information), the result you expected, the result you actually got, your device type, and your browser version. The more specific this is, the faster the same behavior can be reproduced.
For example, if a PDF tool produces a blank page in a specific browser, or a statistics calculator returns an error for a particular sample size, naming the tool, the browser version, and the exact inputs used is usually enough to start investigating.
Suggesting a tool or requesting a content fix
When suggesting a new tool, briefly explain the problem it should solve, what inputs it should accept, what output it should produce, and the situation where you'd actually use it. Specific suggestions are easier to prioritize than general requests.
For a content correction, include the page URL and the exact sentence or result that looks wrong. If the issue depends on a public rule, formula, or current regulation, include a link to a reliable source so the published content can be compared against it directly.
GitHub Issues and business inquiries
GitHub Issues is a public channel — anyone can see what you reported and how it was handled. It works well for reproducible bugs or feature requests that don't involve private information. Do not post private or confidential data in a public issue.
There is currently no separate inbox for business partnerships, licensing, or media inquiries. Questions of that kind can be sent to the general contact address, but they may be reviewed more slowly than bug reports and tool suggestions, which are the current priority.
Safety reminders and what support cannot do
Do not email or post passwords, identity documents, financial statements, private student records, medical records, or other confidential files, either by email or on GitHub. This site has no dedicated process for storing sensitive files securely, and none of that is needed to reproduce most technical issues.
Most technical problems can be reproduced with a small set of fictional test data instead — for example, a fake name list to test a random-grouping tool, or made-up figures to test a loan calculator. That demonstrates the problem without exposing your real information.
Messages are used for site maintenance, but a reply time is not guaranteed. FunnyTools cannot certify a calculation result, recover data from your browser, or act as an intermediary between you and an employer, school, bank, government agency, or third-party service.
The site does not provide live support, personal financial planning, or legal, medical, or tax advice. For anything affecting formal rights or obligations, contact the relevant official source, financial institution, HR department, or a qualified professional directly — treat calculator results here as a starting point only.
When you're ready to send a message, email btcson66@gmail.com or open an issue on GitHub — either channel reaches the same person.
You can write in English or Chinese — both are read by the same person, so there's no need to translate your message first.
A specific report is far more useful than a general one. "The PDF merge tool doesn't work" is hard to act on; "merging two PDFs over 20MB on Chrome for Android produces a corrupted file, but the same files merge fine on desktop Chrome" can usually be reproduced and fixed directly. The extra time spent adding detail up front tends to save days of back-and-forth later.
If a fix is made in response to your report, it's usually reflected directly on the tool page rather than announced individually — checking the page again after a few days is often faster than waiting for a reply confirming the change.
Response volume varies. A quiet week might mean same-day review; a busier stretch can push simple confirmations back by several days. If the issue is urgent for you and you haven't heard back, a short follow-up referencing your original message, or the GitHub issue number if you used that channel, is a reasonable way to bump it.