Browser Diary

Browser Diary Privacy Policy

Browser Diary is a local-first Chrome extension: it records the pages you visit so that you can find and review them yourself.

Last updated
October 29, 2026
Build
0.3.0 (source 79c9226)
Publisher
limer
Contact
weiyezhu180@gmail.com
Policy URL
https://browser-diary-privacy.pages.dev/en/

What the extension handles

After your first informed confirmation, Browser Diary records eligible HTTP(S) page titles, addresses, readable page text, visit timestamps and confirmed foreground intervals. It also stores your categories, saved state, notes, display choices and locally created reports. Browser-history import happens only when you choose it; imported entries do not include historical page bodies or measured reading time.

Records and local search indexes are stored in your browser profile on your device. On-device search and local report generation do not require sending these records to a publisher server. Browser Diary does not sell browsing records or use them for advertising. The reviewed extension includes no advertising or analytics SDK.

Controls and scope

You can pause recording, set a temporary pause, turn automatic recording off and exclude domains. Private windows are disabled; browser internal pages and local files are outside capture scope. The page extractor omits form controls and editable regions and does not read form field values. Readable pages can still contain sensitive information; exclude sensitive sites or pause recording as needed.

Network requests

If you enable meaning search, a model is downloaded from Hugging Face and its delivery infrastructure, or from the model host you choose. Those hosts can receive normal connection metadata, such as your IP address and the requested file. The model runs locally with the bundled runtime; your search query and indexed page text are not uploaded as part of local inference. Opening a source page navigates to that website under its own privacy practices. Website identities use Chrome's favicon facility rather than a separate icon-analytics service.

Optional connected services

The default local core has no configured publisher account service. If you actively connect one, your email address and sign-in data are sent to that service; session tokens and entitlement information can be kept locally. A purchase can involve an external checkout provider, and the service can retain order and entitlement records. Card-entry details are handled by the checkout provider.

If you request cloud AI interpretation, you first review a summary containing a period, aggregate statistics, selected titles and your category labels. The confirmed summary is sent to the connected service and its configured AI provider. Page bodies, notes, URLs and raw visit logs are excluded from that summary. Selected titles and category names can still reveal sensitive interests. Cloud processing is optional and separate from local search.

The current release (0.3.0) does not enable a publisher account, payment or cloud interpretation service. If such services are enabled later, the legal operator, hosting, email, payment and AI providers, processing locations, server logging, retention and deletion rules, and public contact will be disclosed in the product first, and this policy will be updated accordingly.

Retention, access and deletion

Local records remain until you delete them through the extension or remove the relevant browser-profile data. Retention settings suggest a cleanup period; deletion requires your confirmation. You can review records, exclude sites and export or restore local backups. Copies you export, downloaded artwork and model caches may remain separately; delete these copies where they are stored. Uninstalling the extension does not delete exported files or records held by an optional connected service.

The publisher cannot recover device-only records you have not shared. Requests concerning a connected service must go to that service operator using the contact information supplied before activation.

Sharing and limited use

Records leave the device only through actions such as opening source pages, exporting files, sharing artwork or confirming an optional cloud summary. Review your own title and caption before sharing: public artwork hides source identities but retains text you authored.

Browser Diary's use of information received through Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data handling is limited to the diary, recall, visualization, reporting and optional account/purchase functionality described to users. It is not used for advertising profiles, data brokerage or unrelated creditworthiness decisions.

Changes and contact

Changes to this policy will update the date above. Material changes in data practices must be disclosed in the product before the affected processing begins. Contact weiyezhu180@gmail.com with privacy questions.

This page is the public privacy policy URL for Browser Diary's Chrome Web Store listing. It is permanent and requires no sign-in. The Chinese version is at /.