Privacy

nanofile.app is made and published by Digital Sandbox B.V., registered with the Dutch Chamber of Commerce under number 42124304. Digital Sandbox B.V. is the controller in the sense of the General Data Protection Regulation (GDPR).

For privacy questions, write to privacy@digitalsandbox.app.

When you drop a file on this site, open one, or paste markdown, the file is read by your own browser and rendered there. It is not sent to us and it is not sent to anyone else. This site has no upload endpoint and no server-side rendering of your content.

You do not have to take our word for it: open the network tab in your browser's developer tools, load a document, and look at the requests. None of them carries your file.

Because nothing is transmitted, there is nothing for us to store, read, share or lose.

So the page is useful when you come back, the viewer keeps three things in your browser's local storage: the last document you had open, the file name shown in the toolbar, and your view and reading-theme preferences.

That data stays on your device. It is not synced, not readable by us, and the Clear button in the viewer removes the document again. Clearing your browser's site data removes everything.

NanoFile is also an app for iPhone, iPad and Mac. It works the same way and for the same reason: the document is rendered on your device, by the same renderer this website uses, and nothing about it is sent anywhere. The page that renders it is locked down so that it cannot make a network request at all, which means a document cannot reach out even if something in it tried to.

There is no account, no sign-in and no sync. No analytics, no crash reporter and no advertising or tracking framework of any kind is built into the app. Apple's privacy questionnaire for the App Store listing answers "Data Not Collected" in every category, and the app's own privacy manifest says the same: no tracking, no tracking domains, no collected data types.

Your reading preferences, the list of recently opened documents, the folder you have open, and the folders you have saved as workspaces. All of it lives in the app's own storage on your device and none of it is transmitted.

One part of that is worth stating plainly rather than glossing over. The recent list and the folders are stored as what Apple calls security-scoped bookmarks, and a bookmark records where a file is. So the app does keep a record of which files and folders you have opened. It is on your device, we never see it, and it holds nothing about what those files contain, but it is a record of file locations and you should know it exists. It is what allows the app to reopen your work without asking for permission again.

Once, and only when you ask. If you open a public GitHub repository, the app asks GitHub for the file list and then for the files. That request is unauthenticated, it names a repository that is already public, and it carries nothing about you: no account, no token, no identifier. There is no other network code in the app.

The Mac version declares a network permission that deserves an explanation, because someone who inspects the app will find it. macOS will not let a sandboxed app start the component that renders your document without that permission, even when everything being rendered is local. It is there for that reason and for no other, and the rendering page itself is configured so that it cannot make a request.

The apps sell nothing. There is no purchase, no subscription, no paid tier and no account, so there is no payment data for this notice to describe: no card number, no billing address, no name, no receipt. The apps do not contact the App Store while they run.

This section exists because its absence would be the more suspicious thing. An app that reads your files and asks for no money invites the question of what it takes instead, and the answer is in the two sections above: nothing leaves your device.

We use Vercel Web Analytics to see which pages are visited and roughly where visitors come from. It is cookieless, it does not build a cross-site profile of you, and it counts page views rather than people.

There is no Google Analytics, no advertising pixel and no third-party tracker on this site.

This site sets no cookies at all. What the viewer remembers, your last document and how you like to read it, sits in your browser's own storage rather than in a cookie, and the analytics work without one. That is also why you never see a cookie banner here.

The site is hosted by Vercel Inc., which processes data on our behalf. Like any web server, Vercel's infrastructure logs technical request data, including IP addresses, for delivery and abuse prevention. These logs are short-lived and we do not use them to identify visitors.

Everything the page loads comes from nanofile.app itself. Fonts are bundled at build time rather than fetched from Google, and the syntax highlighter and the diagram library are served from this domain, so browsing here does not announce you to third parties.

The GDPR gives you the right to access, correct and erase personal data, and to object to its processing. Since we hold no personal data about visitors to this site, there is usually nothing to hand over or delete, but you are welcome to ask.

Write to privacy@digitalsandbox.app. You also have the right to complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

If this policy changes, the date at the top of this page changes with it. Material changes will be described here rather than quietly rewritten.