Privacy Notice
Privacy
This page explains what the Glasses website and app collect today, what they do not collect, why that data exists, and how telemetry can be turned off.
App privacy
Glasses is designed to run locally on the user's device. The app is intended to help users capture and review slide-based course material for their own study workflow.
Glasses does not upload slide images, screenshots, OCR text, slide text, filenames, PDFs, course content, study material, or other personal files as part of its basic usage telemetry.
App telemetry
The app may send limited telemetry to the Glasses backend to help measure rollout health, version adoption, update behavior, and basic feature usage. The telemetry data is limited to fields such as:
- event name and timestamp
- app version and build version
- a random local install ID generated on first run
- license ID, if a license is present
- platform information such as Windows
- a small event properties object for counts, status, or feature flags
Telemetry events are limited to download starts, first run, app launch, daily heartbeat, update check, update installed, capture started, capture stopped, review completed, and app error. The properties object is intended for small non-content metadata only, such as capture counts, update status, or error type.
What telemetry is for
This telemetry is used to understand whether Glasses is being installed successfully, which versions are still active, whether update checks are working, and whether key flows like capture and review are working.
Telemetry retention
App telemetry data is intended to be retained for up to 90 days. Aggregated daily summary rows may be kept for up to 12 months so the project can see adoption trends over time without keeping detailed event rows forever. License request emails may be retained longer if needed for support history.
Telemetry controls
The app includes a Basic usage and error reporting setting. If you turn that setting off, the app will stop sending new usage telemetry and clear any locally queued telemetry that has not been sent yet. This setting may be on by default with this disclosure in place.
Website data
The website may collect standard server or hosting logs, such as IP address, browser type, requested page, and timestamp, as part of normal website operation and security.
Accounts and sign-in
Glasses accounts are handled through Clerk. If you create or sign in to an account, the website may receive account identity information such as your email address, display name, sign-in provider, verified email status, and a provider user ID. Glasses uses that information to show your dashboard, associate access requests with your account, and manage future license or entitlement records.
At launch, account sign-in is intended to use Google, Microsoft, or email one-time code options. Password-based sign-in is not planned for the initial account rollout.
When a public installer download is posted, the download button is intended to route through a backend redirect that records one download-start event before redirecting to the installer file. That logging is used to count installer starts and monitor release rollout.
License requests
If you submit a license request on the website, Glasses support collects the contact details and message you provide, such as your name, email address, organization, intended use, and any optional notes. Account-based access requests are also associated with your account ID and request review status. That information is used to review the request, grant or deny app access, create license or entitlement records, and reply by email. It is not to be used for unrelated marketing.
Bug reports and feedback
The desktop app can send classified bug reports and product feedback through a linked Glasses account. These submissions include the comments you enter, selected categories, app and platform versions, account and linked device identifiers, and standard request security data such as a hashed network address. Submission metadata is intended to be retained for up to 90 days. Support emails may be retained longer when needed to investigate an issue or maintain support history.
Bug reports include an optional recent-app-logs checkbox that is on by default. The app explains before submission that logs may contain local file paths, course names, and session metadata. The report archive excludes slide images, PDFs, full OCR results, queued telemetry, and account credentials. The archive is sent as an email attachment and is not stored in the support-submission database.
Contact
For privacy questions, contact:
Last updated: June 11, 2026