Privacy

Nearly every tool under /tools runs entirely in your browser. What you type into a word counter, a JSON formatter, a JWT decoder or a password generator is never sent anywhere — there is no server request to send it to. You can confirm this by opening your browser’s network tab while you type, or by disconnecting from the internet and using the tool offline. Nothing you enter is stored, and nothing survives a page reload; passwords and tokens in particular exist only in the tab you generated them in.

The exceptions are named here rather than left for you to discover. These tools send what you give them to a server I run, because the work cannot be done in a browser:

• PDF to Images
• PDF to Text
• Video Downloader

For those, the line under the tool’s title says so before you use it, and that line is generated from how the tool actually works rather than typed by hand. The video downloader is the furthest from “runs in your browser”: for most sites it has to fetch the video onto my server, combine the separate video and audio streams, and hand you a link — so the file itself passes through my storage and is deleted six hours later. The link you paste is processed to find the media and is not kept.

Analytics are not loaded on tool pages at all.

Every page outside the tools section — the home page, the blog, and this page — loads one third-party analytics script, from app.usecortana.ai, which records page views and interaction events so I know which articles get read. It sets its own identifiers and receives your IP address and user agent, as any request to any server does.

The video downloader page contacts two others. Cloudflare Turnstile supplies the “are you human” check, which is what keeps the tool from being drained by scripts, and it receives your IP address and browser details. When a download can be served directly, your browser fetches the file from the originating platform’s own network — TikTok’s, X’s, and so on — which means that platform sees the request, though the referrer is stripped so it does not learn that you came from here.

Yes, including this one. Carving out an exception for the privacy page would make the sentence above harder to state honestly, and a policy you cannot verify by looking is not worth much.

If you would rather it did not load, any content blocker will stop it, and the site works normally without it.

The site is hosted on Vercel, which keeps standard server logs including IP addresses for a limited period as part of operating the service. I do not add my own logging beyond that.

Blog content is stored in a database I control. It holds articles, not readers — there are no user records because there are no users.

The site sets no cookies for ordinary browsing. There is one cookie used by the private admin area, which only exists after logging in and only applies to me. The analytics script described above may set storage of its own on the pages where it loads.

The video downloader sets one cookie, and only once you use it. It records that the “are you human” check has been passed, so a single download does not ask you to pass it again for every step. It holds no identifier for you — only a one-way hash of your address and two timestamps — cannot be read by any script, is not sent to any other site, and expires within fifteen minutes of you stopping.

I do not sell data, share it with advertisers, or build profiles. There is no ad network on this site.

These tools are provided free and as-is, with no guarantee of uptime, accuracy or fitness for any particular purpose. Check anything important — a loan figure, a tax calculation, a contrast ratio in an accessibility audit — against a second source before relying on it.

Questions, corrections, or a request to remove something: email kanchanakavitha6@gmail.com.