nopa

Privacy Policy

Effective July 18, 2026. nopa is built by a small volunteer team. We are not a registered company or legal entity.

Summary

nopa (nopa.space) is a free desktop in your browser. Your notes, files, and app outputs generally stay on your device. We do not run a server that stores your content. We do not sell user data. We do not charge for the service. We may use limited analytics — such as Google Analytics and/or Yandex Metrika when enabled — to understand how the product is used and to improve it. We do not use analytics to collect the content of your notes, files, passwords, audio, images, transcripts, generated outputs, or tool inputs.

Who we are

nopa is maintained by the nopa team — an informal group of contributors. There is no registered legal entity behind nopa.space. Questions about this policy can be sent through the contact options listed on the site.

Data on your device

nopa is a desktop in your browser. App data is stored in your browser using IndexedDB, localStorage, and similar storage — including notes, boards, calendar events, the Files library, desktop icons, saved results, settings, and other app outputs. Files stay local: import, PWA “Open with” / share target, Smart Box, and Preview (images, PDFs, Office, audio, and video) run in your browser. Playback uses local blob URLs — media is not uploaded to nopa servers. Public pages may save your language preference locally. AI features may download model files once and cache them in your browser for faster reuse. You can clear site data at any time in your browser settings. Clearing browser data or uninstalling the PWA may delete local data permanently.

What we do not collect

We do not operate servers that receive your files, notes, passwords, audio, images, transcripts, generated outputs, tool inputs, or filenames. We do not require accounts, email addresses, or payment details — the service is free and has no paid plans. We do not upload your desktop content to nopa infrastructure because there is none for user data.

Analytics

When enabled by the site operator, nopa may use limited analytics such as Google Analytics, Yandex Metrika, and/or PostHog on public and product surfaces. Analytics helps us understand page views, product funnel events, navigation, errors, performance, and UX issues. Some analytics tools may provide aggregated or anonymized behavior diagnostics — such as click maps, session diagnostics, or automatic interaction tracking (PostHog "autocapture", which records clicks and page structure, not typed text) — to help us improve the product. We do not use analytics to collect the content of notes, files, passwords, audio, images, transcripts, generated outputs, or tool inputs. We avoid sending query parameters or user-entered content in analytics events. You can block analytics with browser extensions, privacy settings, or similar tools.

Optional crash reports

Crash reporting is off by default. If a build includes crash reporting (via Hawk, hawk.so) and you turn it on in Settings → Data, nopa may send a sanitized error report (error message, stack shape, and app version) to help us fix bugs. Reports do not include your files, photos, notes, passwords, audio, tool inputs, browsing history, or account identity. You can turn crash reports off again at any time.

Advertising (future)

nopa does not display third-party advertising today. If we add display advertising in the future (for example through Google or Yandex ad networks), it would appear only on public marketing pages — home, tool catalog, and tool landings — not inside the desktop where your files and notes live, and never between you and downloading or copying your result. Before ads go live, we would update this policy, document ad provider domains, and use consent where required by law (for example in the EU). Ad scripts would not receive your tool inputs, file contents, or desktop data.

AI models (on-device)

Some tools optionally download machine-learning models to your browser from public hubs (for example Hugging Face). Processing runs on your device. Model files are cached locally after the first download. Models and libraries have their own licenses; some model licenses include restrictions. Details — including Background Remover and Local Transcriber models — are listed on the Licenses page.

Third-party requests from your browser

Your browser may make requests directly to third parties when you use nopa — for example: • Google Fonts (typography) • public model hubs such as Hugging Face (AI model files) • emoji artwork CDNs — jsDelivr, GitHub raw content, and openmoji.org — when you preview or download an emoji image in the Emoji app • jsDelivr, when the Retro app fetches the libretro Genesis Plus GX core the first time you open a Sega game • analytics providers such as Google Analytics, Yandex Metrika, or PostHog, if enabled • Hawk (hawk.so), only if you turn on crash reports in Settings → Data These requests go directly from your device to the third party; nopa does not proxy your content through our servers.

Your choices

You control your data: • Export or copy results from any tool • Clear site data in browser settings • Uninstall the PWA or stop using the site • Block analytics as described above • Keep optional crash reports off, or turn them on/off in Settings → Data

Children

nopa is a general-purpose productivity site. We do not knowingly collect personal information from anyone, including children, because we do not collect user content on our servers.

Changes

We may update this Privacy Policy from time to time. The effective date at the top will change when we do. Continued use of nopa after an update means you accept the revised policy.