What to include when you report a bug
A few details make a bug much easier to track down:
- The name of the tool or the page address.
- What you pasted or did, using a short sample that contains nothing private.
- What you expected to happen and what happened instead.
- Your browser and device, for example Chrome on Windows or Safari on iPhone.
Please don't send passwords, API keys or customer data, even as an example.
Suggesting a new tool
Tell me what you were trying to do, not only the name of a tool. A sentence like 'I need to turn a CSV into JSON and keep the headers' helps me build the right thing. Ideas that come up more than once usually move to the top of the list.
Privacy and data requests
To ask about your data, or to use a right described in the Privacy Policy, email me with the subject 'Privacy request'. ToolPlank has no accounts and doesn't store what you enter into the tools, so there is usually very little to delete, but I'll check and reply either way.
Business enquiries
For partnerships or other business questions, email me with a short description of what you have in mind.
Response time, and a warning
I usually reply within a few days. I will never ask you for a password, a payment or a one-time code. If someone asks for those in the name of ToolPlank, it isn't me.