Your data stays yours
Privacy Policy
This policy describes the data handling of the Bday Android app and this legal website. The app is designed to work locally on your device.
Last updated: 22 November 2026
1. Controller and contact
The controller responsible for this website and privacy inquiries is:
Lorenz MoserWalderseestraße 19
72805 Lichtenstein
Germany
Email: lorenz.moser.bw@gmail.com
2. Data stored in Bday
Bday stores names, birthdays, optional birth years, groups, gift ideas, reminder rules, reminder-delivery status, and app settings in private storage on your device. The database is used to manage entries, display home-screen widgets, and schedule local Android reminders.
Settings such as appearance, language, reminder time, and group defaults are stored locally in the app's preferences. No account is created and the app has no internet permission.
3. Contacts and file imports
Contact import is optional and requires the Android contact permission. Bday reads contact names and birthdays to create an import preview and stores only the entries you select. You can revoke the permission in Android settings at any time.
Bday reads an ICS, VCF, or CSV file only after you select it in Android's file picker. Files are limited to 5 MB. Unselected and duplicate entries are not imported or saved.
4. Notifications and widgets
Bday uses local Android notifications and alarms for reminders, including after device restarts and relevant clock or time-zone changes. Notification access is requested separately on Android versions that require it. You can disable notifications in Android settings.
Widgets read local birthday data to display upcoming birthdays on the home screen. Android may show notification and widget content outside the app, depending on your device settings.
5. Exports, sharing, and calendar access
Exported ICS, VCF, and CSV files contain selected names and birthdays. CSV exports can also contain groups. They are not complete backups: gift ideas, reminder rules, and app settings are not included.
When you save a file, share it, or add a birthday to a calendar, Android passes the relevant data to the destination or app you choose. That destination processes the data under its own privacy terms. Files saved or shared outside Bday remain after the app is uninstalled.
For sharing, Bday creates a temporary file in private app cache. Temporary share directories older than 24 hours are removed the next time you share.
6. Retention and deletion
App data remains on your device until you delete it in Bday or uninstall the app. You can view, edit, and delete individual birthdays, associated gift ideas, and reminders in Bday.
Android cloud backups and device transfers are disabled for Bday. Therefore, local app data does not automatically transfer to a new device. Deleting or uninstalling the app does not delete exports, shared copies, or calendar entries created outside Bday.
7. Network access and third parties
The Android app does not request internet access and contains no account system, advertising, analytics, crash-reporting, or remote tracking service. The developer does not receive app data. Android, your chosen file apps, sharing targets, and calendar provider process any data you deliberately hand to them under their own terms.
8. This website
This website serves static HTML and CSS and uses no cookies, analytics, external fonts, embedded third-party content, or tracking scripts. The hosting server must technically process connection data required to deliver the requested page. The Caddy gateway configuration does not enable separate access logging for this site; other hosting or network logs may depend on the infrastructure provider's operation.
If you contact the operator by email, the information in your message is received and used to handle your inquiry. Do not include more personal data than necessary.
9. Your choices and rights
You can manage or delete data stored in Bday directly in the app and can revoke contact or notification permission in Android settings. For privacy questions about this app or website, contact the operator using the details above. You may also contact your competent data protection supervisory authority.