This Privacy Policy explains how the Backup Manager Android application ("the App", "we", "us") handles information. Please read it before installing or using the App. By using the App you agree to the practices described here.
The App accesses the following categories of on-device data, strictly to perform the backup, restore and delete operations that you start from the App's user interface:
| Data category | Why it is accessed | Where it goes |
|---|---|---|
| SMS / MMS messages (sender, recipient, body, timestamps, read/sent status) | To export messages into a backup file, to restore them back to the messaging database, and to delete them when you ask | Written to a backup file (XML) in your chosen local folder. Uploaded to your Google Drive only if you upload it yourself. |
| Contacts (names, phone numbers, e-mail addresses and other contact fields) | To export contacts to a vCard file, to display the contact list in the App, and to restore or delete contacts on request | Written to a vCard (.vcf) backup file in your chosen local folder. Restore is handed to the Android system's own vCard importer. |
| Call logs (numbers, call type, date, duration) | To export, restore and delete call history entries | Written to a backup file in your chosen local folder. |
| Calendar (events, reminders, attendees, calendar account name/type) | To export calendar entries, and to restore or clear events, reminders and attendees on request | Written to a backup file in your chosen local folder. |
| Installed applications (package names, app names, versions, icons, APK files) | To list your installed apps, copy their installation files (APKs) into a backup folder, reinstall them from backup, and uninstall them on request | APK copies are written to the apps sub-folder of your chosen local backup folder. |
| Google account e-mail address (only if you use the Google Drive feature) | To identify the account you signed in with and to authorise uploads to your own Drive | Handled by Google Sign-In on your device; a "signed in" flag is stored in the App's local preferences. |
| App settings (backup folder path, ad-removal purchase state, rate-dialog counters) | To remember your preferences between launches | Stored in the App's private preferences on the device only. |
All processing of the data above happens locally on your device. None of it is transmitted to MyMobileIdeaStudio or to any server operated by us.
By default, backups are written to a folder named BackupManagerData in your device's shared storage.
You can change this location in the App's Settings screen. These files stay on your device and remain under your
control — you can open, copy, move, share or delete them with any file manager. Uninstalling the App does not
automatically erase backup files you created; delete them yourself if you no longer want them.
The Google Drive screen is entirely optional. If you use it:
drive.file permission scope. This scope is
deliberately narrow: it lets the App see and manage only the files it creates or that you explicitly
open with it — it does not give the App access to the rest of your Drive.Data stored in Google Drive is subject to Google's Privacy Policy.
| Permission | Purpose |
|---|---|
READ_SMS, WRITE_SMS, RECEIVE_SMS/MMS handling |
Read messages to back them up, write them back when restoring, and delete them when you ask. |
READ_CONTACTS, WRITE_CONTACTS |
Back up, restore and delete contacts. |
READ_CALL_LOG, WRITE_CALL_LOG |
Back up, restore and delete call history. |
READ_CALENDAR, WRITE_CALENDAR |
Back up, restore and clear calendar events, reminders and attendees. |
READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE |
Create and read the backup folder and the backup files inside it. |
QUERY_ALL_PACKAGES, GET_PACKAGE_SIZE |
Show the list of apps installed on the device so you can select which ones to back up. |
REQUEST_INSTALL_PACKAGES, REQUEST_DELETE_PACKAGES |
Ask Android to reinstall an app from a backed-up APK, or to uninstall an app you selected. The system always shows its own confirmation dialog; the App cannot install or remove anything silently. |
INTERNET, ACCESS_NETWORK_STATE |
Google Drive upload/download, advertising, crash reporting, and checking whether a connection is available. |
GET_ACCOUNTS |
Google Sign-In for the optional Drive feature. |
READ_PHONE_STATE, CALL_PHONE |
Supporting telephony functions used by the SMS and call-log features. |
com.android.vending.BILLING |
The optional one-time in-app purchase that removes advertising. |
Permissions are requested at runtime, and you may decline any of them. Declining a permission only disables the matching feature; the rest of the App continues to work.
Since Android 4.4, only the device's default SMS app may write to or delete from the message database.
For that reason the App can ask to be set as your default SMS app, and it declares the message-related components
(SMS_DELIVER, WAP_PUSH_DELIVER, "respond via message") that Android requires of any default
SMS app.
This role is used solely to let you restore or delete your own messages. The App does not read your messages for advertising, profiling or analytics, does not send messages on your behalf, and does not transmit message content anywhere. You can set your previous messaging app back as the default at any time in Android Settings, and you can use the backup (read-only) features without granting this role at all.
The App integrates the following third-party SDKs and services. Each one collects data under its own privacy policy, and we encourage you to read them:
| Service | Used for | Typical data it processes | Policy |
|---|---|---|---|
| Google AdMob | Displaying banner, interstitial and rewarded-video ads in the free version | Advertising identifier, IP address, device and app information, ad interactions | Google Ads policy |
| Meta Audience Network | Displaying banner and interstitial ads in the free version | Advertising identifier, IP address, device and app information, ad interactions | Meta Privacy Policy |
| Firebase Crashlytics | Diagnosing crashes and stability problems | Crash stack traces, device model, OS version, app version, an app-generated installation identifier | Firebase Privacy |
| Google Analytics for Firebase | Aggregate usage and performance statistics | App events, device and OS information, app instance identifier | Firebase Privacy |
| Google Play Billing | The optional one-time purchase that removes ads | Purchase token and purchase state. Payment details are handled entirely by Google Play; we never see your card or payment information. | Google Privacy Policy |
| Google Sign-In & Google Drive API | Optional cloud backup to your own Drive | Your Google account e-mail address and an access token limited to files the App creates | Google Privacy Policy |
| Google Play In-App Update & In-App Review | Prompting you to update or to rate the App | App version and Play Store account state, handled by Google Play services | Google Privacy Policy |
Advertising: ads may be personalised based on the advertising identifier held by your device. You can limit this at any time via Android Settings → Privacy → Ads, where you can reset or delete your advertising ID and opt out of ad personalisation. Purchasing the one-time ad-removal product stops ads from being displayed in the App.
BackupManagerData folder removes all local backups.Because we hold no copy of your data, we cannot delete data on your behalf — but you can always delete all of it yourself using the steps above.
Depending on where you live (for example, under the EU/UK GDPR, or the CCPA in California), you may have rights to access, correct, delete, restrict or port your personal data, and to object to certain processing. Since your personal data never leaves your device and your own Google account, you can exercise most of these rights directly: the data is in your hands, in files you control. For anything relating to the advertising, crash-reporting or analytics data handled by the third parties listed in section 5, please contact those providers, or contact us and we will help where we can.
The App is a general-purpose utility and is not directed at children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal data from children. If you believe a child has used the App in a way that raises a concern, please contact us.
Your data stays on your device and in your own Google account, which limits exposure by design. Transfers to Google Drive use encrypted HTTPS connections. However, no method of storage or transmission is completely secure, and — as noted in section 2.1 — local backup files are not encrypted by the App. Please protect your device with a screen lock and be careful about who you share backup files with.
We may update this Privacy Policy as the App changes or as legal requirements evolve. The revised policy will be published at this address with a new "Last updated" date. Significant changes may also be announced in the App or in the Play Store listing. Continued use of the App after an update constitutes acceptance of the revised policy.
If you have any question, request or complaint about this Privacy Policy or about how the App handles data: