NoteNest Privacy Policy

Effective date: 9 November 2026

Publisher: Humble Meteor Studio

NoteNest is a Chrome extension that keeps personal notes and checklists with the pages and websites where you need them. This policy describes the extension's handling of information.

Information NoteNest handles

NoteNest reads tab addresses and titles to identify the current page, match saved notes, follow navigation and update the extension icon's note count. The background process can check addresses of open tabs when refreshing those counts. It does not read webpage content, use Chrome's browsing-history API or keep a separate log of pages you visit.

When you create or import a note, NoteNest stores its text, checklist items and completion states, source address and title, Page or Website scope, internal identifiers, creation/update times and revision numbers. Page matching retains URL query parameters and fragments; these may contain private information. Website matching uses the exact protocol, hostname and port.

NoteNest also stores recovery drafts, notes moved to Trash, the date you explicitly confirm a backup was saved, a data-format version and whether you dismissed the introductory message. Recovery copies are used to help preserve unfinished edits and conflicting versions.

Purpose and local storage

This information is used to provide contextual notes, checklists, search, save recovery, Trash restoration and manual backup/import. NoteNest uses Chrome's local extension storage in the browser profile. It does not use Chrome Sync for these records.

There is no NoteNest account, backend, cloud synchronisation, analytics or advertising service. The extension does not automatically transmit your note content, tab addresses or titles to Humble Meteor Studio or other recipients. We do not receive a copy of your local notes through the extension. We do not sell note data or use it for advertising, profiling, creditworthiness or lending decisions.

Permissions

NoteNest does not request website host access, read page contents through content scripts or execute remotely hosted code.

Export is a manual action. A JSON backup contains active saved notes, including their source addresses and titles. It does not include recovery drafts, Trash or the backup-confirmation preference. The export file is plain text, without password protection or encryption added by NoteNest. Keep backups somewhere appropriate for their contents.

The displayed last-confirmed-backup date records your own confirmation that a file was saved. It is not an automatic verification of a file's existence or integrity. Import reads the file you choose and previews additions, duplicates and conflict copies before confirmation.

Opening a note's source address or a help, policy or support link navigates the browser to that website. Those ordinary website requests are subject to the destination's practices; NoteNest does not append your notes to those links. If you voluntarily send notes, a backup or other information in a support message, the information you submit is shared through that support service. Avoid sending private note content unless it is necessary for your request. The studio website's contact form and hosting are separate from the extension's local processing.

Retention, deletion and control

Saved notes remain in the browser profile until you change or remove them, remove the extension or clear its data. Moving a note to Trash retains a recoverable copy; it is not permanent deletion. Trash is not automatically emptied. You can restore a note, permanently delete a selected Trash note or empty Trash after confirmation.

Permanent deletion removes the selected saved Trash records from NoteNest's local storage. It does not erase independently retained recovery drafts in another open panel, backups you already exported, browser/profile backups or information you separately sent through support. Resolve or discard independent edits and manage those copies separately when you want to remove all copies of particular content.

Successful saves normally clear the recovery copies associated with those saves. Failed or conflicting edits may remain available as drafts until resolved. Uninstalling NoteNest removes its extension-local data; loss or removal of the browser profile can also remove it. NoteNest cannot restore local data from a studio server because it does not hold a server copy.

Security and limitations

Local data is handled within Chrome's extension storage and the browser profile. NoteNest does not add its own encryption layer to stored notes or JSON exports. Access to your device, profile or exported files may allow access to their contents. Do not use NoteNest as a password vault or assume that local storage is an external backup. Save failures or an abrupt shutdown before a write is confirmed may affect the latest input.

Limited Use

NoteNest's use of information received through Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. The information is used for the disclosed contextual-note features described in this policy, not for unrelated purposes.

Changes and questions

We will update this policy when NoteNest's information-handling practices change and show the effective date above. A change to local processing, permissions or recipients must also be reflected in the extension and store disclosures.

For support or privacy questions, use NoteNest contact. For a privacy request, identify NoteNest and state that your question concerns privacy. Since we cannot access your extension-local records, local data removal is performed in your browser rather than by requesting deletion of a studio-held note account.