Use this Android launcher privacy checklist before setting a third-party app as Home. A launcher naturally knows which launchable apps it displays. Sensitive access beyond that should connect to a feature you chose and understand.
The checklist is designed for ordinary users. You do not need to inspect source code to ask useful questions.
1. Confirm the package source
Install from the official store listing or the developer's verified release page. Check the developer identity and package name. Avoid modified APKs because they can be signed and changed by someone else.
2. Read the current privacy policy
Look for a last-updated date and concrete answers about collection, storage, sharing, retention, and deletion. Take a screenshot or save the URL if the policy is important to your decision.
Minimalistic's current policy says there are no ads, analytics, trackers, login, or cloud sync, and that settings remain local. The live source is the Minimalistic privacy page.
3. Separate required and optional permissions
The launcher must list and open installed apps. Wallpaper and user-selected backup files also have clear purposes. Location, contacts, notifications, usage access, and Accessibility should be optional unless a visible feature requires them.
Decline optional access during the first test. Home, search, favorites, and the app drawer should remain usable.
4. Check installed-app data handling
An app list can reveal interests, work tools, financial apps, or health apps. Ask whether package names or labels leave the device. A local cache is different from uploading a list for analytics or recommendations.
Package-change handling should remove uninstalled apps from local favorites, hidden lists, and distracting lists without sending the list elsewhere.
5. Review every network feature
Turn off optional weather or remote content and test the launcher offline. If the core Home depends on a server, the privacy and reliability risk is higher.
For weather, look for the provider, what location value is sent, and whether precise GPS is necessary. Minimalistic allows a manual city and uses Open-Meteo for the requested forecast rather than continuous location tracking.
6. Inspect SDK disclosures
Advertising, analytics, attribution, crash reporting, and social SDKs can send data even if the launcher's own code does not run a user account. Check the store data-safety section, privacy policy, and any available dependency list.
No tracker claim should cover the shipped app, not only the developer's own server.
7. Understand Accessibility Service use
Accessibility can observe interface events and take broad actions. A launcher that uses it for optional blocking must show a prominent disclosure, ask for consent, limit use to that feature, and work without it.
Read Accessibility permission for a launcher before enabling the service. Do not grant it because a setup screen simply says "required" without explaining why.
8. Check backup and restore
A local backup can contain favorites, hidden packages, renamed labels, profiles, notes, tasks, and preferences. Choose the file location through Android's Storage Access Framework and protect the file like any personal configuration.
The app should handle malformed restore files without crashing. Avoid backups that silently upload to a vendor account when the product claims no cloud sync.
9. Find deletion controls
You should be able to unhide apps, clear local notes, reset preferences, disable special access, or uninstall the launcher. Changing the default Home app should not depend on a vendor account.
Android clears ordinary app storage on uninstall, though exported backup files remain where you saved them.
10. Repeat the review after material updates
Read release notes when a launcher adds cloud sync, an AI feature, ads, analytics, account login, device-wide blocking, or a new SDK. A safe decision from last year may need a new review after ownership or feature changes.
Record a short verdict
Write down the source, optional permissions you enabled, network features you use, backup location, and switch-back path. This takes a minute and helps later if behavior changes.
Privacy is easier to manage when each capability has a visible reason. If a launcher cannot explain its data flow in plain language, keep the stock Home app while you investigate.