CalendarRules Privacy Policy
Effective: November 14, 2026 · Project: CalendarRules, an independently developed open-source eisy / IoX plugin
CalendarRules reads Google Calendar event information so that users can map their own calendars to existing Universal Devices IoX state variables. This policy describes how the CalendarRules plugin accesses, uses, stores, and shares Google user data. It is designed to run on a user's own eisy controller, not as a hosted calendar-processing service operated by the developer.
Google information requested
CalendarRules requests the Google Calendar read-only OAuth permissions https://www.googleapis.com/auth/calendar.events.readonly and https://www.googleapis.com/auth/calendar.calendarlist.readonly. These permissions let the plugin retrieve calendar lists, selected calendars, and their events; they do not authorize CalendarRules to create, edit, or delete Google Calendar events.
The event data retrieved for the calendars a user configures can include event titles, locations, start and end times, recurrence and cancellation information, and technical event identifiers used to interpret the schedule. Calendar IDs and matching rules are stored as user-supplied configuration.
How Google data is used
CalendarRules checks calendar event titles or locations against the user's configured rules and time offsets. It calculates whether each configured existing IoX type-2 state variable should have value 0 or 1, subject to the plugin's authorization and safety checks. The user's own ISY programs determine what to do with those variables.
Google Calendar event data is not used for advertising, marketing profiles, or unrelated analytics, and is not sold. CalendarRules does not directly command HVAC, lighting, doors, or other equipment.
Where data is stored
CalendarRules runs on a user's eisy controller. It saves configuration in the eisy-ui / Polyglot supported configuration storage and retains a local event schedule cache to evaluate events between Google requests and during temporary connectivity failures. The cache may contain event titles, locations, times and processed event identifiers. Its configured maximum offline eligibility is 30 days, subject to actual schedule coverage; this is a validity limit, not a guarantee that stored files are automatically erased after 30 days.
OAuth authorization and refresh tokens are handled by the Universal Devices eisy-ui / Polyglot OAuth integration. CalendarRules does not intentionally include tokens in its schedule cache or source repository. The plugin's calendar schedule cache uses restricted local file permissions and integrity checks; it is not encrypted at rest by the plugin. eisy-ui backups or other user-controlled device backups may retain local plugin data.
Sharing and third-party services
CalendarRules communicates with Google Calendar APIs to retrieve information requested by the user and uses the Universal Devices eisy-ui / Polyglot platform for OAuth, configuration, status and local IoX integration. Calendar-derived decisions are sent to the user's own IoX system as numeric variable values. The plugin is not designed to upload calendar event contents to a separate developer-operated server.
CalendarRules is open source and published on GitHub. The project website is served through GitHub Pages. Those services may process website or repository visits under their own privacy policies; visiting this website is distinct from authorizing the plugin to access Google Calendar.
What appears in logs and status
Status notices can show rule names, state-variable IDs, event times, and aggregate counts. Display of event titles is optional and off by default; event locations are not intended to appear in activity notices. Users should still avoid sharing diagnostic logs or screenshots publicly without checking for private calendar or configuration details. The plugin requires safe logging settings for Google authentication and IoX writes.
Retention, revocation, and deletion
Users control which calendars and rules they configure. They may revoke CalendarRules access in their Google Account's third-party connections / permissions settings. Revocation stops future authorized Google Calendar requests but does not automatically erase local cached events, configuration, OAuth records, or backups from an eisy controller.
Users can disable rules, stop or uninstall the plugin, and remove local plugin data using their controller's supported management and backup procedures. Reinstallation or restoring a backup may restore prior data. Consult the Universal Devices platform documentation before deleting protected application files; if you need help understanding what remains stored, contact the project through the support link below without posting confidential data.
Security and limitations
CalendarRules is beta software. Missing or untrusted schedules cause its write gate to close rather than treating missing events as an empty calendar. Previously set state variables can remain at their last value if the plugin stops or loses authorization; users are responsible for independent equipment fail-safes. For further details, see the security documentation.
Updates and contact
Material changes to Google data handling will be reflected in this policy and dated here before being introduced to general users. For privacy questions, support, or requests about the project, use CalendarRules GitHub Issues. Do not include OAuth tokens, calendar contents, addresses, or passwords in public reports.
CalendarRules' use of Google user information is intended to be limited to providing and improving the user-facing calendar-to-variable functionality described here and to follow the Google API Services User Data Policy, including its Limited Use requirements.