Privacy Policy
This is short, because there isn't much to disclose. YourFileKit doesn't collect your data because it never has it. Here's exactly what that means.
Last updated: July 30, 2026
The short version
Your files never leave your browser
Every tool reads, processes, and writes files using your browser's own File, Canvas, and encoding APIs. Nothing is uploaded to a server, because no server is ever involved.
No accounts, no visitor tracking
There's no sign-up, no analytics, no cookies, and no third-party scripts loaded at runtime. We don't know you visited, let alone what you did here.
Nothing we could see, even if asked
Since your files are never transmitted anywhere, there's nothing on our end to view, store, hand over, or lose in a breach. We can't disclose data we never received.
A few things saved on your own device
Some tools save your in-progress work locally in your browser, purely so a refresh doesn't lose it. That data stays on your device. See "What's saved locally" below.
How this actually works
A typical online file tool works by uploading your document to a server, running a program on it there, and sending the result back. That upload is the whole privacy problem: once your file leaves your device, you're trusting someone else's server, their retention policy, and everyone with access to it.
YourFileKit skips that step entirely. Modern browsers can already decode a file, redraw it, re-encode it, and save it back to your disk, the same APIs a web page uses to display a PDF or an image. Every tool here is built on top of those APIs, running inside the tab you already have open. There's no upload because there's no server on the other end waiting for one.
What's saved locally, and why
A handful of tools save your in-progress work using your browser's own local storage (specifically localStorage for the invoice and receipt generators, and IndexedDB for the PDF editor), so that closing the tab or refreshing the page by accident doesn't erase what you typed or edited.
- That data is written only to your own device. It's never sent to us or anyone else, at any point.
- It stays there until you clear it yourself, either with the tool's own "Start over" button or by clearing site data in your browser's settings.
- We have no access to it. It doesn't pass through a server we operate, so there's nothing for us to read, back up, or lose.
What we don't do
A couple of specifics
Fonts are self-hosted.The typefaces this site uses are bundled at build time rather than fetched from Google's servers when you load a page, so opening YourFileKit doesn't quietly tell a font CDN you're here.
"Validation" tools check format, not a live database.Tools like the GSTIN validator check structure and format entirely in your browser. They don't look anything up against a government registry or any external service, and never send what you typed anywhere.
A couple of outbound links exist.Pages like About link to GitHub. If you click through, you're on their site under their privacy policy. This one only covers YourFileKit itself.
Children's privacy
YourFileKit doesn't knowingly collect personal information from anyone, including children, largely because it doesn't collect personal information from anyone, period. There's no account system or data-collection mechanism for this policy to apply differently to a child versus an adult.
Changes to this policy
If what YourFileKit collects or stores ever changes, this page will change with it and the date at the top will be updated. Given the whole premise here is "nothing leaves your browser," that's not a change we'd make quietly.
Questions
If anything here is unclear, or you want to ask about a specific tool's behavior, reach out at hello@yourfilekit.com.