Is the text I paste into a tool sent to a server?

No. The formatters, converters, encoders, generators, parsers, hash tools and the offline AI engine all run inside your browser. Your input is never transmitted to TLKS. The single exception is described in the AI provider section: if you connect your own provider, the input you submit is sent from your browser to that provider.

What is stored in my browser?

Two things at most: your theme preference, and the AI provider settings you entered yourself. Both live in local storage under keys prefixed with "tlks-" and both can be removed by clearing site data for this domain.

Does TLKS set cookies?

No. No cookies are set, and no cookie banner is shown because there is nothing to consent to. The theme and provider settings use local storage, which is not sent to the server with each request.

Can TLKS read the files I encode?

No. When you drop a file into a tool that accepts files, the browser reads it locally using the File API and passes the bytes to the tool. The file is not uploaded.

What happens if I connect an AI provider?

Your API key and endpoint are saved in this browser only. When you press a generate or explain button, your browser sends the prompt directly to the endpoint you configured. TLKS is not a party to that request and cannot see it.

Privacy

Privacy Policy

TLKS is built so that the privacy answer is short: your tool input stays in your browser, and the site stores almost nothing.

Last updated 2026-09-22

The short version

Tool input is processed in your browser and is never uploaded to TLKS.
No cookies are set, and no third-party analytics or advertising scripts are loaded.
Your theme choice and, optionally, your AI provider settings are kept in local storage on your device.
If you connect an AI provider, requests go from your browser directly to that provider under their terms.
If you email us, we keep the email so we can reply.

What is processed in your browser

Everything that computes a result runs on your device. That includes formatting and validating JSON, YAML and XML; encoding and decoding Base64 and URLs; generating UUIDs, hashes and timestamps; parsing cron expressions and CIDR ranges; generating Nginx, Dockerfile and Kubernetes configuration; converting JSON into Go structs; and the offline engine behind the AI developer tools. None of these operations makes a network request with your input.

Files are handled the same way. If a tool accepts a file, the browser reads it locally with the File API, and the bytes are handed to the tool in memory. Nothing is uploaded, and nothing is written to disk by the site.

What is stored on your device

TLKS uses local storage, not cookies, for two small pieces of state:

tlks-theme – whether you prefer the light or dark palette, so the correct one is applied before the first paint on your next visit.
tlks-ai-provider – only if you connect a model provider: the base URL, model name, your API key and the enabled flag. This is what lets the AI tools work on your next visit without re-entering the key.

Both entries are readable by anything running on this domain, including browser extensions with access to the page, so treat the stored API key as you would any credential on a shared machine. The provider panel includes a disconnect action that deletes the stored key immediately.

Optional AI providers

The AI developer tools work without any provider. If you choose to connect one, the request is a plain fetch from your browser to the chat completions endpoint you configured, authenticated with the key you entered. That means:

The prompt and any input it contains are transmitted to the provider you selected, subject to their privacy policy.
TLKS does not proxy the request, does not see the response, and does not log the exchange.
Review what you send. A diff, a stack trace or a configuration file can contain internal host names, tokens or personal data.
Disconnecting removes the stored credentials from this browser; it does not revoke the key at the provider, which you should do from their dashboard.

Analytics and third parties

TLKS does not load an analytics product, an advertising network or a social widget. The site defines a small set of event names and pushes them to an in-memory array so a first-party tag could be attached later; with no tag installed, those events stay in the page and disappear when you close it. If an analytics tag is ever added, this policy will be updated first and the events will never include the content of your tool input.

Two third parties are involved in serving the pages. The hosting provider that delivers the static files may record standard request metadata such as IP address, user agent and requested path in access logs for security and operations. The site also requests the Inter and JetBrains Mono web fonts from Google Fonts, which means your browser contacts Google's font servers and reveals your IP address and user agent to them.

Data we hold

TLKS has no user accounts and no database of tool usage, so there is no profile to delete. The only personal data we hold is the content of emails sent to hello@tlks.io, kept so that we can answer and, where a bug report leads to a fix, follow up. Ask us to delete an email thread and we will.

Children

The site is a developer tool aimed at professional and hobbyist programmers. It is not directed at children and does not knowingly collect information from them.

Your choices

Clear site data for this domain to remove the theme and any stored provider configuration.
Use the AI tools without a provider, in which case no prompt ever leaves your browser.
Block third-party font requests with your browser or an extension; the tools will still work.
Email us to ask what we hold about you, or to have your email thread removed.

Changes to this policy

If the way TLKS handles data changes, this page changes with it and the date at the top is updated. Material changes will be described in plain language rather than silently edited.