Contact

Email is the only channel: jeromell@be-winner.com. This is a one-person site — no phone line, no ticket form, no chat widget — and the same person who built the tools answers the mail. Email works for tool bugs, factual corrections, privacy questions, and advertising.

Corrections and tool bugs

For a bug report or correction, four details make the difference between a message that gets fixed in one pass and one that earns a follow-up question:

Do not attach confidential images. The converters run locally in your browser, so there is no server pipeline that could open an attachment anyway; a description of the file type, its rough size, and the error message is enough to reproduce almost every issue. The same four details work for questions that are not bugs — a format behaving oddly, a string that will not decode, an image that renders in one client but not another.

What happens next

Support is best-effort, and that is stated here rather than hidden behind a ticket number. Messages are read in arrival order, fixes are made in public — code changes land in the GitHub repository, where you can watch an issue move from report to patch — and there is no guaranteed response time. For questions the site already answers, the FAQ is faster than waiting on an email.

How your email is handled

Message content is used for one purpose: reproducing and fixing whatever you describe. It is read manually by the site operator, it is not fed into any analytics or advertising system, and it is never added to a mailing list. If a correction changes a public page, the fix shows up on that page — your name and address do not. The privacy policy covers what the site itself collects from visitors.

Advertising

Advertising and partnership inquiries are welcome at the same address. The site runs Google AdSense; see the privacy policy for cookie and vendor details, and ads.txt for authorized sellers. Two things hold regardless of budget: ads are never placed inside converter controls, and guides carry no paid recommendations.

What we will not do

For who runs the site and why the tools work the way they do, see About and the editorial policy.