Contact

Questions, corrections, or feedback about any tool on ProperScript? We'd like to hear it.

Email us at . A clear subject line helps us route faster — for example "Bug:", "Feedback:", or the name of the tool you're writing about.

Bugs and corrections

If a tool produces something wrong or unexpected, tell us which tool and what happened. Because every tool runs in your browser, we can't see your input — so the more detail you can share, the better.

Requesting a tool

Suggestions are welcome, and the ones that get built tend to share a shape: a single, well-defined job that can run entirely in the browser, that you'd otherwise have to trust a random site with. Formatters, converters, encoders, validators, and generators all fit that description.

Things that don't fit as well are tasks needing a server, an API key, or a large dependency — those either can't run client-side or would make the page heavy enough to defeat the point. If you're not sure which category your idea falls into, send it anyway.

Privacy questions

The most common question is whether we can see what you paste into a tool. We can't. Everything runs locally in your browser — your input is never transmitted to a server, and there are no accounts, so there's nothing stored against you in the first place.

That's also why we can't recover anything for you. If a result is lost when you close the tab, it's genuinely gone; nothing was kept. For questions about cookies, advertising, or analytics, the privacy policy covers what third parties may set and how to control it.

Business and licensing

For advertising enquiries, partnerships, or questions about using these tools inside an organisation, use the same address and say so in the subject line.

Response time

We're a small operation and aim to reply within a few business days. Bug reports with clear reproduction steps get looked at first, because they're the ones that affect everyone else using the same tool.

If you don't hear back within a week, it's worth resending — occasionally a message is caught by a spam filter, and that's more likely with an email containing code samples or links.