REVIEW DRAFT โ not published. Prepared November 19, 2026.
Hestia Calendar DEV โ Privacy Notice
This notice describes the bounded Calendar feature of Hestia Calendar DEV, a private household application developed by Hermosillo Infrastructure Group.
What we read and why
With the account holder's permission, Hestia retrieves events overlapping the current Pacific day from one approved Family calendar to show the household's Today schedule.
It requests event title, start and end dates/times, event status, visibility, and whether an end time is unspecified. It also processes the response type, calendar access role and pagination information to validate and complete the read. Only title, times and all-day status are projected into the household schedule.
The adapter does not request attendee lists, event descriptions or notes, locations, conferencing links or event IDs. Cancelled events and events marked private or confidential are filtered out. The shared calendar must still be curated by its owner: a default-visibility event can appear to eligible members of the bound household.
Permission and control
The only requested Google scope is https://www.googleapis.com/auth/calendar.events.readonly. The scope can authorize viewing events across the account's calendars, but Hestia's reader permits requests only to the approved Family calendar. Hestia does not write to Google Calendar or copy calendar events into Home Book or Maintenance.
Storage and retention
Calendar responses and the displayed schedule are processed in memory for the request. The Calendar feature does not store events in Hestia's database. The household Home response is marked no-store.
Remembered authorization is separate from event data. The prepared regular-Hestia implementation stores an encrypted permission record on the household host, outside the source repository and database, with its decryption key stored separately. The record contains the client configuration, refresh permission and approved household/calendar binding. Access tokens stay in memory and are cleared on shutdown. Refresh permission is retained until the operator removes it or it becomes unusable; it is not a permanent guarantee of access.
Who can see calendar data
Eligible, signed-in human members of the approved household can see the shared Today schedule. Household system administrators can access the host and may have access to information processed there. Google processes authorization and Calendar requests as the calendar provider.
This Calendar feature does not sell Google user data, use it for advertising or AI model training, or send it to analytics services, data brokers or unrelated third parties. Its use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Disconnecting and removal
You can revoke Hestia's permission in your Google Account connections. Ask the household administrator to stop the connection and remove the locally saved permission and key using the approved removal procedure. Revocation/removal does not delete the events in Google Calendar. Information already seen by household members cannot be recalled.
Questions
Contact the household administrator through your established household support channel. A public support contact must be confirmed before this draft is published.
This public website
The planned public information site at hestia.hermosilloinfra.com will be hosted on GitHub Pages. It contains only the application description, this privacy notice and the terms of use. It does not connect to the household application or display calendar events.
These pages include no application-added analytics, advertising, forms, scripts, external fonts or cookie storage. GitHub, as the hosting provider, logs and stores visitors' IP addresses for security purposes, including for visitors who are not signed in. See GitHub Pages documentation and the GitHub Privacy Statement for the provider's practices. When you follow an external link, that site's own practices apply.