We read everything that arrives. We cannot promise a response time — this is a free tool with no support desk behind it — but a clear bug report with a reproduction will always get further than a general complaint.
What to write about
- Something is broken
- The most useful report names your browser and version, your operating system, roughly how large the image was, and what you expected against what happened. If a specific photo fails, describe it — “dark hair against a dark background”, “a glass bottle” — rather than sending it. We would rather debug from a description than ask you for a file.
- A feature you need
- Especially the ones with a concrete job behind them: an export preset for a marketplace we have missed, a format we do not write, a step in your workflow that takes ten clicks here and two somewhere else.
- Licensing and commercial use
- The output is yours with no restriction from us, and the terms say so. If your organisation needs that in writing, or has questions about the model licences — the IS-Net weights are genuinely unresolved upstream — ask.
- Privacy
- Anything about how the tool handles your files, or a claim on the privacy page you think is wrong. That last one we treat as urgent: it is the strongest thing we say about the product.
Why there is no contact form
A form has to post somewhere. That means a server that accepts what you typed, stores it, and sits under our control — the exact thing every other page here says we do not have. We would rather keep the claim true and make you open your mail client than run a backend for the sake of a nicer-looking page.
It is also more honest about what happens to the message: an email is a message between you and us, with no third-party form service in the middle logging it. The privacy policy and the terms of use cover the rest.