Data practices
Privacy policy
Last updated: October 30, 2026
This policy describes Calendar Control, a personal-use Google Calendar integration operated by Neer Patel and hosted as a Notion Worker. It also describes this static information website.
Google access
The application requests only these Google OAuth scopes:
https://www.googleapis.com/auth/calendar.events.owned— permission to access and manage events on calendars owned by the authorizing account.https://www.googleapis.com/auth/calendar.calendarlist.readonly— permission to read calendar-list information.
The deployed code further restricts operations to the operator’s two permitted primary Google calendars. It uses calendar identity, ownership, timezone and default-reminder metadata, plus event identifiers, titles, dates, times, recurrence, reminder settings, availability and event links. Requested creation may include a description and location. Event records are fetched from Google, including attendee information used to refuse unsupported writes.
Purpose and processing
Google Calendar information is used to answer authorized calendar requests, preview and perform requested supported actions, prevent duplicate creation, and verify results. Relevant results are returned to the requesting Notion agent and can appear in its conversation or execution records. The tool is not a public service for other users to connect accounts.
The information website does not connect to Google Calendar, contain OAuth credentials, or display private events. It contains no application analytics, advertising scripts, forms, or login mechanism. Its hosting provider may process ordinary request metadata to deliver and secure the site.
Storage and service providers
Google stores calendar events. Notion’s hosted OAuth facility manages the app’s account authorizations; the Worker obtains access tokens at runtime without intentionally returning them in tool results. App credentials are configured through Notion’s secure Worker setup, not published with this site.
The Worker code does not maintain a separate calendar database or background synchronization. However, event details returned to the agent may remain in Notion conversations, tool results, operational records, or user-created pages. Notion and its applicable service providers process this information under the terms and privacy controls applicable to the operator’s account. This policy does not promise zero retention or a fixed deletion period for platform records.
Use and disclosure limits
Calendar Control does not sell Google user data or use it for advertising. Its code contains no feature for training generalized AI or machine-learning models. Google data is processed only to provide and support the described user-facing calendar functions through Google, Notion and their applicable service providers; it is not intentionally published on this website or sent to an unrelated external service by the Worker.
Calendar Control’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.
Revoke access and manage retained information
You can revoke the application’s Google access through Google Account connections. Revocation prevents further authorized access after Google invalidates the authorization; it does not delete existing calendar events or records already retained in Notion. Manage events in Google Calendar and retained conversations or pages through Notion’s available controls. Contact the operator for help with information under the operator’s control; provider retention and backups remain subject to the provider’s terms.
Changes and contact
This policy will be updated if the app’s access or data practices change. Questions or requests can be sent to neerdpatel@fusionspace.co.