privacy policy.
Reminders uses Firebase for guest and signed-in accounts. Apple sign-in is optional. Reminders contains no advertising or cross-app tracking.
Verbeet UG (haftungsbeschränkt), Bismarckstrasse 116, 20253 Hamburg, Germany, is responsible for BAM Reminders. Contact hello@verbeet.com with privacy questions or requests concerning your data.
Reminders and optional sign-in
Reminders opens without requiring Apple sign-in. Firebase Authentication automatically creates a guest identity. Your reminders are stored in BAM’s Firebase backend under that identity, including while visibly signed out. Firebase’s persistent device cache lets you read and change reminders offline; changes upload when a connection becomes available. The shared Firestore database is located in Frankfurt, Germany. Guest use is not a device-only storage mode.
Stored reminder data includes text, dates, importance, notification preference, completion status, identifiers and change metadata. The app maintains a local widget projection and widget commands; those are associated with the current Firebase identity. Firebase processes authentication, database and messaging requests, including ordinary connection information such as IP addresses.
Sign in with Apple is optional. It adds access to the same BAM account across devices and enables shared assignments. Apple supplies an account identifier and, when you permit it, your name and email address or private relay email address. Guest reminders are preserved when the guest identity is linked, or copied into an existing account when you sign into it. Firebase stores session credentials in the device Keychain. Your BAM username is shared across apps using this Firebase account; private profile information is stored separately from the public username.
Sharing
When you invite someone to a task, its text, date, importance and completion state are shared with that person. Your public BAM username identifies you. Invitees see the task before accepting; accepted participants can update completion, while the creator controls edits and deletion. Shared tasks and invitation responses can be queued offline. Server-rejected changes are rolled back and reported. Username search exposes public usernames, not private names or email addresses. BAM block records restrict interactions between blocked accounts. Blocking stops new invitations and removes the blocked relationship from existing shared reminders; the creator keeps the task. Unblocking does not restore old invitations. Reports store the reporting and reported account identifiers, a reason, time and a snapshot of reported reminder content or the reported public username in a server-only moderation queue. These records support review and action against abuse.
Notifications
The app schedules notifications locally through iOS. Firebase Cloud Messaging device registrations signal account changes so the app can refresh its local schedule when iOS permits background execution. Signals contain an account identifier, not reminder text. The app checks the current identity before fetching data or showing a notification. Device registration records may remain after sign-out until removed as invalid or during account deletion. Device power, notification permissions, connectivity and iOS background restrictions affect delivery.
Retention and deletion
Signing out hides the previous account’s reminders on this device and creates a new guest identity. It does not delete the previous account or its server data. Cached records and pending writes remain associated with their own identity. Deleting individual reminders keeps deletion metadata to prevent stale devices from restoring them.
You can alternatively choose Delete Reminders data. This removes your personal reminders, deletes shared tasks you created and removes you from tasks you were invited to, while keeping your BAM identity, username, private profile and Debts data. Reminders signs out on this device afterward. Deletion markers remain to prevent offline devices from restoring erased content.
Profile provides full BAM account deletion, including deletion of an automatically created guest account. Full deletion removes the Firebase identity and personal reminders, deletes shared reminder tasks you created, and removes your participation from other shared tasks. It also affects other BAM apps using that same Firebase login, including Debts. Existing shared debt records involving other people may remain, with the deleted identity anonymized; a public username reservation and deleted-identity marker are retained to prevent impersonation. Apple users are asked to verify their identity again so their Apple authorization can be revoked. Data already cached on another device can remain there until it reconnects and updates.
Any legacy BAM data still held in a separate backend is not automatically removed by this Firebase deletion. Contact hello@verbeet.com for requests concerning legacy data, access, correction or other privacy questions.
Advertising and tracking
Reminders has no advertising, app usage analytics SDK or cross-app advertising tracking. Firebase processes technical diagnostics and SDK/platform metadata to maintain its services; Firebase Messaging also processes installation identifiers and notification tokens. These service diagnostics are separate from tracking how you use your reminders. BAM does not sell reminder data. This policy will be updated when the app’s data handling changes.