The short version
EncodeKit is a static website: 7 pages, 5 of which run a converter in the browser. There are 0 accounts, 0 cookies, 0 analytics scripts, 0 advertising pixels and 0 third-party requests, so the pasted text has 0 server-side conversions and 0 bytes of it leave the tab. Refreshing or closing the tab discards it, because there is no database behind the site to write to.
This policy applies to all 7 pages — 4 specialist tools plus the universal converter, 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. Input is read from the textarea, transformed in memory, and written back to the result box: 0 requests are made with that content, to us, to a third party or to an API. The browser’s network panel shows 0 new requests while a conversion runs, and the tools keep working after the network is disconnected.
Local conversion is a feature, not an accident. API tokens, customer records and authentication headers are 3 examples of values people decode, and they should not travel to a server just to be read; with 0 uploads and 0 storage keys, there is no copy to leak from this site.
What we do not collect
- 0 accounts, 0 names, 0 email addresses and 0 passwords: the site has no sign-up and no login.
- 0 analytics services, 0 data warehouses and 0 advertising pixels: 0 third-party scripts load on any of the 7 pages.
- 0 cookies set by this site, 0 local-storage entries and 0 session-storage entries written by the tools.
- 0 tool inputs logged, transmitted, stored or used to train anything.
- 0 file uploads and 0 form submissions: the tools accept text only, and no form posts anywhere.
What the hosting provider may see
Like every website, EncodeKit is delivered by a hosting provider, which must process 1 request per page in order to send it. That means the provider may record 4 standard fields — requesting IP address, browser user agent, requested URL and 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, and this site adds 0 tracking parameters of its own.
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 [email protected]; 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.