Privacy Policy
Last updated:
This policy covers noteloom.qusere.in — the marketing site, documentation, Playground, and My Notes app. It does not cover the noteloom npm package itself, which runs entirely inside whatever application installs it and has no data practices of its own to disclose.
The short version
There is no account, no sign-up, and no server-side database behind this site. Anything you write in the My Notes app or the Suggestions page is saved only in your own browser's local storage — it never leaves your device. The one exception is the floating feedback prompt: if you answer it, your emoji rating and which page you were on (never your typed comment) is sent to Google Analytics, anonymously, to help us understand how noteloom is landing. See Suggestions & feedback below for the details.
Your notes and Playground content
The My Notes and Playground pages run entirely in your browser. Whatever you type is held in React state and, for My Notes, persisted to window.localStorage on your device so it survives a reload. None of that content — titles, text, or the document JSON — is transmitted to any server we operate. Clearing your browser's site data, using a different browser or device, or browsing in a private/incognito window will make it unavailable, since there is no backup copy anywhere else.
Analytics
This site uses Google Analytics to understand aggregate traffic — which pages get visited, roughly how, and from where. Google Analytics may set cookies and collect information such as your browser type, device type, approximate location (derived from IP address), and pages viewed. We do not use this data to identify you personally, and we don't combine it with anything else.
Google acts as an independent data processor for this information under its own terms — see Google's Privacy Policy for how it handles this data. You can opt out of Google Analytics tracking across all websites using the Google Analytics Opt-out Browser Add-on, or block it more generally with your browser's tracking-protection settings, an ad blocker, or by disabling JavaScript for this site.
Suggestions & feedback
The Suggestions page works the same way as your notes: whatever you type — a feature idea, a description — is saved only to localStorage on your device, and we never receive it. The one exception is entirely your own choice: clicking "Open as GitHub issue" on a suggestion opens a pre-filled new-issue form on GitHub in a new tab. That action sends the suggestion's text to GitHub, governed by GitHub's own privacy statement — nothing is sent unless you click that link yourself.
The small floating feedback prompt (shown once on the Playground, My Notes, and individual note-editing pages) is different: it's the one place on this site that sends something automatically. When you pick an emoji or dismiss the prompt, we record that (so it doesn't ask again) in a local flag, exactly like everything else here. But if you pick an emoji, we also send an anonymous Google Analytics event containing just that emoji rating and which page you were on — nothing that identifies you, and never the optional comment text, which stays local-only alongside the rating in your own browser. This is genuinely just for us to see, in aggregate, whether people are finding noteloom useful; there's no way for us to trace an individual event back to a specific visitor.
Cookies & local storage
Aside from whatever Google Analytics sets, this site does not itself set tracking cookies. It does use localStorage for several purposes with nothing to do with tracking: saving your notes and suggestions (see above), remembering whether the feedback prompt has been shown, and caching pages/assets via a service worker so the site keeps working offline. All of it stays entirely on your device.
Third parties
We don't sell, rent, or share any data with third parties for advertising or marketing purposes — we don't run ads on this site at all. The only third-party service in use is Google Analytics, described above.
Children's privacy
This site is not directed at children and we do not knowingly collect personal information from anyone under the age of 13 (or the equivalent minimum age in your jurisdiction).
Changes to this policy
If this policy changes, we'll update the "Last updated" date at the top of this page. Since there are no accounts, we have no way to notify individual users directly — check back here if you want to stay current.
Contact
Questions about this policy can be raised as an issue on GitHub.