Nokia Launcher is an independent Android launcher with an optional Nokia System Keyboard and built-in tools. This policy describes the data practices of the app's available features, including optional Accessibility access and Google Play purchases where billing is enabled. Features and permissions depend on the installed version, Android version and device. The developer is identified on the Google Play listing. Privacy contact: [email protected].
The app accesses installed-app names, icons, package names and launch activities to display and open apps, search the drawer, assign shortcuts and apply your selected Dumb Mode rules. Installed-app inventory is not uploaded by these features. Preferences, shortcuts, blocked-app selections and local feature state may be saved on your device; this information is not limited to temporary working memory.
Nokia Launcher accesses the foreground app's package name and its interface content, including text, controls and their positions, through Android Accessibility Service. It uses these capabilities for Nokia-key focus, scrolling and selection, Back, Recent Apps and screen lock. While Dumb Mode is active, foreground-app changes identify apps you chose to block and return you to Home, including when Nokia Launcher is not on screen. This Accessibility data is processed locally; it is not stored as a screen history, used to record typing, or sent to the developer, RevenueCat or other third parties. Accessibility is optional and requires a separate in-app disclosure and affirmative consent before activation. You can decline and continue using launcher features that do not require it, or disable the service in Android Accessibility settings. Consent is not included in Android backup or device transfer.
The optional system keyboard processes input locally to send it to the app where you are typing. Nokia Launcher does not upload keyboard input for tracking or advertising. The receiving app has its own privacy practices. When you use built-in communication features and grant the corresponding permissions, Nokia Launcher accesses contact names and numbers, SMS content and metadata, and call-log entries to display contacts, conversations and recent calls. Direct dialing uses Phone access. Sending SMS and placing calls deliver your selected message or call to the recipient through Android and your carrier, whose charges and privacy practices apply. Local read markers and feature state may be retained on the device. Permission availability and functionality remain subject to Android and Google Play requirements.
Camera access provides photo and video capture. Microphone access records audio when recording video. Media is saved locally and gallery access displays available media. Taking, deleting or sharing media occurs through the feature you select. The app does not automatically upload your photos, videos or microphone recordings to the developer.
If you enable notification access, Nokia Launcher reads notification information, including sender/title, message text, application identity, timestamps and available images or reply actions. It uses this information for status indicators and supported notification conversations and replies. A bounded on-device cache supports this display; notification history is not a complete SMS mailbox. Replies use the originating app's Android reply action. Notification content is not uploaded to the developer by this feature. You can revoke notification access in Android Settings.
When billing is enabled, Google Play processes payments and RevenueCat validates purchase tokens and transaction information, manages subscription or Lifetime access and restores purchases. RevenueCat uses an SDK-generated anonymous app-user identifier, purchase history and status, and technical information such as app/SDK and operating-system information. Network requests also expose normal connection information to the receiving service. Nokia Launcher does not ask you to enter card details and does not send contact lists, SMS text, keyboard input or Accessibility screen content to RevenueCat. Purchase records can be available to the developer through RevenueCat for access management and support. See Provider privacy policy and Provider privacy policy.
Where Play Integrity checks are used, Google processes app, licensing and device-integrity signals; an encrypted integrity token is sent to the configured verification backend to verify the request. Browsing, searches, maps, shared media and support messages send the information needed for the action to the website, provider or recipient you choose. Those services have their own privacy policies. Friend Authenticator pairing uses locally stored pairing information and user-directed QR/code exchange; keep pairing codes private.
Local settings, read markers, caches, media and pairing information are retained as needed for their features. You can revoke Android permissions, disable the keyboard or Accessibility service, manage or delete media, and clear app storage or uninstall the app. Android or your device provider may back up eligible app data under your system settings; clearing app storage does not erase media saved outside private app storage or provider-side purchase records. Clearing or uninstalling the app does not cancel a subscription: manage subscriptions in Google Play. Google and RevenueCat retain purchase/service records under their applicable policies and legal obligations. Contact [email protected] for privacy or deletion requests; we may need purchase/support information to locate the relevant record.
We do not sell personal information or use keyboard input, installed-app inventory or Accessibility content for advertising. Purchase validation and optional security checks involve the providers described above; the app is not entirely offline. On-device data is protected by Android's security controls. Provider requests use their secure service connections. No storage or transmission method is perfectly secure.