Why is there no contact form?

A form would need a backend, and a backend would mean storing whatever you typed. Email is the honest option: it works, it leaves a record you control, and it does not require TLKS to run a database.

Do you offer support for the tools?

Use the email address below and describe what you expected versus what happened. Include the browser, the input that failed and, if a page crashed, the text you pasted. Reports about incorrect output are treated as bugs.

Can I request a new tool?

Yes, and specific requests are more likely to be built. Describe the recurring task, the input you have and the output you need, rather than naming a competitor to copy.

Contact

Contact TLKS

One inbox, read by the people who build the tools. No form, no ticket queue and no autoresponder.

Last updated 2026-09-22

Email

Write to hello@tlks.io. If you are reporting a bug, a short message that can be reproduced beats a long one that cannot.

What to include in a bug report

The page or tool you were using, ideally as a URL.
The exact input, trimmed to the smallest version that still fails.
What you expected to happen and what happened instead, including the message you saw.
Your browser and operating system, since clipboard and crypto behaviour differ between them.
Whether the failure is reproducible after a reload, or only after a specific sequence of actions.

Security reports

If you believe you have found a security issue, state that clearly in the subject line and describe the impact rather than only the symptom. Please do not attach payloads that would affect anyone else, and do not test against infrastructure you do not own. Reports that lead to a fix are credited on request.

One thing worth saying plainly: because the client-side tools never send your input anywhere, a report about tool output leaking data is usually a report about your own environment, such as an extension or a shared machine. If an AI tool is involved, remember that connecting a provider is an explicit action that you can disconnect at any time from the panel on the tool page.

What we cannot help with

Debugging your application, your container or your cluster. The error explainer is the fastest starting point.
Recovering data that was never sent to us, because there is nothing stored to recover.
Third-party services: quotas, outages and billing for a provider you connected are outside our control.

Response times

This is a small project, and email is answered in batches. Bug reports with a reproduction typically get a reply within a few days. Feature requests are read, but a reply is not guaranteed; the ones that are built usually arrive with a clear description of the underlying chore.