Privacy Policy

Last updated: November 8, 2026
Developer / Publisher: nightjar
Contact: heynightjar@gmail.com

1. Overview

Infinite Scrolling for Google Calendar™, also called Infinite Calendar, is an independent browser extension that replaces google's native calendar's month view with a continuously scrollable calendar grid. It is not affiliated with Google.

The extension accesses and processes calendar information to provide these features. Calendar operations communicate directly between your browser and Google. The developer does not operate a backend server, database, or proxy that receives your calendar records or authorization tokens. The extension contains no advertising, analytics, or automatic telemetry.

2. Information accessed and why

With your authorization, the extension uses Google's Calendar API to access your calendar list and event records. These may include calendar names, identifiers, colors, access permissions, and time zones; event titles, descriptions, locations, dates, times, recurrence information, organizer and attendee information, and other metadata returned by Google.

The extension uses this information to display your calendars and perform supported operations you request, such as creating, editing, moving, copying, and deleting events. Shared invitations and meeting descriptions may contain content supplied by other people. Event locations are Calendar text and may include physical addresses; the extension does not request GPS or device-location access.

The extension also reads relevant parts of the Google Calendar page to integrate its interface. Where identifiable, the account email displayed on the page helps match the connected account. It can be sent to Google as a sign-in hint; the extension separately checks the account returned by Google's API before proceeding with account-specific operations.

Google handles sign-in and consent. The extension receives authorization tokens, not your Google password. It requests these OAuth permissions:

• calendar.events (https://www.googleapis.com/auth/calendar.events): read events and perform supported event changes requested by you.
• calendar.calendarlist.readonly (https://www.googleapis.com/auth/calendar.calendarlist.readonly): read your calendar list and associated display settings, access roles, and time zones.

The extension does not request access to Gmail inboxes, Google Contacts, or text/chat services. Names and email addresses can nevertheless appear in Calendar records. It does not collect a browsing-history list or record interaction analytics such as clickstreams or keystroke logs.

3. Storage, security, and retention

• Calendar data: Event data is cached in the Calendar tab's memory for the scrolling view, rather than written to persistent extension storage. Disabling the view or reloading/closing the tab clears this application cache. Displayed calendar information is rendered into the Google Calendar page.
• Undo and redo: Up to 30 recent reversible operations, including event fields needed to reverse changes, are kept in tab memory. History is cleared when the view is disabled or the tab reloads/closes.
• Authorization: Tokens, the account identifier used as a sign-in hint, and the authentication-provider preference are cached in extension session storage. Web tokens and associated sign-in settings may also be saved in browser-local extension storage after access has been restricted to trusted extension contexts. If that restriction is unavailable, the extension uses session storage instead. Tokens are not sent to content scripts or browser sync. Chrome may separately manage native authorization tokens through its identity service.
• Token retention: Cached web tokens can remain until replaced, rejected, or extension storage is removed. Expiration makes a token unusable but does not necessarily erase its stored copy.
• Preferences: The enabled setting and calendar visibility choices are saved using browser sync storage. Calendar identifiers can contain email addresses. Your browser may synchronize these settings across devices, depending on its settings and capabilities.
• Clipboard: Copying an event can place its title on your system clipboard. The event details used for pasting remain in the active view's memory. Clipboard access, synchronization, and history are controlled by your operating system and other software.

Calendar API and authorization requests use HTTPS. Stored data relies on the browser's storage isolation and your device's protections; the extension does not add its own encryption layer to browser storage. Restricting access to trusted extension contexts is an access-control measure, not a claim of additional encryption.

4. Sharing and external services

The extension exchanges calendar data and authorization information with Google to provide the features you request. The developer does not receive a server-side copy of your calendars or tokens, sell your calendar data, or send it to advertising or analytics providers. Browser-synced preferences are handled by your browser's sync service.

An optional Donate link opens Buy Me a Coffee. The extension does not attach your calendar data or authorization tokens to that link, process payments, or receive payment details through the extension. If you visit or donate, that service's privacy practices apply.

Google and your browser provider process information according to their own applicable policies. The extension cannot control data you independently share with those services or other applications.

5. Your choices and deletion

You can turn the extension's view off using its toolbar popup. This restores the native calendar view but does not revoke Google authorization or erase saved settings and credentials.

You can revoke the extension's access in your Google Account third-party connections settings. Uninstalling removes browser-local extension storage; review your browser's sync settings and any other installations to manage synchronized settings. Clipboard history and device backups are managed separately by your operating system and other software.

Revoking access or uninstalling does not delete events from Google Calendar. Events created or changed through the extension remain in Google Calendar until you manage them there. The developer has no server-side calendar copy to retrieve or delete.

6. Limited Use commitments

The extension's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Chrome Web Store User Data Policy.

Calendar information is used only to provide the extension's disclosed calendar features. It is not sold or used for personalized advertising, unrelated profiling, determining creditworthiness, lending, or training generalized artificial-intelligence models. Transfers are limited to those necessary for the disclosed functionality, such as sending requested event changes to Google.

The developer has no remote access to read your calendars. If you voluntarily provide specific information for support, the developer may review that information to respond to your request.

7. Support, changes, and contact

If you contact heynightjar@gmail.com, the information you choose to send—such as your email address, a problem description, or screenshots—is used to respond and troubleshoot. Please redact private calendar information and never send passwords, tokens, or client secrets. Support communications are retained only as needed to handle the request and applicable obligations.

This policy will be updated when the extension's data practices change. The date above identifies the latest revision. Any additional consent required for a change will be requested through the appropriate permission flow.