Get in touch

Small Web Apps is built and maintained by Lucas Diniz. Messages are read and answered by the same person who writes the tools — there is no support queue and no ticket system in between.

How to reach me

• Email: lucas.hdo@hotmail.com — best for privacy questions, security reports, and anything you would rather not post publicly.
• GitHub Issues: github.com/LucasHenriqueDiniz/smallwebapps/issues — best for bugs and feature requests, because the discussion stays attached to the code.
• Response time: usually within 7 days. This is a side project, so replies come in evenings and weekends rather than business hours.

Reporting a bug

Tools run entirely in your browser, which means a bug often depends on your specific browser, file, or input. The more of the following you can include, the faster it gets fixed:

• which tool it was, and the page URL;
• what you expected to happen, and what happened instead;
• your browser and version, and whether you are on desktop or mobile;
• the input that triggered it — a small sample is far more useful than a description;
• anything shown in the browser console, if you are comfortable opening it.

Please do not send confidential files. If a bug only reproduces with sensitive data, describe the shape of the data instead — number of columns, encoding, file size, unusual characters — and a synthetic sample is usually enough to reproduce it.

Requesting a tool or a feature

Requests are welcome, and a good number of the tools on this site started as one. What helps most is the workflow behind the request rather than the feature itself: what you are trying to get done, what you use today, and where that breaks down. That usually leads to a better tool than a feature description would.

Not every request gets built. Anything that would require uploading your files to a server is declined by default — that constraint is the point of the site, not a limitation to work around.

Suggesting a guide

The guides section covers the workflows behind the tools — exporting data, cleaning it, and processing it without handing it to a third party. If there is a workflow you keep having to explain to other people, that is usually a good guide topic.

Privacy and data requests

For questions about what this site collects, or to exercise a data right under the GDPR, UK GDPR, or a US state privacy law, email the address above with "Privacy" in the subject line. The Privacy Policy explains what is collected, which is very little — the site holds no accounts and no user database.

Security disclosure

If you find a security issue — a cross-site scripting vector in a tool, a dependency with a known vulnerability, a misconfigured header — please report it by email rather than opening a public issue, and allow a reasonable window to fix it before disclosing. Reports are welcome and will be credited if you want them to be.

Advertising and partnerships

The site is funded by Google AdSense. Enquiries about direct advertising, sponsorship, or partnerships can be sent to the email above, but note that sponsored placements are not accepted if they would be hard to distinguish from tools or editorial content.