Privacy
Hilo turns your recurring Google Calendar meetings into a single living canvas per series. AI ingests the context you drop in (transcripts, screenshots, files, links) and writes blocks into that canvas. This page describes what data Hilo collects, why, where it lives, and how to delete it. Hilo is currently a private alpha; if anything is unclear, email cohnen@gmail.com.
What we collect
When you sign in with Google, we receive your Google account profile (a stable Google subject identifier, your email, name, and picture URL) and OAuth tokens that let Hilo read your calendar. The only calendar scope Hilo requests is https://www.googleapis.com/auth/calendar.events.readonly — read-only access to your calendar events. We do not request any other Google scopes.
From your calendar, Hilo reads your recurring meeting series only — title, description, recurrence rule, occurrence times, and the email addresses of attendees. Hilo does not read one-off events, your email, your Drive, or any other Google data.
When you or another attendee adds context to a meeting (drag-and-drop files, pasted transcripts, screenshots, links, or — in future versions — forwarded emails), Hilo stores that content so the AI can summarize it into your canvas. We call these drops.
How we use it
- Calendar data — to discover your recurring meetings and create one canvas per series.
- Attendee list — to determine who can read and write the canvas (current attendees only).
- Drops — sent to Anthropic's Claude API for classification, summarization, and extraction of decisions and action items, which the AI writes back into the canvas as blocks.
- Edit history — every block records the author (a human or the AI) and a timestamp, so collaborators can see who wrote what.
Where it lives
All Hilo data is stored on Cloudflare infrastructure: D1 (SQLite) for users, calendar metadata, and edit history; R2 for binary blobs (file drops, document snapshots); Vectorize for semantic-search embeddings; and Durable Objects for live multiplayer canvas state. OAuth tokens are encrypted at rest with AES-GCM-256 using a key held only by Hilo.
Drops sent to Anthropic for AI processing are subject to Anthropic's commercial terms. Anthropic does not train models on data sent through their commercial API.
Hilo does not sell or share your data with third parties for advertising. The only third parties that touch your data are Google (the source of your calendar) and Anthropic (the AI provider).
Who can see your canvas
Access to a meeting's canvas is the meeting's current Google Calendar attendee list. When you remove an attendee from the calendar invite, they immediately lose access in Hilo — including to past canvases they previously contributed to.
Cookies
Hilo sets two cookies, both first-party and HttpOnly:
hilo_session— a 7-day signed JWT that keeps you logged in (SameSite=Lax, Secure).hilo_oauth_state— a 10-minute anti-CSRF cookie used during Google sign-in.
Hilo does not use analytics or advertising cookies.
Retention and deletion
Your data persists while your account is active. To delete your account and all associated data — D1 rows, R2 blobs, Vectorize embeddings, edit history, OAuth tokens — email cohnen@gmail.com. Full deletion completes within 30 days.
You can revoke Hilo's calendar access at any time at myaccount.google.com/permissions.
Children
Hilo is not intended for users under 16. If you are under 16, please do not sign in.
Changes
If we update this policy, the new version will be posted on this page with a fresh "last updated" date. For material changes, we'll also notify signed-in users.
Contact
Questions, corrections, or deletion requests: cohnen@gmail.com.