Effective October 22, 2026.
Everything you open, write or make in nopa — files, notes, boards, passwords, recordings, results — stays in your browser on your device. There is no nopa server that receives it, stores it or could be breached for it. We count how often a tool is opened and whether it worked; we never see what you put in.
Open your browser tools, switch to the Network tab, then open any tool on this site and use it. What you put in is never sent: there is no upload. You will see two kinds of rows: our own code arriving from this address, and visit statistics for Yandex Metrica, PostHog and nopa’s own counter. The statistics say which page was opened and which tool was used, never what is in it.
Your work never left this device.
What the Network tab shows while you work on this page
Most “free” tools upload your file, process it on their machines and send a result back. That upload is where the risk lives: a copy of your document now sits somewhere you cannot see, under rules you did not write. nopa is built the other way round. The PDF is merged, the background removed, the audio transcribed by your own browser, on your own hardware. The file never leaves the tab. This is not a policy we chose — it is how the product works, and we could not change it quietly even if we wanted to.
Notes, boards, calendar events, the Files library, desktop icons, saved results and settings are stored by your browser (IndexedDB, localStorage and similar). Opening, previewing and playing files — images, PDFs, Office documents, audio, video — happens locally; playback uses local blob URLs, and nothing is uploaded. Public pages remember your language. AI tools cache their model files in the browser after the first download so the second run is instant.
Because it is your browser’s storage, it follows your browser’s rules: clearing site data or uninstalling the app removes it, and it does not travel to another device unless you export it yourself.
We do not operate any server that receives your files, notes, passwords, audio, images, transcripts, generated outputs, tool inputs or even filenames. We do not ask for an account, an email address or a card. We cannot sell your data, hand it over or lose it in a breach — for the plainest reason there is: we do not have it.
We use two analytics services, Yandex Metrika and PostHog, to learn which pages are visited, which tools are opened and whether they finish successfully. That is how we know what to fix and what to build next.
What they receive is the event — “merge PDF opened”, “download clicked” — never the content. Nothing you type, open or generate is sent in an analytics event, and page views are counted without the query part of the address. A search on the site is counted the same way: that it happened and whether it found anything, never the words you typed, which the results page also removes from its address. Nothing records your screen: session recording is off in both services. Clicks are counted as positions on the page (Yandex’s click map) and as “a click happened” (PostHog), without the text you clicked. A click on a link that leads to another site is counted with that link’s address on our public pages; in the full app at /main, where links come from your own notes and documents, it is not. Each service keeps a random visitor ID in a cookie, so a return visit is not counted as a new visitor; it is not tied to a name, an email or an account. The same events also reach nopa’s own counter, N1 Hub (hub.n1.team), which keeps only daily totals: no cookie, no visitor ID, no IP address kept. So that we can tell whether people come back without knowing who they are, it gets one more signal: once a day, “this device got a result today”, and once a week, the week of your first result and on how many days of the previous week you had one. That week and those dates are kept only in your browser; saying no to analytics or resetting the workspace deletes them, and a later yes counts you as new. It follows the same answer you give the two services. In the EU, the EEA, the UK and Switzerland — judged by your device’s time zone, since nopa has no server to ask — neither service loads, and no cookie is set, until you choose “Allow” in the banner. Elsewhere they load by default. Anywhere, “Analytics settings” at the bottom of every page changes your answer, and nopa works exactly the same without them.
If something breaks, we would love to know — but only with your permission. Crash reporting (via Hawk) is off by default. Turn it on in Settings → Data and nopa sends a sanitized report: the error message, where in our code it happened, the page address without its query part, which browser and system you use, and the window size. Never your files, notes, inputs, history or identity. Turn it off again whenever you like.
Background removal, transcription and similar tools use machine-learning models downloaded once from a public hub such as Hugging Face and cached in your browser. The model comes to your device; your photo or recording does not go to the model. Processing happens locally, which is the only way it could be private. Models and libraries carry their own licenses, listed on the Licenses page.
A few features fetch resources directly from third parties — from your device to them, never through us:
• Google Fonts, for the typefaces of the full app at /main (public pages use your device’s own fonts) • Hugging Face and similar hubs, for AI model files • jsDelivr, for emoji artwork when you preview or download emoji images • icon services (Google gstatic, DuckDuckGo) for desktop bookmark tiles — they see your IP and the bookmarked site’s host • jsDelivr, when the Retro app loads a game core the first time • analytics providers as described above, and Hawk only if you turned crash reports on
nopa does not proxy your content through any server of ours, because there is no such server.
Export or copy any result at any time. Clear site data in your browser and it is gone — for good, since we hold no copy. Uninstall the app or simply stop using the site. Block analytics if you wish. Crash reports stay off unless you switch them on, and switch off the moment you say.
nopa is made by a small team led by its founder, Kirill Dobrinov — not a registered company. Write to hello@nopa.space about this policy or anything else; a person reads every message and answers.
nopa is a general-purpose productivity site. We do not knowingly collect personal information from anyone, children included — there is no place in nopa where personal information is collected.
When this policy changes, the effective date at the top changes with it. Using nopa after an update means you accept the revised policy — and the promise at the top of this page is the one part we do not intend to change.
See also: Terms of Service and Licenses on this site.
