- General, tool requests, bugs — hello@furtu.xyz
- Privacy questions and corrections — privacy@furtu.xyz
- Security reports — security@furtu.xyz
What helps us fix a bug faster
- Which tool you were using, and the link to it.
- Your browser and operating system — the About row in your browser menu is enough.
- What you expected, and what happened instead.
- The error text, if there was one. A screenshot of the whole workspace is ideal.
- A file that triggers it, if you can share one safely. Please do not attach anything sensitive when a description will do.
Requesting a tool
Requests are more useful with an example. “A tool that does X to Y files” is far more actionable than a tool name, and telling us where you currently do the job is even better — it usually reveals whether the real need is a conversion, a limit, or something the format does not support.
If a request cannot be done properly in a browser, we will say so rather than shipping a version that quietly loses quality. The changelog keeps a running list of what is planned and what is not going to happen.
Response time
Furtu is a small project, so expect replies rather than a ticket queue. Security reports are prioritised. There is no support plan with an SLA, because there is no paid tier to attach one to.