Privacy policy

Lens for Google Calendar is developed by Ishaan Hiranandani. Contact ishaanhiranandani@gmail.com with privacy questions.

What Lens accesses

With your consent, Lens reads your Calendar account identity, calendar list, calendar access levels, and event data. Event data can include titles, dates, attendees, organizers, meeting links, locations, descriptions, and response status. It reads event identifiers and the active account shown on Google Calendar to display matching details.

How Lens uses this data

Lens matches busy blocks to event copies your account can already read. For work accounts, it can discover other readable calendars from colleague addresses present in those events. It does not bypass Google permissions. Lens does not create, edit, delete, or respond to calendar events.

Storage and retention

Event matching runs in your browser. Resolved details are cached locally for up to five minutes of use. Expired entries are excluded from display and removed during cache maintenance. If the extension is inactive, expired records can remain on disk until it runs again. Calendar discovery metadata is reused for up to one hour. The connected account and settings remain until you disconnect or remove the extension. Browser-managed credentials or session-only access tokens allow Google API access.

Sharing and security

Lens communicates with Google for authentication and Calendar access. Lens does not send Calendar data to a developer-operated server. We do not sell Calendar data, use it for advertising, or use it to train AI models. The website host may process ordinary request information such as IP addresses and browser metadata to serve and protect the website. The website does not receive your Calendar events or OAuth tokens.

Google API Limited Use

Lens for Google Calendar’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Your choices

Use “Disconnect and clear data” in the extension to remove its local saved data and stop displaying added details. You can also remove Lens and revoke its access from your Google Account connections. Removing the extension clears its extension storage. No developer-held Calendar database needs to be deleted.

Changes

Updates will be posted here with a revised date. Any broader Google access will require a new permission grant.