Privacy Policy
App: DKReminder
Last updated: August 13, 2026
In brief
DKReminder is a local-first reminder app. You can create and use local reminders without an account. An optional Exchange account uses Google Firebase so that users can request permission and send selected reminders to one another. We do not sell personal data, and the app does not include advertising or analytics SDKs.
Data stored locally
Reminders, reminder settings, trigger history, and details you add to scenarios such as meetings and deadlines are stored in the app’s internal database on your device.
You control this local data and can use the core reminder functions without signing in. Except for data that you explicitly send through Exchange, local reminder content is not uploaded to the DKReminder cloud service.
Optional Exchange account
Exchange requires an optional account created with an email address and password or with Google Sign-In. Firebase processes account details such as your display name, email address, user ID, sign-in provider, verification state, and technical authentication records. DKReminder also stores a private email lookup used to find the intended user, installation and push-notification identifiers, app and exchange-protocol versions, and records needed for abuse prevention and reliable delivery.
A permission to send reminders is directional and must be approved by the recipient. Requesting permission and sending new reminders require Pro. Signing in, approving or revoking permissions, receiving a reminder, and creating a local copy from it do not require Pro.
Reminder exchange
When you explicitly choose to send a reminder, Firebase stores the complete reminder snapshot needed for the recipient to review it: title, description, schedule, priority, alert behavior, recurrence settings, and any meeting or deadline details you included. The sender and recipient also keep separate journal entries with delivery status and timestamps. These journals are not a shared reminder and are not synchronized with one another.
The recipient may reject the incoming item or open a prefilled editor and save an independent local reminder. After sending, the sender cannot control the recipient’s copy and does not learn whether the recipient opened, rejected, imported, changed, completed, or deleted it. Deleting a sent or received journal entry affects only that user’s own journal.
Push notifications do not contain the reminder title, description, or schedule. They contain technical identifiers needed to fetch the item and may include the sender’s display name. Firebase Cloud Messaging is a delivery signal, not the source of truth for the reminder.
Selected contacts and sensitive text
When you choose a meeting participant through Android’s system contact picker, DKReminder reads only the display name of the contact you selected. The app does not request unrestricted access to your address book. If you then send that reminder through Exchange, the selected display name is sent as part of the meeting details.
Reminder text is user-provided and may contain private or health-related information, for example a medication name or medical appointment. DKReminder treats it as ordinary reminder content and uploads it only when you explicitly send that reminder. DKReminder is not a medical device and does not provide diagnosis or treatment advice.
Firebase and other Google services
DKReminder uses Firebase Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging, Firebase Installations, and App Check with Play Integrity. Google may process device or app identifiers, IP address, user-agent and integrity information as needed to provide, secure, and protect these services. Data is encrypted in transit and protected at rest by the service provider, but Exchange is not end-to-end encrypted.
Firebase acts as a service provider for DKReminder. Google’s handling of data is also governed by the Google Privacy Policy and Firebase Privacy and Security documentation. DKReminder does not use advertising networks, analytics SDKs, or Crashlytics.
Google Play Billing
DKReminder uses Google Play Billing to offer and verify the annual DKReminder Pro subscription. Google Play may process Google Account, purchase, and payment information. The app receives technical product, purchase token, and purchase-status information needed to provide Pro access. DKReminder does not receive payment card details, and reminder content is not sent to Google Play Billing.
Android backup and device transfer
Depending on your Android and Google Account backup settings, Android may include allowed DKReminder data in a system backup or transfer it directly to another device. This can include local reminders, their metadata and history, onboarding state, and the initial Pro access start date. These operations are performed by Android’s backup and device-transfer services, not by the DKReminder Exchange service.
Paid subscription confirmation, the local billing cache, account credentials, cloud authentication tokens, and debug testing settings are excluded from Android backup. You can manage system backup settings on your device.
Manual backup and restore
If you use DKReminder’s Export data feature, the app creates a backup file in the location you choose. You are responsible for storing, sharing, and deleting that file. When you import a backup, its data replaces the current data in the app. The file includes the initial Pro access start date so that restoring it does not create a new 30-day period, but it does not contain paid subscription status, the billing cache, account credentials, cloud authentication tokens, or payment information.
Permissions and their purpose
- Notifications — to show reminders at the scheduled time.
- Alarms & reminders (exact alarms) — to trigger reminders at the selected time.
- Full-screen alerts — to display a prominent reminder alert, including on the lock screen when permitted by Android.
- Run after device restart — to restore scheduled reminders after the device restarts.
- Foreground media playback — to play the selected reminder sound reliably while an alert is active.
Exchange also uses internet access and push notifications for account and delivery operations. The system contact picker grants access only to the contact the user explicitly selects; DKReminder does not request broad contact permission.
Storage and deletion
You can delete local reminders and journal entries in the app. Cloud Exchange records do not have a fixed automatic expiration in the current version and remain until you delete the relevant entry or delete your Exchange account, subject to the independent-copy rule below.
To delete your Exchange account in the app, open Settings → Reminder exchange account → Delete account, re-authenticate, and confirm permanent deletion. This removes your Firebase Authentication account, profile and private email index, registered devices and push tokens, permissions, your own sent and inbox journals, and related backend operation records. A public request method and full details are available on the Account deletion page.
A reminder already delivered to another user’s inbox, or an independent local reminder that another user created from it, is controlled by that user and is not removed when you delete your account. Local data on your device, Android system backups, and manual backup files must be deleted separately. Deleting an Exchange account does not cancel a Google Play subscription.
Children’s privacy
DKReminder is intended for users aged 18 and over. The service is not directed to children, and we do not knowingly collect children’s personal data.
Changes to this policy
We may update this Privacy Policy when the app’s features or data practices change. The current revision date is shown at the top of this page.
Contact
Developer: Kryzhanovskyi Dmytro Volodymyrovych
Privacy questions: dkreminder.support@gmail.com
Account deletion: instructions and request method