Legal
Terms of Use
This page is a prelaunch draft for bday.is. It is suitable as a working internal baseline, not as final legal text for a public commercial launch. Operator details, billing terms, refund handling, and governing-law provisions still need to be completed.
Service scope
bday.is is intended to help users store birthdays, import birthday data, subscribe to birthday calendars, and manage reminder or send workflows across supported providers.
No guarantee of provider availability
Integrations with messaging, social, and contact providers may change, break, or remain disabled. Availability of imports or autosend paths is dependent on technical feasibility, provider policy, and feature-flag status.
Acceptable use
- Do not use the service to impersonate others.
- Do not use the service to send spam, harassment, or unwanted automated outreach.
- Do not attempt to bypass provider limits, account restrictions, or platform policies.
- Do not share private subscription URLs outside the people or systems that need them.
Accounts and access
The current product architecture uses actor-scoped settings and private calendar tokens. Final authentication, identity, and workspace terms are still under development and should be published before broad availability.
Payments and pricing
The intended pricing model starts with a free tier, then expands to paid coverage tiers based on the number of birthdays managed through reminders or automation. Final billing provider terms and refund policies still need to be published.
Launch-stage limitation of liability
Because the service is prelaunch and integration-heavy, users should expect interruptions, incomplete features, and behavior changes. Before launch, replace this section with final liability caps and jurisdiction-specific language reviewed for your business setup.
Changes
These draft terms will change as the product and company setup become concrete. Keep the draft status explicit until the final operator and billing model are in place.