Memolight

Add private notes and color markers for usernames or selected text. Local by default; Drive sync is optional.

Memolight helps you remember who said what—and why it mattered. Add a private note, short label, and color marker next to usernames, authors, or selected text you encounter on the web. The next time that person or phrase appears, your own context is right there—without creating a Memolight account or sending your notes to a developer-operated server. How it works On supported community pages, select the dot next to a username or author to add a personal note, short label, and color. On websites you allow, open a quick memo from selected-text right-click, the toolbar, or the customizable Alt+Shift+M shortcut. Choose This page or This site for phrase memos, or add a note to the page itself without selecting text. Page notes reappear when you return. Phrase matching can also be limited with CSS selectors. New memos can keep a sanitized source URL, page title, and short context snippet so you can return to the original page later. The Current Page Hub shows whether the active page is supported, enabled, and allowed, together with saved-memo, match, detected-target, marker, and sync status. From the hub you can write a quick memo or page note, open Memo Manager, or view a detailed page diagnosis. The summary does not include memo content or the full page URL. Key features - Built-in author markers for supported community sites, with per-site access controls - Notes, short labels, five marker colors, sanitized source context, and hover previews - Quick capture, page-only or site-wide phrase memos, and standalone page notes on user-approved domains - Search, filters, sorting, editing, recent changes, the latest 20 memo versions, and recoverable deletion - Extension-origin memo UI that keeps memo text, labels, source context, history, and unsaved drafts out of the website DOM - Readable CSV export and password-protected AES-GCM backup export/import - Optional encrypted Google Drive synchronization, Sync now, disconnect, and separate Drive-data deletion - Optional community activity alerts through the browser's existing signed-in session - Korean, English, Japanese, Traditional Chinese, and dark-mode UI Private and local by default Core memo features require no Memolight account or sign-in. By default, notes, settings, history, and recoverable deletions stay in Chrome's local extension storage. Local extension storage is not separately encrypted by Memolight and relies on the security of your device and browser profile. Website access is requested only for supported sites or custom domains you choose. An optional all-sites shortcut can be revoked at any time and is used only on built-in supported sites and custom domains you explicitly enable. Source context is stored only for a memo you create. Memolight sanitizes the source URL and keeps a page title and short snippet to help you recognize the original context. It does not collect general browsing history. Optional Google Drive sync Google Drive sync is off until you explicitly connect your Google account. When enabled, memo data, labels, colors, phrases, source context, history, deletion markers, synced custom-site definitions, and a random installation ID are encrypted on your device with AES-GCM and sent directly to your hidden Google Drive app-data space. There is no developer-operated sync server. Memolight requests only drive.appdata, so it cannot view or modify normal Drive files. The sync key is stored in that same hidden Drive app-data space so another installation can reconnect with the same Google account. This is not zero-knowledge encryption against access to the Google account or Google itself. Chrome manages the OAuth access token. The account email used to identify the connection and verify destructive recovery stays in local extension state and is not added to synchronized data. If a rare terminal remote-vault corruption pauses automatic sync, a full vault rebuild is offered only after an encrypted backup of the unchanged local database is downloaded in the same session, the connected account is verified, and the user enters an explicit confirmation phrase. Memolight replaces only identified Memolight objects, then reads back, decrypts, and compares the new vault. Other devices must reconnect afterward. Optional community alerts use the browser's existing signed-in session only after you enable the feature. Memolight does not request cookie access, copy login cookies, keep the original HTML response, or send activity data to a developer server. Data use Websites may observe marker existence and color and, when enabled, the page-count badge. Ordinary page scripts cannot read private memo fields from the isolated editor. CSV exports are not encrypted; encrypted backup files and Drive snapshots are. Store exported files carefully. Memolight does not use user data for analytics, advertising, tracking, sale, creditworthiness, data brokerage, or unrelated purposes. It does not download or execute remote code. Why permissions are needed - Storage: Keeps user-created memos, labels, colors, sanitized source context, history, deletion records, settings, optional sync and recovery state, and bounded diagnostics locally. - Scripting: Registers or removes content scripts only on built-in sites and custom domains you explicitly enable and grant, to detect targets and render memo markers. - Context menus: Opens a private memo draft for selected text or the current page after your context-menu action; it is stored only when you choose Save. - Active tab: After you select the toolbar icon, temporarily checks current-page permission, configuration, target, and marker counts; the saved diagnosis excludes memo text and the full URL. - Alarms: Schedules optional Google Drive synchronization and, only while community alerts are enabled, the interval you choose for activity checks. - Identity: After an explicit Connect action, authorizes only the drive.appdata scope for optional encrypted synchronization. Normal Drive files remain inaccessible. - Notifications: Requested only when you enable or test community alerts. - Website access: Requested per supported site or user-added domain, or through your reversible all-sites choice. Content scripts run only on enabled built-in or custom sites.