Creative and strategic studio for brands built with intention. We design brand foundations, creative systems, and storytelling that endure.
HoloCalendar · Privacy Policy
HoloCalendar
Privacy Policy.
HoloCalendar is made by House of Rubi LLC (“House of Rubi,” “we”). This page explains what data HoloCalendar accesses, where it goes, and how you control it — across the desktop app (macOS, Windows, Linux) and the local bridge it runs.
Last updated · October 22, 2026
0
House of Rubi servers involved
100%
Of your data stays on your device
3
Minimal Google scopes requested
The short version
Your data stays between you and Google.
HoloCalendar runs on your own computer. It talks directly to Google and, if you turn on voice, to Google’s Gemini API — never to a House of Rubi server. We don’t operate any backend for HoloCalendar, and we don’t collect, see, or store your calendar, tasks, or voice data ourselves.
01 — Access
What HoloCalendar accesses, and why
Each item below shows why HoloCalendar needs it and exactly where it travels.
Google Calendar
Why: To display your calendars on the wallpaper and let Holo add, move, or cancel events by voice.
Where it goes: Directly between your computer and Google's servers.
Google Tasks
Why: To display and update your task lists.
Where it goes: Directly between your computer and Google's servers.
Your voice audio
Why: Only if you enable Holo — so Holo can understand spoken commands.
Where it goes: Directly between your computer and Google's Gemini API.
Approximate location
Why: The city or coordinates you enter, used to show local weather.
Where it goes: Sent to Open-Meteo, a weather API that does not require an account.
Google OAuth scopes
Only what's needed. Nothing more.
- calendar.calendarlist.readonly — see which calendars you have
- calendar.events — read, add, move, and cancel events
- tasks — read, add, and complete tasks
We do not request access to Gmail, Drive, Contacts, or any other Google data.
02 — Our commitments
What we don't do
- We don't run analytics, telemetry, or crash reporting that sends data to House of Rubi.
- We don't have a server that your calendar, tasks, or voice data passes through — the bridge (server.py) runs on your own computer and only talks to Google and Open-Meteo directly.
- We don't sell or share your data, because we never receive it.
- Hands-free "Hey Holo" listening (macOS) uses Apple's on-device speech recognition. Nothing is sent to Gemini until the wake phrase is heard, or while you're actively talking to Holo.
03 — Storage
Where your data is stored
Everything HoloCalendar stores lives on your own computer.
Credentials
Google and Gemini credentials are stored in the macOS Keychain, the Linux Secret Service (keyring), or encrypted with Windows DPAPI. Never written to a plain file.
Settings & logs
Stored locally — ~/Library/Application Support/HoloCalendar on macOS, %APPDATA%\HoloCalendar on Windows, ~/.local/share/HoloCalendar on Linux.
The local bridge
Listens only on 127.0.0.1 (your own machine) and is not reachable from the internet or other devices on your network.
04 — Your controls
You're always in control
Disconnect Google
Remove HoloCalendar's access at myaccount.google.com/permissions, then delete the app's data folder.
Remove your Gemini key
Delete it from the app's voice settings, or delete the data folder.
Undo anything
Every voice edit has an Undo (button, ⌘Z, or say "undo that"). Holo always asks before deleting an event.
05 — Third parties
Services HoloCalendar relies on
Calendar, Tasks, and Gemini APIs — governed by Google's Privacy Policy.
Open-Meteo
Free weather data, no account required — governed by Open-Meteo's terms.
HoloCalendar is not affiliated with Google. Google Calendar, Google Tasks, and Gemini are trademarks of Google LLC.
06 — Updates
Changes to this policy
If this policy changes, we’ll update the “Last updated” date above. Material changes will be noted in the project’s release notes on GitHub.
Contact
Questions about this policy or your data?
Write to us any time — we reply within 24 hours.