Privacy Policy
Summary
Remember is designed so your notes and reminders stay on your device. The app does not require an account for normal use. The developer does not collect analytics, run ads, or send your data to any server not described in this policy.
Data stored on your device
Your content — notes, lists, checklists, file attachments, reminder schedules, tags, and settings — is stored locally in app-private storage on your device. Nothing is sent to the developer's servers.
Android automatic backup
Android automatically backs up most app data through Google's backup service (Google One Backup) and during device-to-device transfers, depending on your Android version and Google account settings. This means your notes, reminders, tags, and app settings may be included in your Android backup without any action on your part.
The following are excluded from Android's automatic backup: images attached to notes, other file attachments, and backup ZIP files you export manually.
Automatic backup is handled entirely by Android and Google; the developer does not control what Google does with that data. You can turn off Android's automatic backup at any time in Android Settings → Google → Backup.
Manual backup and import
You can export app data to a folder you choose, including cloud storage connected to your device. That data is handled by Android and the storage provider you select, not sent to a server run by the developer.
Google user data and Google Tasks import
This section describes Remember's optional Google Tasks import. Google access is used only when you choose to connect Google Tasks.
Data Accessed
When you choose Connect Google, Remember asks Google for these OAuth permissions:
- Google Tasks read-only access (
https://www.googleapis.com/auth/tasks.readonly) - used to read your Google Tasks lists and tasks. - Email address (
https://www.googleapis.com/auth/userinfo.email) - used to identify the Google account you selected and show the connected account in the app.
With that access, Remember reads only the Google Tasks data needed for the import screen: task list IDs and titles, task IDs, task titles, notes or descriptions, due dates, completed status and completion timestamps, parent or subtask relationships, ordering, and hidden or deleted status. Remember does not request access to Gmail, Google Drive, Google Calendar, Google Contacts, Google Photos, or any other Google service. Remember never requests permission to create, edit, or delete anything in Google Tasks.
Data Usage
Google Tasks data is used only to show your task lists in the import screen, let you search, filter, and select tasks, and create or update local Remember notes and lists from the tasks you choose to import. Task titles become note titles or checklist text, task notes become note bodies, due dates become Remember reminders, completed status becomes Remember's done state, and task list titles may become tags. Remember's usage of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Remember does not write changes back to Google Tasks. The app does not monitor Google Tasks in the background, sync continuously, or access your Google Tasks unless you open the import flow and connect, refresh, or import.
Data Sharing
The developer does not sell Google user data, share it with advertisers, or send it to analytics, telemetry, crash-reporting, or developer-operated servers. Remember makes network calls only to Google services needed for the import flow: Google Identity Services for authorization, the Google Tasks API to read task lists and tasks, Google's userinfo endpoint to read the selected account email, and Google's token revocation endpoint if disconnect requires token revocation.
If you export a Remember backup to a folder you choose, including a cloud provider such as Google Drive, the exported notes in that backup are handled by Android and the storage provider you selected. Android automatic backup may also include local Remember data depending on your device and Google account settings. Those backups are controlled by Android and Google, not by the developer.
Data Storage & Protection
Your Google password is never seen or stored by Remember. OAuth access tokens are obtained through Google Play Services / Google Identity Services and kept only in app memory while the import flow needs them; Remember does not store OAuth access tokens in its database or preferences.
Remember stores imported tasks as local notes, lists, reminders, tags, and completion state in its on-device Room database. It also stores the last connected account email and a small mapping of Google task IDs to Remember note IDs in app-private Android DataStore so it can show the connected account and avoid duplicate imports. This local app data is protected by Android's app sandbox. If you enable app lock, access to the app UI is additionally protected by your device's existing unlock method.
Data Retention & Deletion
Google Tasks data loaded for preview is retained only in the active import screen session unless you import it. Imported Google Tasks data stays in Remember until you delete it. Deleting a note or list moves it to Trash; you can delete it forever immediately or empty Trash manually. Trashed notes are automatically deleted after 30 days.
You can disconnect Google Tasks inside the import screen. Disconnect revokes or clears the Google authorization where possible and removes the locally stored connected account email and import mapping for that source. Disconnecting does not delete notes or lists you already imported; delete those inside Remember if you want to remove the imported content.
You can also revoke Remember's Google access from your Google Account settings at any time. To remove local data, delete the imported notes or lists, empty Trash or delete forever, clear the app's storage, or uninstall the app. To remove data from Android automatic backup, manage or delete your Android backup from your device or Google account settings. The developer does not keep a server-side copy of your Google user data, so there is no server-side Google data for the developer to delete unless you separately choose to send information in a support request.
Permissions
Granted automatically at install
These permissions are granted when you install the app. Android does not show a separate approval prompt for them:
- Internet access — used for three purposes: checking for app updates, fetching the release changelog from GitHub, and the optional Google Tasks import. No other network connections are made.
- Receive boot completed — allows the app to restore your reminder notifications after the device restarts, so active reminders are not silently lost.
Requested in a system prompt
Android shows a dialog before granting these:
- Notifications — to show reminder alerts, an optional persistent reminder summary in the notification shade, and widget refresh signals.
- Battery optimization exemption — when you enable "Reliable Reminders," the app shows a system dialog asking whether to exempt Remember from battery optimization. Once granted, Android allows the app to run unrestricted in the background so reminder delivery is not deferred during Doze mode. This matters most on devices from manufacturers like Samsung or Xiaomi that aggressively restrict background apps.
- Install unknown apps (GitHub release only) — allows the app to install a downloaded APK update without leaving the app. Only present in the GitHub build; the Play Store build uses Google Play's update mechanism instead.
Exact alarm scheduling
How this works depends on where you installed the app from:
- GitHub / APK release — the app is granted exact alarm access automatically at install (
USE_EXACT_ALARM). No action is required from you and this cannot be revoked. - Google Play — exact alarm access (
SCHEDULE_EXACT_ALARM) is user-grantable on Android 12 and above. Some OEMs grant it by default; others do not. If it is not already granted, enabling "Reliable Reminders" in Settings navigates you to the relevant Android settings screen. Full reliable reminder delivery on Play Store requires both exact alarm access and the battery optimization exemption above.
Reminders you mark as High importance are exempt from both of the above: they use Android's alarm clock API (setAlarmClock), which is always precise and always Doze-exempt regardless of which flavor you installed or what you have granted.
Optional: app lock
If you turn on app lock, Remember uses your device's existing unlock method — fingerprint, face, or device PIN — to protect access to the app. The developer never receives any of this; authentication is handled entirely by Android.
Diagnostic log
The app maintains a local diagnostic log on your device. It records technical events — errors, crashes, permission states, notification channel settings, Android version, and device model. It never contains the content of your notes, reminder titles, or any personal data you have entered.
This log is never sent anywhere automatically. It is only shared if you choose to tap the bug report button in Settings and then explicitly share the file. The log is capped at 256 KB and older entries are trimmed automatically.
No analytics or tracking
The app does not include analytics, advertising, crash-reporting, or telemetry SDKs. The developer does not receive information about how you use the app.
Children
The app is not directed at children under 13, and the developer does not operate any service that collects personal information from children.
Changes
This policy may be updated from time to time. The latest version will be published on this page.
Contact
For privacy questions about Remember, including deletion requests for information you voluntarily sent in a support request, use the GitHub project or the app store listing where you installed the app from.