Skip to content

Privacy Policy

Effective:
July 12, 2026
Last updated:
September 15, 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 your device-wide app history — which apps you open, how long you stay in them, and what you tend to open next — to rank suggestions. That history is read and stored only on your device. The launcher works without this permission; suggestions then learn only from the apps you open through the launcher.
Contacts (READ_CONTACTS) — optional
Typing @ in the search bar looks up people so you can message, call, or email them without opening another app. When you grant it, the launcher reads contact names, phone numbers, email addresses, and the contact actions other installed apps publish, and only while you are searching. Your address book is never transmitted and never copied off the device. Until you grant it, @ still works on a phone number or email address you type out in full.
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. The launcher uses no GPS or satellite positioning API, records no coordinates, and keeps no 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.
Country and timezone — no permission, optional
With Travel awareness on, the launcher reads the country code your mobile network reports and your system timezone so it can notice when you have travelled and adjust suggestions accordingly. This needs no permission, is never GPS, and the reading stays on your device. It is on by default and can be turned off under Integrations in the app.
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

Contacts access is optional, is used only for the @ search described above, and can be revoked at any time in Android settings. Andcor Launcher does not request or use access to your calendar, camera, microphone, SMS, call logs, or files and media, and it never reads a GPS or satellite location fix. There is no advertising SDK, no third-party analytics SDK, and no 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, plus counters for the day phase, weekday, month, country, and timezone you tend to use them in, used to score suggestions on-device.
Action history
How often you use a particular app shortcut, or a particular way of contacting someone, so the right action is offered first. Contact actions are recorded under a one-way hash of the action, not as a copy of your address book.
Recent activity
The Activity list in the app drawer keeps the apps you opened, searches you ran, links you opened, and contact actions you took from search, so you can repeat them. A repeated contact action stores the number or address it used. Clear All empties the list.
Suggestion feedback and tuning
Apps you rate, apps you mark never to suggest, and the per-signal influence gauges you set for an app.
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), and the automation event log the app records so you can see why a Space switched.
Favorites and layout
Dock pins, widget pages and placement, quick-action slots, and interface preferences.
Backups you create
The optional export writes a JSON file containing your Spaces, triggers, day phases, dock pins, usage counters, suggestion feedback, and per-app signal gauges to a location you pick. Learned action history and country or timezone counters are not exported. That file is under your control; share or delete it as you wish.
Diagnostic exports you share
The automation event log and the signal snapshot can be shared as JSON from inside the app. Those files include the current Wi-Fi network name and your device model, so send them only to someone you intend to.
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, @ contact lookup, 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 crash reports, a 5% sample of performance traces, and anonymous session counts so problems can be found and fixed during the beta. Reports are configured not to carry personally identifying information (the "send default PII" option is off, which also prevents your IP address being transmitted), not to attach screenshots or screen contents, and not to record what you tap. Before a report is sent, the app strips phone numbers, email addresses, web and contact links, search text, Wi-Fi network names, app and Space names, and country or timezone values from it. Your install is identified only by a random identifier generated on first run — not an advertising ID and not an account. A 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.

Data sharing and sale

The developer does not sell personal information and does not share it with third parties for advertising or marketing. Crash-report data is shared only with Sentry, acting as a processor for the developer. The only exception is if we are ever legally required to disclose information (for example, in response to a valid subpoena or court order), though we have very little information to give.

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. Inside the app you can also clear everything learned about a single app, clear what a single Space has learned, revoke contacts, location, or usage access in Android settings, and turn Travel awareness off.

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.

On your device, the launcher also ages out what it has learned: usage counters for an app you have not opened in 30 days are decayed and then dropped, app-to-app transition counters after 7 days, internal prediction records after 90 days, and suggestion-rating telemetry after 180 days. Apps you marked never to suggest are kept until you restore them, and data for an app you uninstall is removed.

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.