MemoryX - Photo Recovery
Privacy Policy
1. Introduction
Welcome to MemoryX - Photo Recovery (“MemoryX”, “we”, “our”, or “the App”).
MemoryX is a photo recovery assistant designed to help users identify and restore accessible photos, videos, and media files stored on their device.
Your privacy is important to us.
This Privacy Policy explains:
- what information MemoryX accesses;
- how information is used;
- what information is collected by third-party services;
- how you can control your data.
By using MemoryX, you agree to the practices described in this Privacy Policy.
2. Our Privacy Commitment
MemoryX is designed with a privacy-first approach.
We do NOT:
- upload your photos or videos to our servers;
- store your personal media files remotely;
- sell your personal information;
- access your files without your permission;
- collect your photo content for advertising purposes;
- require account registration.
Your photos and videos remain on your device.
Scanning and recovery operations are performed locally on your Android device.
3. Information We Access
3.1 Photos and Videos
To provide photo recovery functionality, MemoryX requests access to photos and videos stored on your device.
Depending on your Android version and permission settings, MemoryX may access:
- photos;
- videos;
- media files;
- thumbnails;
- accessible cached media copies;
- items in your device’s system trash (“Recently deleted”) and the date they are scheduled to be permanently deleted;
- user-selected folders.
This access is used only for:
- scanning available media;
- identifying recoverable media candidates;
- displaying previews;
- restoring selected files to your device;
- restoring items from the system trash to their original location, which Android asks you to confirm in a system dialog.
MemoryX does not upload, transmit, or store your photos or videos outside your device.
3.2 Storage Access
When you choose advanced scanning options, MemoryX may request access to user-selected folders through Android’s Storage Access Framework.
This permission allows MemoryX to:
- scan files inside folders you select;
- identify accessible media files;
- help restore selected items.
MemoryX cannot access folders that you have not selected.
3.3 Device Activity and On-Device Counts (for Notifications)
To show reminder notifications at appropriate times, MemoryX may respond to certain on-device events, including:
- when you unlock your device or turn on your screen;
- when your device starts charging;
- when your device finishes restarting;
- when new photos or videos are added to your media library;
- when you go to your home screen, or leave MemoryX (for example, a reminder about scan results you have not restored yet, about 30 seconds after you leave);
- periodic background checks (about every 15 minutes);
- push messages we send.
Except for push messages, reminders are only shown while your screen is on and your device is unlocked. MemoryX does not show reminders between 10 p.m. and 8 a.m. (device time).
When a reminder may be shown, MemoryX counts the photos and videos on your device by category (for example, items in the system trash or camera photos) so the numbers in reminders are accurate. These events and counts are processed on your device only. They are not uploaded, and the counts are kept on your device only until they are refreshed.
3.4 Status Bar Notification (Optional)
MemoryX shows an ongoing notification in your status bar with a summary of media counts (photos and videos found by the latest quick scan, and items in the system trash) and a shortcut to start a scan. It is on by default and appears once notifications are allowed for MemoryX; you can turn it off at any time. The counts are calculated on your device.
To keep this notification available, it runs as an Android foreground service, which Android shows as that same notification. While the notification is turned on and notifications are allowed, MemoryX may start it again when your device restarts, after the App is updated, when a push message arrives, when you dismiss one of our reminder notifications, and about every two hours. It does not collect any additional data.
Tapping it, or a reminder notification, opens MemoryX, where an ad may be shown as the App opens (see Section 6), and then starts a scan.
You can turn it off at any time in MemoryX Settings (it then stops and is not started again) or in your device’s notification settings.
4. How We Use Information
MemoryX uses accessed information only to provide core app functionality.
| Information | Purpose |
|---|---|
| Photo metadata | Display recovery candidates |
| Video metadata | Display video candidates |
| File size | Show recovery information |
| Image dimensions | Display preview information |
| Scan results | Generate recovery history |
| App settings | Remember user preferences |
We do not use your media content for:
- advertising targeting;
- artificial intelligence training;
- profiling;
- selling purposes.
5. Local Data Storage
MemoryX stores limited information locally on your device.
- scan history;
- recovery records;
- app preferences;
- selected settings;
- temporary thumbnail cache.
This information remains on your device, is not uploaded by MemoryX, and can be deleted by clearing app data or using in-app settings.
6. Advertising and Measurement Services
MemoryX uses third-party advertising services to support free access to the App.
We use Google AdMob.
Google AdMob may collect information such as:
- device information;
- advertising identifiers;
- approximate location information;
- app interaction information.
Ads may be shown when you open or return to MemoryX (including from a notification), and at certain points in the App, such as after a scan or recovery finishes. MemoryX does not require you to watch an ad to scan or recover your files.
This information is used for displaying advertisements, measuring advertising performance, preventing fraud, and providing personalized or non-personalized ads depending on your choices and applicable regulations.
Where required (for example in the EEA, the UK and Switzerland), MemoryX shows a consent message from Google’s User Messaging Platform when you first open the App. Your choices there decide whether ads may be requested and whether they may be personalized; you can change them at any time in MemoryX Settings > Privacy options. These choices mainly concern advertising; see Section 7 for how they relate to analytics.
MemoryX does not provide your photos, videos, or recovered files to advertising partners.
MemoryX uses MagicianReach, our own SDK for managing ads and notifications. It collects device information (such as device model, operating system version, language and time zone), an app-instance identifier, and ad events and ad revenue information. We use this data for ad delivery, measurement and fraud prevention. It is stored on servers we operate in Singapore, hosted by Alibaba Cloud as our service provider, and is not sold or shared for other companies’ own purposes.
We also use Adjust, a mobile measurement provider, to attribute installs and app events to the campaign they came from. Adjust may collect device and app identifiers (such as the Google Advertising ID), device and network information, and app event data. We use this only for measuring marketing performance and preventing install fraud.
To understand how the App was installed (for example, from an ad campaign or organically), MemoryX also reads Google Play Install Referrer information. We use this only to adjust how often ads and reminders are shown.
For more information:
7. Analytics Services
MemoryX may use analytics services such as Firebase Analytics and Firebase Crashlytics.
Firebase Analytics helps us understand app performance, feature usage, and user interaction patterns. Firebase Crashlytics helps us detect and diagnose app crashes so we can fix them.
Analytics and crash data may include app version, device information, operating system information, an app-instance identifier, app events, app usage statistics, and technical crash/error reports (e.g. stack traces).
Analytics events may include whether a reminder was triggered, shown or skipped (and why), and interactions with in-app prompts. We also record whether the App was installed organically or from an ad campaign as an analytics property. To deliver push messages, Firebase Cloud Messaging uses a device token.
Analytics and your consent choices. Firebase Analytics collects analytics data from the first time you open the App, including before you have responded to any consent message. It uses an app-instance identifier that Firebase stores on your device, so that events can be counted per App installation; it is not linked to your name, email address or any account. By default, MemoryX sets Google Consent Mode for Firebase to “granted” (analytics and advertising storage, and the related advertising signals), so Firebase may also use this data for advertising measurement, for example to see which of our ad campaigns led to an install. Where a consent message is shown (for example in the EEA, the UK and Switzerland), your choices there, and later in MemoryX Settings > Privacy options, mainly affect advertising: whether ads may be requested and whether they may be personalized (see Section 6). In some cases, for example if you make or change your choice some time after the App has started, Google’s consent tools may also pass your choice on to Firebase Analytics, which can then limit how analytics data is collected or used. Versions of MemoryX without ads do not show a consent message. To reset the analytics identifier, clear the App’s data or uninstall MemoryX.
Crash reports (Firebase Crashlytics) are collected regardless of your consent choices, only to detect and fix crashes.
Remote configuration. MemoryX uses Firebase Remote Config to receive app settings from us, such as how often ads and reminders are shown. The App fetches these settings when it starts and when it returns to the foreground, including before you have responded to a consent message. The request is made by Firebase and includes technical information such as an app-instance identifier, app version, device and operating system information, and whether the App was installed organically or from an ad campaign, so that we can send the right settings. It does not include your photos, videos or file names.
We do not send photos, videos, file names, file paths, or personal media content.
8. Google Play Data Safety
This section summarizes how MemoryX aligns with the Google Play Data safety form.
| Data type | Collected? | Purpose | Shared? |
|---|---|---|---|
| Photos and videos | Accessed on-device only (not uploaded by MemoryX) | App functionality: scan, preview, restore | No |
| Device or other IDs | Yes (via Google AdMob, Adjust, MagicianReach and Firebase) | Advertising and advertising measurement; analytics (Firebase app-instance identifier, from the first launch) | Yes, with Google AdMob and Adjust |
| App interactions | Yes (via Firebase Analytics) | Analytics | Yes, with Firebase Analytics (events linked to an app-instance identifier) |
| Crash logs / diagnostics | Yes (via Firebase Crashlytics) | Analytics: detecting and fixing app crashes | Yes, with Firebase Crashlytics |
| Device activity (unlock, screen on, charging, restart, media library changes, going to the home screen or leaving the App) | Observed on-device only, not stored or transmitted | App functionality: timing local reminder notifications | No |
Photos and videos are processed locally and ephemerally for recovery features. MemoryX does not upload your media to MemoryX servers.
See also the in-app Data Safety screen and the Google Play Data safety declaration for this app.
9. Device Permissions
Photos and Videos Permission — To scan and identify accessible media files for recovery.
Storage Permission — To scan user-selected folders and restore selected files.
Notification Permission (Optional) — To show reminder notifications and the optional status bar notification about MemoryX’s recovery features. If you decline, MemoryX may ask again when you open the home or results screen, at most three times a day, first explaining why; if Android no longer shows the request, MemoryX offers to open your notification settings instead.
Foreground Service (Special Use) — To keep the status bar notification running (see Section 3.4). The notification is on by default; the service is only used while it is turned on and notifications are allowed, and stops when you turn the notification off in MemoryX Settings.
You may deny permissions at any time. Without required permissions, some recovery features may not function.
10. Data Sharing
MemoryX does not sell or share your personal information.
We may share limited technical information with service providers only when necessary for advertising, advertising measurement (Google AdMob, Adjust), analytics, crash reporting, and app stability improvements.
Third-party services operate according to their own privacy policies. Your photos and videos are not shared.
11. Children’s Privacy
MemoryX is not specifically designed for children under 13.
We do not knowingly collect personal information from children.
If you believe a child has provided personal information, please contact us and we will take appropriate action.
12. Data Security
We use reasonable technical measures to protect the App and user information, including local processing of media scanning, limiting collected analytics information, and avoiding unnecessary access to personal data.
However, no electronic storage method can guarantee absolute security.
13. Your Rights and Choices
You can:
- deny permissions;
- change permissions in Android Settings;
- clear app data;
- uninstall MemoryX;
- disable personalized advertising according to your device settings;
- change your consent choices (mainly whether ads may be requested and personalized) in MemoryX Settings > Privacy options, where a consent message is required (for example in the EEA, the UK and Switzerland); these choices mainly concern advertising and do not affect crash reporting (see Section 7 for analytics);
- reset the analytics identifier by clearing app data or uninstalling MemoryX;
- turn off the status bar notification in MemoryX Settings.
14. Third-Party Links
MemoryX may contain links to third-party websites or services.
We are not responsible for the privacy practices of third-party services. Please review their privacy policies separately.
15. Changes to This Privacy Policy
We may update this Privacy Policy from time to time.
When changes are made, the updated version will be posted on this page and the revision date will be updated.
Your continued use of MemoryX means you accept the updated Privacy Policy.
16. Contact Us
Email: [email protected]
Developer: MemoryX Team