Scope and operator
Calendar Precision is a local Google Calendar integration developed by Josh Levy for his personal use through Codex on a Mac. It has no public registration and is not operated for other users. This policy covers the integration and this informational website. Google and OpenAI operate their own services under their respective policies.
Google Calendar access
The integration uses Google authorization to access calendars available to the connected Google account. It can read calendar identifiers, names, access roles, and time zones, and retrieve event data to carry out requested operations.
Event information can include titles, descriptions, locations, dates, times, time zones, availability, status, event identifiers, calendar links, and update timestamps. Google’s responses can also contain other event fields, such as organizer, attendee, recurrence, or attachment information. The integration returns a selected set of event fields to Codex rather than forwarding the full Google response.
The current setup requests https://www.googleapis.com/auth/calendar. Google describes this broad permission as allowing access to see, edit, share, and permanently delete calendars accessible to the account. Calendar Precision currently exposes calendar reading, event creation and updates, and event audits. It does not expose a delete tool or calendar-sharing management.
Calendar data is accessed to answer calendar requests, prepare changes, apply requested changes, and review results. The authorization also permits the integration to obtain fresh access tokens without a new Google sign-in on every request.
Use and sharing
The local integration communicates with Google’s authorization and Calendar services. New or changed event information is sent to Google when a change is applied. Calendar sharing and event visibility settings determine who can see that information in Google Calendar. A request can also select Google’s guest-update notification options.
When used with Codex, calendar results and change previews are returned to Codex and may be processed by OpenAI’s services. This can include event titles, dates, descriptions, locations, and identifiers. Processing and retention by that service depend on the product, account settings, and applicable provider policies. See OpenAI’s privacy policy.
The integration does not include advertising, advertising analytics, a sale of calendar data, or an additional hosted calendar database. This website does not receive calendar data from the integration. Any exports or copies you choose to create or share are separate from the integration’s own storage.
Calendar Precision will use and transfer information received from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Calendar information is used for the requested personal calendar features and their change records. The operator does not use it for advertising, sale, or training generalized AI models. Model-improvement sharing is turned off in the OpenAI account used with this integration.
Storage and retention
- Google Calendar: your calendar and event records remain with Google until changed or removed through an authorized service, subject to Google’s policies.
- Authorization credentials: the OAuth client details and refresh token are stored in macOS Keychain. Access tokens are used in the running local process. The integration does not intentionally return tokens as tool results.
- Local change logs: applied creation and update operations are appended to a local file on the Mac. Records can include calendar and event identifiers, submitted content, timestamps, and before-and-after event details. These logs are not encrypted by the integration and have no automatic deletion or expiration.
- Codex records: tool results, previews, and conversation content can remain in Codex or associated service records. Their retention and deletion controls are separate from the integration.
- Setup files and backups: a downloaded Google client configuration file is not automatically removed by setup. Local backups or synchronization may preserve copies of files according to the user’s own settings.
The integration uses HTTPS for requests to Google and macOS Keychain for stored authorization credentials. Security of local logs, device backups, and any copied records also depends on the Mac and services used with it.
Your controls and deletion
You can stop using or disable the integration and remove its access through your Google Account’s third-party connections. Revoking access stops future authorized requests but does not erase existing events, local logs, downloaded files, backups, or conversation history.
You control deletion of local credentials and logs on your Mac. Use the relevant Google and Codex controls to manage data held by those services. Deleting a local log does not undo a Google Calendar change. For questions about data handling or help locating the relevant controls, contact the developer below.
This informational website
The website contains static information about Calendar Precision. It does not connect to Google Calendar, ask you to authorize Google access, display calendar events, or accept file uploads. Its pages include no advertising, analytics scripts, embedded third-party content, or app-set cookies.
This website is hosted on Cloudflare Pages. Cloudflare receives ordinary connection information, such as IP addresses and request metadata, to deliver and protect the website. That information is governed by Cloudflare’s privacy policy. Following an external link takes you to a separate service.
Contact and policy changes
Operator: Josh Levy. Contact: jlevy.dev@gmail.com.
If you send an email, your message and email address are used to respond and may remain in the email correspondence. Do not send passwords, authorization codes, tokens, or private calendar exports.
This policy should be updated before any material change in the integration’s data practices. A new date will identify the revised version, and additional consent will be sought when required.