Privacy Policy

Status

bday.is is currently being developed as a birthday reminder and birthday automation product. The service is not yet in general paid availability, and the production feature set remains behind flags.

What data the product is designed to handle

• Contact names and birthday dates.
• Communication handles such as WhatsApp, Instagram, Messenger, and Slack identifiers.
• Import metadata from sources such as iOS Contacts, Google Contacts, Facebook, X, and GitHub.
• Actor settings such as time zone and private calendar subscription tokens.

Privacy posture

The product is designed to minimize exposure of sensitive birthday details. Public and subscribed birthday calendar feeds hide birth years. Private subscription links are tokenized and can be rotated.

New integrations and autosend paths are intended to launch behind feature flags so risky or unfinished behavior does not become active for production users by accident.

How imported data should be treated

Imports are intended to be reviewable before they are applied into a durable contact list. The current backend already stores import runs separately from the primary contacts namespace so imported data can be previewed and deduplicated.

Retention and deletion

Final retention rules are not published yet. Before paid launch, this page should be updated with concrete retention windows, deletion procedures, and the exact way backups are handled.

Third-party services

The deployed stack currently uses hosted infrastructure providers. Final disclosure of all subprocessors, regions, and billing or messaging providers still needs to be completed before launch.

Your responsibilities before launch

If you operate bday.is commercially, complete this document with the correct legal operator identity, contact address, support email, subprocessor list, and region-specific rights language before collecting production customer data.