Privacy Policy
- Effective:
- July 12, 2026
- Last updated:
- July 12, 2026
This policy covers the Andcor Launcher Android app(app.andcor.launcher) and this website. The website itself sets no cookies and runs no analytics.
Overview
Andcor Launcher is an Android home-screen launcher. It is built to work without an account, without advertising, and without behavioral analytics. The information the launcher works with — which apps you have installed, when you open them, and the preferences you set — is stored on your device and is used only to provide launcher features.
This policy explains what the app can access on your device, what (if anything) leaves your device, and the choices you have. It distinguishes clearly between information the app processes locally and information transmitted off your device.
Information and permissions the app uses
Andcor Launcher requests the following Android permissions, each tied to a specific launcher feature:
- Installed apps (QUERY_ALL_PACKAGES)
- As a home-screen launcher, the app lists and launches the apps installed on your device, including work-profile apps. The list of installed apps never leaves your device.
- Usage access (PACKAGE_USAGE_STATS) — optional
- If you grant Usage access in system settings, the launcher reads app-usage statistics to rank predictions and suggestions. Usage data is processed and stored only on your device. The launcher works without this permission; predictions are simply less informed.
- Location (ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION) — optional
- Android requires location permission for an app to read the name (SSID) of the Wi-Fi network you are connected to. The launcher uses it solely for Wi-Fi-based Space automations. It does not read GPS position, track your movements, or store a location history.
- Wi-Fi and network state (ACCESS_WIFI_STATE, ACCESS_NETWORK_STATE)
- Used to detect the connected Wi-Fi network for Space automations and to check connectivity.
- Internet (INTERNET)
- Used only to deliver crash and performance reports to the developer (see “Crash reporting” below). The launcher has no other server of its own and no in-app browsing.
- Run at startup (RECEIVE_BOOT_COMPLETED)
- Re-arms your scheduled Space automations after the device restarts.
What the app does not access
Andcor Launcher does not request or use access to your contacts, calendar, camera, microphone, SMS, call logs, or files and media. It has no advertising SDK, no third-party analytics SDK, and it does not use an advertising identifier. There is no account system and no sign-in.
Local device storage
The launcher stores its working data in a local database and local preferences on your device only:
- App usage records
- Which apps you launch and when, used to compute predictions on-device.
- Spaces and automations
- Your Spaces, their app assignments, day-phase definitions, and Wi-Fi or time triggers (including the Wi-Fi network names you choose for triggers).
- Favorites and layout
- Dock pins, widget configuration, and interface preferences.
- Backups you create
- The optional export feature writes a JSON file containing your Spaces, day phases, automations and favorites to a location you pick. That file is under your control; share or delete it as you wish.
- Android system backup
- If you use Android's device backup, the system may include the launcher's data in your device backup according to your Android backup settings.
Network communication and crash reporting
The launcher makes no network requests to deliver its core features. Predictions, search, Spaces, and automations all run on-device. When you use the web-search shortcut, the launcher opens your browser with the query — the request is made by your browser, not by the launcher.
The one exception is crash and performance reporting. The app uses Sentry, an error-monitoring service, to send the developer crash reports, performance traces, and anonymous session counts so problems can be found and fixed during the beta. These reports are configured not to include personally identifying information (the “send default PII” option is off, which prevents transmission of your IP address) and not to include screenshots or screen contents. A crash report typically contains the technical stack trace, app version, device model, operating-system version, and similar diagnostic context.
Information collected by the developer
Outside of the crash and performance reports described above, the developer collects nothing: no account data (there are no accounts), no usage analytics, no advertising data, and no marketing profiles.
If you email the developer for support or a beta invitation, the developer will have your email address and whatever you include in the message, used only to respond to you.
Third-party services
The app relies on the following third parties:
- Sentry (Functional Software, Inc.)
- Receives crash reports, performance traces, and session counts as described above. Sentry processes this data on the developer's behalf. See Sentry's privacy documentation for details of its processing.
- Google Play
- The app is distributed through Google Play. Google's own terms and privacy policy govern the store, including install statistics Google provides to developers in aggregate.
Your privacy rights
Because almost all of your data is stored locally on your device, you have direct control over it. You can access, modify, or delete your launcher data at any time through the app's settings or by uninstalling the app. You can also export your configuration using the app's backup feature. If you have questions about the limited diagnostic data in Sentry, you can contact the developer.
Retention and deletion
Data the launcher stores on your device stays there until you clear the app's storage in system settings or uninstall the app — either removes it. Backup files you export are yours to keep or delete.
Crash and performance reports are retained in Sentry under the developer's account and are automatically deleted on Sentry's standard retention schedule (typically 90 days). To ask for earlier deletion of a specific report, contact the developer.
Security
Launcher data lives in the app's private storage area, which Android isolates from other apps. Crash reports are transmitted to Sentry over encrypted connections (HTTPS). No system is perfectly secure, but the app's design — keeping data on the device and minimizing what is transmitted — limits exposure.
Children's privacy
The app is a general-audience utility and is not directed at children under 13. It does not knowingly collect personal information from anyone; the only off-device data is technical crash reporting as described above.
International use
The app processes launcher data on your device wherever you are. Crash reports are processed by Sentry in the United States. By using the app, you understand that this diagnostic data may be processed outside your country of residence.
Changes to this policy
If the app's data practices change — for example, if analytics, accounts, or new permissions are ever added — this policy will be updated before the change ships, and the “last updated” date above will reflect the revision. Significant changes will be called out in release notes.
Contact
Questions, requests, or concerns about privacy? Contact the developer at privacy@andcor.co.