The short version
EncodeKit is a static website. There is no account system, no server-side conversion, no analytics script and no advertising tracker. When you paste text into a tool, it stays in the memory of that browser tab. Refreshing or closing the tab discards it, and nothing is written to a database because there is no database to write to.
This policy applies to every page on the site, including the Base64 tools, the URL tools, the about page and this policy. It was last reviewed on November 9, 2026.
What happens to text you paste
The converters are JavaScript functions running in the page. Your input is read from the textarea, transformed in memory, and written back to the result box. No request is made with that content: not to us, not to a third party, not to an API. You can verify this yourself by opening the browser’s network panel and watching it stay empty while you convert.
Because the conversion is local, the tools keep working after you disconnect from the internet. That property is a feature, not an accident: values such as API tokens, customer records and authentication headers are exactly what people decode, and they should not travel to a server just to be read.
What we do not collect
- No accounts, names, email addresses or passwords. The site has no sign-up and no login.
- No analytics service, data warehouse or advertising pixel. There is no third-party script on any page.
- No cookies are set by this site, and nothing is written to local storage or session storage by the tools.
- No tool input is logged, transmitted, stored or used to train anything.
- No file uploads. The tools accept text only, and no form on the site submits anywhere.
What the hosting provider may see
Like every website, EncodeKit is delivered by a hosting provider, which must process the request for a page in order to send it. That means the provider may record standard technical information such as the requesting IP address, the browser user agent, the requested URL and a timestamp in its own operational and security logs.
Those logs are about the page request, not about your input: the text you paste is never part of a request, so it cannot appear in a log. The provider operates under its own privacy terms, and its retention periods are set by it, not by us. We do not combine hosting logs with anything else or use them to build profiles.
Changes, children and contact
The tools are generic utilities suitable for general audiences; the site is not directed at children and collects no personal information from anyone. There is no newsletter and no remarketing list to join.
If this policy changes, the revised version will appear on this page with a new review date above, and the change will describe what is different. Questions about privacy can be sent to hello@encodekit.pages.dev; the same address handles corrections and bug reports, which are described on the about page.
Frequently asked questions
Does EncodeKit work offline?
Yes. Once a page has loaded, conversion needs no network access because the code runs in your browser. The offline behaviour is also the clearest proof that your input is not being sent anywhere, since a local conversion cannot depend on a server.
Do you use cookies or analytics?
No. There are no cookies, no analytics scripts, no advertising pixels and no third-party embeds on any page. The only information collected is whatever the hosting provider records to deliver the files, which is standard web server behaviour.
Is the text I paste stored anywhere?
No. It exists only in the memory of the browser tab while the page is open. Refreshing or closing the tab discards it, and nothing is saved to disk, local storage or a server. If you want to keep a result, copy it before closing the page.