Privacy information

Calendar access and use

TrimlightBridge requests Google's read-only calendar-event permission. That permission can allow reading calendars available to the authorizing account, but the application requests events only from one configured calendar. Google may return additional event fields; the lighting logic uses event identifiers, titles, start and end times, time zones, and cancellation status to select saved lighting patterns. It never creates, edits, or deletes Google events.

Storage and display

The owner's computer stores Google authorization credentials, configuration, and automation state. State includes an active or held event identifier, selected pattern, event end time, and manual-override state. Current and upcoming event titles and times may appear in the private bridge interface.

Local operational logs rotate by size. Credentials remain until replaced or removed; automation state is updated as the application runs. There is no automatic age-based deletion policy. Separately created backups may retain older copies.

Data handling

The current implementation uses Calendar data for personal lighting automation and contains no advertising, sale-of-data, or AI-training integration. Google processes Calendar API requests. The local controller receives lighting commands. Operational monitoring receives health pings without Calendar event contents in the ping payload.

Where a reverse proxy provides access to the private bridge, that provider processes the traffic, which can include event information displayed in the private interface. This public site does not retrieve Calendar events or contain Google credentials. Cloudflare Pages hosts this information site. Cloudflare may process request information such as IP addresses and browser details to deliver and protect the site. See Cloudflare's privacy policy. These pages contain no analytics scripts, forms, or advertising.

Revocation and deletion

The owner can revoke access through Google Account's third-party connections settings. Revocation stops future authorized access but does not erase existing local files. The owner can disable Calendar integration and remove local credentials, automation state, logs, and retained backups as appropriate. Removing local files does not delete Google Calendar events.

Contact

Questions or data-removal requests: basementgame.unlisted472@aleeas.com.