Plain English, local-first, and written to match the app's actual Data Safety behavior.
Last updated: 29 September 2026
Recall50+ is designed to work locally first. You do not need a Recall50+ account for normal use.
We do not run a custom Recall50+ server for your memories. Most data stays on your device unless you choose an optional Google backup or use a Google service that the app needs for a feature.
If you use optional Google Drive backup, your Google account or email may be used only for that backup or restore flow.
Recall50+ stores your memories in the app on your device by default. That can include:
Recall50+ asks for only the permissions needed to make the app work.
Location
Used to save places, guide you back to a memory, calculate distance, and support parking and proximity features.
Camera, photos, media, and files
Used to attach photos, receipts, documents, and scans to a memory.
Microphone
Used to record voice notes.
Notifications
Used to deliver reminder alerts.
Notification access / listener
Used for the optional notification-saving feature after explicit in-app disclosure and Android permission approval.
Physical activity / activity recognition
Used only for optional parking and walking-away detection where the user turns that feature on.
Exact alarms / reminder timing
Used to keep reminder timing accurate where Android allows exact scheduling.
Biometric / device credential unlock
Used to unlock private memories; the app does not store biometric templates.
Notification saving is optional. It only starts after we explain it in the app and you approve the Android system permission.
If you turn it on, the app may see notification text, the source app name, timestamp, and related metadata so it can save useful notification-based memories.
Recall50+ tries to filter or ignore sensitive notifications where possible, such as OTPs and banking alerts, but filtering is not perfect.
You can choose Not now in the app, and you can disable notification access later in Android settings.
Google Drive backup is optional and user-initiated.
When you choose it, Recall50+ uses your own Google account and Google Drive app-data storage.
The backup may include saved memories and attachments, depending on the backup option you select.
Where implemented, the backup payload is encrypted before upload, including passcode-derived AES-GCM protection for encrypted backups.
Google receives the data needed to provide Drive and Sign-In services. You can delete Drive backups from Google Drive or app data, or clear app data on the device.
Recall50+ uses the following Google services and no others in the current audit:
We found no Firebase SDKs, no ads SDKs, no analytics SDKs, and no custom Recall50+ backend for user memories. We do not sell user data.
Recall50+ uses Google Play Billing to handle Plus and lifetime purchases.
Purchase and subscription status are used to unlock Plus features in the app.
Subscription management, cancellations, and refunds happen through Google Play, not through a Recall50+ account.
You can delete individual memories, reminders, attachments, and notification memories inside the app.
You can disable permissions in Android Settings at any time.
You can clear app data to wipe the local app data on your device.
You can delete Drive backups from Google Drive or app data, and you can cancel subscriptions in Google Play.
Recall50+ stores data in Android app-private storage.
Encrypted local media is used where implemented, and temporary backup files are cleaned up where implemented.
Encrypted Google Drive backups use a passcode-derived AES-GCM key where the encrypted backup feature is enabled.
Biometric or device-credential unlock is handled by Android. The app does not receive or store your biometric template.
Recall50+ does not rely on a custom backend for your memories. Android auto-backup is not the supported backup path; optional Google Drive backup is.
Questions about this policy? Contact us at info@voxcor.app or through voxcor.app/contact.
This policy may change over time. If it does, we will update this page.