Calveil is designed to share availability without sharing the event behind it. It processes Google Calendar data only to create and maintain the calendar links you configure.
Data we store
We store your Calveil identity, connected Google authorization, encrypted provider tokens, owned-calendar metadata, calendar-link settings, opaque synchronization state, managed-event mappings, and privacy-safe operational activity.
Data we deliberately do not copy
Mirror events never include attendees, descriptions, locations, conference details, attachments, reminders, organizer details, or links back to the source. Raw Google response bodies are processed in memory and are not retained. While a bounded synchronization run is in progress, Calveil may temporarily retain one normalized source event, including its title, inside an encrypted continuation cursor. That cursor is removed when the run completes, is abandoned, reaches terminal failure, or the account is deleted.
Event titles
Fixed private text is the default. If you explicitly choose a template containing {title}, the source title is used only for that configured destination and may be temporarily encrypted for a queued write or an in-progress synchronization continuation.
Security and retention
OAuth tokens and cursor data are encrypted with AES-GCM. Session tokens are stored only as hashes. Activity metadata and mirror tombstones are retained for limited operational periods described in the product.
Your choices
You can pause or delete links, disconnect Google accounts, revoke access, and delete your Calveil account. Cleanup is attempted before revocation so managed future events can be handled safely.
Contact
A production support and privacy contact must be published before public launch.