Readglass Privacy Policy

Effective date: November 3, 2026 Developer: Yejin Son · ozzaney.github.io

This policy covers the Readglass Chrome extension. The separate macOS development app is outside this policy's scope.

What Readglass does

Readglass estimates reading time from the length of an AI answer and compares that estimate with time spent while the answer is visible in a focused browser window. It includes eligible time during answer generation. These estimates are reflection cues; Readglass does not track your eyes or measure understanding.

Information processed on your device

Readglass handles the following information locally to provide its reading timer:

• Website content and personal communications: AI answer text is read temporarily in memory to estimate reading time. In pages you connect, the current message editor's text is checked temporarily to tell whether an attempted send clears the editor. Prompts, drafts and answers are not saved in timing records or transmitted to the developer.
• Page context: The current page's domain and conversation path are checked in memory to choose the website adapter and reset the timer when the conversation changes. Readglass does not access the browser history API or store a list of sites you visited, page URLs, page titles, or conversation identifiers.
• User activity related to the timer: Answer visibility, window focus, generation state and the next message or a manual finish are observed to start, pause and stop timing. Readglass does not record keystrokes, clicks or mouse movements as a log. Pointer movement is used only while you are explicitly selecting an answer.

Automatic scripts run on ChatGPT, Claude, Gemini, Perplexity and DeepSeek domains listed in the extension. On another website, reading access begins only when you use Readglass's Connect this page or Pick an answer controls.

Information stored in this browser

Readglass uses chrome.storage.local for:

• Settings: enabled/disabled, interface language, full/compact display, and the two reading-speed references.
• Up to 100 timing records, each containing only the record timestamp, focused/visible time, total elapsed time and estimated reading time. The popup displays the latest five records.

Timing records do not contain conversation text, URLs, conversation IDs, CSS selectors or account identifiers. Readglass does not use Chrome Sync to synchronize this information. It has no developer-operated account or remote database.

Information sent to the developer or third parties

The extension does not transmit conversation text, timing records, settings or other usage data to the developer or to third parties. It contains no analytics, advertising, trackers, remote translation service or model API connection. It does not sell data or use data for advertising, profiling, AI model training or unrelated purposes.

All extension scripts and translations are packaged with Readglass. Readglass does not download or execute remote code.

If you voluntarily follow the author's website/privacy links, your browser opens that site, which is subject to its hosting provider's practices. This policy page has no analytics scripts or cookies added by Readglass. GitHub Pages hosts the page and may process routine request information; see GitHub's privacy statement. Chrome Web Store installation and update delivery are handled by Google under Google's policies. AI services' own processing of your conversations is governed by their respective policies.

Permissions and why they are needed

• storage: saves the local settings and bounded timing history described above.
• activeTab: provides temporary access to the current page after you invoke Readglass for an otherwise unsupported website.
• scripting: injects the packaged reading timer and answer picker into that page at your request.
• Content-script site access: lets the timer detect AI answers and their generation/send state on the five supported services. It is not general background access to every website.

Retention and deletion

Timing history stays in this browser until you clear it or remove the extension. New records replace the oldest ones after the 100-record limit is reached. Open the Readglass popup and choose Clear history to remove timing records while keeping settings. Settings can be changed in the popup. Removing Readglass removes its extension-local storage. Disabling the timer stops new measurements without deleting earlier records.

Limited use

Information accessed through Chrome APIs is used only to provide Readglass's visible reading-timer features. Readglass's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact and changes

For privacy questions or deletion guidance, contact Yejin Son at sonyejin@cs.ubc.ca. If you email the developer, the address and message you choose to send are used to respond to your request; please avoid including private conversation text. Readglass itself does not send support messages automatically.

Material changes to these practices will be reflected in this policy and its effective date.