Privacy Notice

How OMC handles data.

Last updated October 26, 2026

This notice explains how Robert Igarashi’s personal calendar utility accesses, uses and retains information.

Information accessed

With authorization, OMC reads Google calendar names, identifiers and access information, including calendars listed as hidden. For selected calendars, it reads event titles, descriptions, dates and times, availability, recurrence information, organizers, attendees, locations, meeting links and event identifiers.

Calendar coordination

OMC uses this information to coordinate availability and maintain managed calendar copies. Depending on configuration, a master calendar receives event details, while other selected calendars receive generic busy or availability blocks. Copies can be stored in Outlook or Google Calendar. Authorization credentials support continued access until access is revoked or otherwise becomes unavailable.

Private events

Private-event settings limit details in synchronized copies, but do not provide complete anonymization. Master copies can replace the title and omit the original description, location and attendee list while still including source references, organizer information, identifiers or meeting links. Generic blocks omit the event description and location. Direct calendar-reading tools can return private-event details to an authorized connected consumer.

Storage and connected tools

OMC stores synchronization identifiers, timestamps, tracking information and operational records locally. Logs and run summaries can include event subjects, diagnostic samples and error information. Its diagnostic database can also store calendar names, identifiers, access information and health reports.

Calendar-reading tools using the Model Context Protocol (MCP) can provide event details to connected assistants or other authorized consumers. Managed copies can also be read by tools connected to the destination calendar, such as a calendar briefing integration. Those consumers may process or retain the information they receive under their own settings and policies.

Disconnecting and removing information

You can revoke OMC’s Google access through your Google Account’s third-party connections settings. Revocation stops future access using that authorization; it does not itself guarantee removal of prior calendar copies or stored records. Removing a local authorization is also separate from revoking access at Google.

Disabling a connection, removing its configuration and cleaning up managed copies are different operations. Some removal options include cleanup. Data removal is a separate operator-managed process; contact Robert to request review or removal. OMC does not currently apply a fixed automatic deletion deadline to all retained records.

This website and notice updates

These information pages contain no sign-in forms, analytics scripts or embedded third-party assets. The website host may process ordinary request information to deliver the pages. Robert will update this notice when data-handling practices change and revise the date shown above.