Skip to content
Collabs Tool

Support

Contact

There is no ticketing system and no chat widget. Email reaches a person, and most messages get a reply within two working days.

Last updated 2 September 2026

Where to write

Three addresses, all read by the same small team. Use whichever fits; if you pick the wrong one it will still be answered.

hello@collabstool.comGeneral. Everything that is not covered by a more specific address below.support@collabstool.comBugs and tool requests. Broken tools, missing features and suggestions for what to build next.legal@collabstool.comPrivacy and legal. Data questions, removal requests, terms and policy matters.

What to include

The four things below turn a message we have to ask follow-up questions about into one we can act on immediately.

  • Something is broken. Tell us the tool name, your browser and version, what you did and what happened. A screenshot of any error message helps. Please do not attach the file you were processing unless it contains nothing sensitive.
  • A tool you want. We keep a ranked list of requests. Say what the task is and how often you need it — frequency is the main factor in what gets built next.
  • Privacy or a data question. If you believe a tool transmitted something it should not have, tell us immediately with as much detail as you can. That would be a serious bug and it gets treated as one.
  • Anything else. Partnerships, corrections to our documentation, accessibility problems, licensing questions — all welcome in the same inbox.

Before you write about a bug

Most failures have one of three causes, and checking them takes under a minute:

  1. The file is too large. Each tool states its limit next to the upload area. Because processing happens in your browser, the real ceiling is your device’s available memory — a file that works on a desktop may fail on a phone.
  2. The format is not what the extension says. A file renamed from .txt to .png is still a text file. Tools validate the actual bytes and will refuse it.
  3. The browser is blocking a capability. Strict privacy modes, some corporate policies and a few extensions disable clipboard access, canvas export or local storage. Try a private window in a different browser to isolate it.

If none of those explain it, tell us — the tool name, the browser and version, what you did and what happened. Error reports are the only way we see failures that do not surface in our own testing, and they are the reason fixes ship quickly.

What we do not do

There is no live chat, no ticketing queue and no automated reply. If you do not hear back within two working days, the message was probably lost — send it again. And please never attach a file you were processing unless it contains nothing sensitive; a description of the input is enough for us to reproduce almost anything.