Contact
Questions about Fieldkit’s tools, bugs, privacy, or advertising? Email is the channel.
Write to alexanderviolino1@gmail.com. Messages go to Alexander Braz, who maintains Fieldkit. That address is the publisher contact for site and ads matters on use-field-kit.com. Please do not send passwords, production secrets, API keys, or large confidential dumps — the tools are meant to run locally in your browser, and email is not a secure dropbox for sensitive payloads.
What to write about
Useful messages include bug reports (which tool, which browser and version, what you pasted or clicked, and what went wrong), requests for a new small utility that fits the “one page, one job” and client-side model, and questions about privacy or how advertising on the site works. Policy topics are welcome; see also the Privacy Policy and FAQ.
Feature ideas land best when you describe the interruption they solve and why a browser-only page is enough. Requests that need accounts, team sync, server-side execution, or paid APIs are usually declined because they conflict with Fieldkit’s scope — but a short note still helps us know what people are looking for.
What makes a bug report easy to act on
- The tool's address, for example
/tools/json-to-csv. - Your browser and its version, and whether an extension such as an ad blocker is active.
- The smallest input that shows the problem, with any real names, tokens or secrets replaced by fake values.
- What you expected, what happened instead, and the exact text in the Status cell of the readout.
For a mistake in a guide, mention the guide, the section, and the source you are relying on, such as an RFC section or a manual page.
Response expectations
Replies are best-effort. This is a small free project, not a support desk with guaranteed SLAs. Clear subject lines and enough detail to reproduce an issue help a lot. There is no ticket system, live chat, or phone line.
Not for urgent production incidents
If a production system depends on a conversion, run the same logic in your own environment (editor, CI, or a local script). Fieldkit pages can change, ads can fail to load, or a browser update can break a path — treat the site as a convenience, not a dependency for outage response.