1. Overview
QuietNote is a Chrome extension for creating, editing, organizing, searching, archiving, restoring, and backing up text notes from the browser toolbar. The extension includes tags, pinned notes, note history, a recent activity view, archive and trash states, import and export tools, appearance preferences, and local storage diagnostics.
QuietNote is designed to work without an account. Note content and application state are stored inside the browser profile using storage belonging to the extension itself. The current version does not require a developer-operated cloud service to save notes, search notes, maintain revisions, or restore the interface between sessions.
2. Scope of this Privacy Policy
This policy applies to QuietNote version 1.0.0 and the functionality packaged with that extension, including its popup interface, note editor, local save, tags, search, archive, trash, revisions, activity records, settings, diagnostics, and user-initiated JSON backup tools.
This policy does not govern Google Chrome, the Chrome Web Store, your Google account, your operating system, your email provider, device backup software, browser-level spellchecking services, security software, or unrelated websites and applications. Those products may process information independently according to their own privacy terms and settings.
If a future QuietNote release materially changes its data handling—for example by adding cloud synchronization, an online account, analytics, advertising, remote AI, website access, collaboration, or new Chrome permissions—this policy should be revised so that it reflects the new behavior.
3. Privacy design principles
QuietNote follows a local-first and data-minimization approach. The extension needs to remember note content and enough local state to provide its features, but the current version does not need to transmit that information to the developer.
- Local-first: notes and application state are kept in extension-origin browser storage.
- No account: QuietNote does not ask users to register, sign in, or create an online profile.
- No website access: the current manifest does not request permission to inspect or modify web pages.
- No analytics: there is no analytics SDK or developer telemetry endpoint in the current package.
- No advertising: the extension does not include an ad network, retargeting technology, or behavioral advertising component.
- No developer backend: core note-taking functionality does not depend on a QuietNote server.
- User-controlled backups: export files are created only when the user chooses to export, and import files are read only after the user selects a file.
- Packaged code: the HTML, CSS, JavaScript modules, and icons required by QuietNote are included in the extension package.
4. Information collected by the developer
During normal operation of version 1.0.0, QuietNote does not collect note content, application usage records, or personal information for the developer. The developer does not receive a copy of the local QuietNote database merely because a user opens the extension, writes a note, performs a search, changes a tag, archives a note, views history, or exports a backup.
QuietNote does not intentionally collect names, email addresses, postal addresses, phone numbers, account passwords, authentication tokens, precise location, financial information, health information, biometric information, browsing history, search-engine history, website content, private communications, or Chrome account identifiers.
The extension also does not automatically report which notes were created, what users typed, which notes were searched, how many notes exist, how often the extension was opened, or which settings were selected.
If a user independently contacts the developer by email, information contained in that email is separate from QuietNote's automated extension behavior. Direct correspondence is discussed in the Contact section below.
5. Data-category disclosure
| Category | Sent to developer? | QuietNote behavior |
|---|---|---|
| Note titles and bodies | No | Stored locally in the extension's browser storage. |
| Tags and organization | No | Tags, pin state, archive state, and trash state are kept locally. |
| Revision history | No | Recent snapshots of individual notes are stored locally to support note history. |
| Recent activity | No | QuietNote keeps a limited local log of note actions for the Activity screen. |
| Application preferences | No | Theme, sorting, spellcheck preference, display options, and related settings are local. |
| Local usage / operational state | No | Local counters and internal state are used to coordinate interface behavior and diagnostics; they are not transmitted. |
| Browsing history | No | QuietNote does not request Chrome history access. |
| Website content | No | QuietNote does not inject scripts into pages or read active-page content. |
| Location | No | No geolocation permission or location API is required. |
| Authentication information | No | No QuietNote account or login credentials are used. |
| Analytics / advertising identifiers | No | No analytics SDK, ad identifier, or cross-site tracking system is included. |
6. Notes, tags, and organization data
QuietNote stores the information needed to represent each note. This may include:
- the note title;
- the note body text;
- tags assigned by the user;
- whether the note is pinned;
- whether the note is archived;
- whether the note is in Trash;
- the note's locally generated identifier;
- creation and modification timestamps;
- recent revision snapshots used by note history.
Because QuietNote is a general-purpose note editor, users may choose to type information that is personal, confidential, or sensitive. QuietNote does not need to understand the meaning of that text in order to save and display it. The current version does not send note text to a QuietNote server for classification, AI processing, advertising, analytics, or profiling.
Users remain responsible for deciding what information they place in their notes. As with other locally stored data, anyone who gains access to the same unlocked browser profile or device may potentially be able to access local extension data depending on the security of the device and browser profile.
7. Revision history and recent activity
Note revisions
QuietNote keeps recent snapshots of notes so that the History panel can show previous versions. A revision can contain the note title, body, tags, timestamp, word count, character count, and a locally computed content hash. The current implementation limits stored revision snapshots for an individual note rather than keeping an unlimited permanent history.
Activity records
QuietNote also keeps a limited local Activity log. Activity entries may describe actions such as creating, editing, pinning, archiving, moving to Trash, restoring, or permanently deleting a note. These records are used only for the extension's local Activity screen.
When a note is permanently deleted, the main note object and its revision history are removed. However, a recent local Activity entry may temporarily retain limited descriptive information about the deletion, including the former note title, until that activity entry is displaced by newer activity or all QuietNote data is reset. This distinction is important when users want to remove every local trace of prior note activity.
8. Preferences, interface state, and local operational data
In addition to note content, QuietNote stores settings and internal state required for a consistent local experience. This can include:
- theme selection, such as System, Light, or Dark;
- default note sorting preference;
- whether browser spellcheck is enabled in the editor;
- display and preview preferences;
- the current QuietNote screen, selected note, search text, or selected tag where needed to restore the interface;
- local counters such as opens, sessions, searches, edits, creates, archive actions, history views, storage views, exports, and imports;
- recent active-day markers and local action timing;
- locally generated identifiers, hashes, random seeds, and internal diagnostic/application state used to coordinate the extension's behavior.
This operational information is stored in the same local application state as the notes. It is not sent to the developer and is not used to build an advertising profile, track the user across websites, or identify the user outside QuietNote.
Some local counters describe interactions performed inside QuietNote. They are maintained to support application behavior and local diagnostics. They do not provide QuietNote with access to unrelated browser activity.
9. Storage, persistence, and retention
QuietNote stores its main application state in the extension's own localStorage. The current storage key is:
quietNoteStateV1
This key is an implementation detail for retrieving the local QuietNote state. It is not an advertising ID, Chrome account ID, device fingerprint, or cross-site identifier.
The local save can remain in the browser profile between sessions so notes are still available after the popup closes. The developer does not control a remote retention period because the current version does not keep a server-side copy.
Local QuietNote information may remain until it is changed or removed through normal note actions, permanent deletion, Empty Trash, the QuietNote Reset function, browser storage controls, browser-profile deletion, extension removal, administrator policy, or other browser/device management.
The current implementation places practical limits on some local structures, such as recent activity records and revision snapshots, so those supporting records are not intended to grow without bound.
10. Import and export backups
Export
QuietNote provides a user-initiated JSON export. When the user selects Export notes, the extension creates a file in the browser containing note data intended for backup or transfer. The exported file can include note identifiers, titles, bodies, tags, pin/archive/trash status, creation and update timestamps, revision snapshots, and QuietNote settings.
The current export does not include the full internal application state. For example, the local Activity log, most local usage counters, and internal operational/diagnostic state are not part of the standard QuietNote export payload.
The file is created locally using browser file-download behavior. QuietNote does not upload the export to the developer. After export, the user controls where that JSON file is stored, copied, backed up, or shared.
Import
QuietNote reads a backup only after the user deliberately selects a JSON file through the Import function. The selected file is parsed locally in the extension. Notes from a valid QuietNote export can then be added to the existing local collection. Duplicate identifiers may be skipped rather than blindly replacing existing notes.
Imported information becomes part of the local QuietNote storage and is then subject to the same local retention and deletion rules described in this policy.
11. Chrome permissions
QuietNote version 1.0.0 uses Manifest V3 and currently requests no Chrome extension permissions and no host permissions.
The manifest does not request access to tabs, activeTab, history, scripting, cookies, downloads, notifications, geolocation, or Chrome's extension storage permission.
QuietNote uses ordinary browser capabilities available inside its own popup, including the DOM, localStorage, user-selected file input, Blob/object URLs for user-triggered backup export, and normal editor controls. These capabilities do not give the extension general permission to inspect arbitrary websites.
12. Website, tab, and browsing access
QuietNote runs in its own toolbar popup and does not need to inspect the page behind the popup to provide its note-taking features.
The current version does not:
- read the URL of the active tab;
- read page titles, text, images, links, forms, or DOM content;
- inject content scripts into websites;
- monitor open tabs;
- read Chrome browsing history or search history;
- read website cookies;
- read localStorage or sessionStorage belonging to unrelated websites;
- capture what the user types into web pages;
- track browsing across domains.
The localStorage used by QuietNote belongs to the extension's own origin and is separate from storage belonging to normal websites.
13. Network activity and remote services
The current QuietNote package does not use fetch, XMLHttpRequest, WebSocket, or a developer API for its core features. Creating notes, saving edits, searching, tagging, sorting, archiving, maintaining revisions, viewing activity, and producing backups are handled locally.
The extension does not rely on remote JavaScript, external CSS, remote fonts, cloud note processing, online AI, social-login APIs, advertising endpoints, or analytics endpoints.
Chrome itself may communicate with Google for extension installation, updates, store functionality, browser security, Safe Browsing, account features, or other Chrome services. Your operating system, network administrator, security software, DNS provider, or backup software may also create network activity. Those communications are not QuietNote developer telemetry.
14. Browser spellcheck
QuietNote includes a preference that enables or disables the browser's spellchecking behavior in the note editor. QuietNote itself does not implement a remote spellchecking service and does not send note content to the developer for spelling analysis.
Chrome and the operating system may offer their own spellcheck features. Depending on a user's browser settings, some browser-level or enhanced spellcheck modes may process text differently or may involve services operated by the browser vendor. Those behaviors are controlled by Chrome or the operating system, not by QuietNote.
Users who are concerned about browser-level spellcheck processing can review Chrome's spellcheck settings or disable spellcheck in QuietNote's local preferences.
15. Analytics, tracking, advertising, and cookies
Analytics
QuietNote does not currently include Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, or another comparable analytics platform. Local usage counters described elsewhere in this policy stay inside QuietNote's local save and are not automatically reported to the developer.
Crash reporting
The current package does not include a third-party crash-reporting SDK that automatically sends stack traces, device identifiers, or note content to the developer.
Advertising
QuietNote does not display third-party advertising and does not include advertising-network code, retargeting pixels, behavioral advertising SDKs, or an ad auction.
Cookies and cross-site tracking
QuietNote does not request Chrome's cookies permission, does not use website cookies to store notes, and is not designed to fingerprint the device or correlate users across websites.
17. Security and data minimization
QuietNote reduces privacy exposure by avoiding unnecessary browser permissions, remote analytics, an account database, and a developer-operated note server. The extension package contains the code and assets required to run the core experience locally.
Local storage is not the same as encrypted vault storage. QuietNote version 1.0.0 does not claim to provide end-to-end encryption, password-protected note encryption, hardware-backed key storage, or protection against another person who already has access to the same unlocked operating-system account or browser profile.
Users should keep Chrome and their operating system updated, use appropriate device security, protect exported JSON backups, and avoid storing secrets in plain text if their threat model requires stronger protection than ordinary local browser storage provides.
18. Deleting, resetting, and removing local data
Trash
Moving a note to Trash does not immediately remove it from the local database. The note can still be restored and remains part of the local save.
Permanent deletion
Deleting a note permanently removes the main note object and its stored revision snapshots. As described above, a recent local Activity entry can still contain limited information about the deletion, such as the former title, until the activity history naturally rolls over or QuietNote is reset.
Empty Trash
Empty Trash removes notes currently marked as trashed. QuietNote may keep an activity event stating that Trash was emptied, but that event does not need to preserve the full deleted note bodies.
Reset QuietNote
The Reset function removes the quietNoteStateV1 local save and creates a new blank QuietNote state. This is the appropriate in-app option when the user wants to remove notes, revisions, activity records, settings, usage counters, and internal local state together.
Browser and extension removal
Users may also clear extension-origin storage through Chrome tools or remove the extension/browser profile. Exact browser behavior can vary by Chrome version, operating system, profile configuration, and administrator policy.
19. User rights and choices
Privacy laws in some jurisdictions provide rights such as access, correction, deletion, restriction, portability, or objection regarding personal information held by an organization.
Because QuietNote's main note database is stored locally and is not transmitted to the developer, there is ordinarily no developer-held note account to access, correct, or erase. Users can directly edit or delete their local notes and can create a portable JSON backup using the Export function.
Users can choose whether to use tags, history, archive, Trash, browser spellcheck, or exports. They can also reset QuietNote or uninstall it if they no longer want the local data retained in that browser profile.
If a user has separately contacted the developer by email, they may contact the developer about information contained in that direct correspondence at tuytrung179227@gmail.com.
20. Children's privacy
QuietNote is a general-purpose note-taking utility. It does not create public profiles, require a date of birth, provide public user-to-user messaging, or operate a behavioral advertising system.
The extension is not designed to solicit personal information from children or adults for developer collection. However, because it is a free-form note editor, users can type arbitrary text into their own local notes. Parents or guardians should use device and browser controls appropriate for their household and should consider whether local plain-text notes are suitable for the information being stored.
If a parent, guardian, or other person believes personal information was separately sent directly to the developer by email, they may contact the developer using the address below.
21. Third-party services and browser functionality
The current QuietNote package does not integrate third-party analytics, advertising, authentication, cloud synchronization, social networking, AI, or remote note-processing services.
The Chrome browser and Chrome Web Store are third-party platforms used to distribute and run the extension. Browser spellcheck, downloads, device backups, operating-system file storage, and any service a user later chooses for an exported JSON file may have their own privacy practices.
QuietNote does not control those independent services. Users should review the settings and privacy information of the browser, operating system, backup provider, or storage service they choose to use.
22. Changes to this Privacy Policy
This Privacy Policy may be revised to improve clarity, reflect changes in QuietNote, respond to Chrome Web Store requirements, or address changes in applicable law.
The effective date at the top of this page identifies the current version of the policy.
If a future QuietNote version introduces materially different data handling—such as cloud sync, shared notes, accounts, remote AI processing, analytics, advertising, website access, external APIs, or new Chrome permissions—the privacy policy and relevant store disclosures should be updated before those changes are represented to users.
23. Contact
Questions about QuietNote privacy practices, this policy, or information sent directly to the developer can be addressed by email.