Privacy-first birthday planning.

Birthday Calendar is designed around local-first import and explicit publishing. Social and contact import flows run in the user's app or browser context wherever possible; the hosted service stores reviewed birthday records, account records, hosted calendar data, and operational logs needed to run the service.

Data handled by the service

The hosted backend may store names, birthday dates, notes, source labels, calendar feed data, account emails, verification/reset records, and settings needed for sync. It does not need raw social passwords or mailbox sessions.

Third-party providers

When enabled, email, OAuth, payment, ad, and AI providers process only the data needed for that integration. Provider credentials are configured through environment variables and are not exposed through public configuration endpoints.

Control

Users can edit or delete birthday records in the app. Hosted calendar publishing only uses the reviewed records the user chooses to publish.