Privacy policy

Google Calendar data

With the owner's permission, the app uses read-only event access to read a selected calendar. It requests event identifiers and revisions, recurrence information, start and end times, locations, event types, cancellation status, and attendee identity and response fields. It uses these fields to identify trips, exclude unsuitable events, detect changes, and avoid duplicate preparation. It does not request event titles, descriptions, or attachments in its event-list requests.

The app does not create, edit, or delete Calendar events. Google Calendar data is used only for this personal trip-preparation function. It is not sold, used for advertising, or used to train machine-learning models.

Routes and vehicle data

To estimate driving time, the app sends the configured origin, a qualifying event's destination address or coordinates, and the proposed departure time to Google Routes. It receives travel-time and location-match information.

With separate vehicle authorization, the app uses Tesla account and vehicle information, including the selected vehicle's identity, connection state, and preconditioning schedules with their locations. It sends Tesla the schedule settings and destination information needed for authorized preconditioning and navigation commands. Calendar titles and descriptions are not needed for those commands.

Local storage and retention

Account tokens and API credentials are stored in macOS Keychain. The local setup also keeps private configuration, signing material, normalized event and trip-planning state, command records, and selected verification snapshots. These records can contain addresses, coordinates, times, and vehicle identifiers. They are not included in this public website.

During normal planner runs, expired local planning records are removed after their appointment is more than seven days old. Calendar observation and command-ownership history, configuration, verification artifacts, and aggregate Routes usage records have no automatic deletion deadline. The owner can stop the local service and remove its local files and Keychain entries when they are no longer needed. Revoking account access does not itself erase existing local records or change schedules already stored in the vehicle.

This public website

Cloudflare Pages hosts this website and the Tesla public key. The site has no advertising, analytics scripts, or app account database. Cloudflare may process ordinary request information, such as IP addresses and URLs, to serve and secure the site.

The Tesla callback page receives an authorization response in its URL. Its local browser script removes the query from the displayed URL and lets the owner copy the response into a hidden local terminal prompt for validation and exchange. It does not exchange the response on this website or save account tokens here. The initial callback URL is nevertheless sent to the hosting provider; this policy does not promise that provider request logs omit it. Google authorization uses a local loopback callback on the owner's Mac.

Control and access removal

The owner can stop the local tool, revoke its access through Google or Tesla account settings, and delete its local data and Keychain credentials. Any automation-created vehicle schedule should be reviewed separately before removing the local records used to identify it. As an owner-only tool, the app does not offer public registration or a third-party account support service.