Privacy Policy

Who this policy is for

This policy explains how VoidLauncher, published by AnonLab, handles information when you use the launcher and its optional features. For privacy questions or requests, contact anonlab.company@gmail.com.

Your home screen is stored on your device. Some features also use online services: AI assistance, weather, ads, updates, developer news, and account or purchase checks. Availability depends on your app version and build. The sections below explain what each feature sends, rather than treating the whole app as either “offline” or “cloud-based.”

Your home screen and media

Layouts, folders, icon choices, widget configuration, lock-screen customization, preferences, recent search history, and setup status are stored in the launcher's local databases, files, or preferences. VoidLauncher reads installed app names and package information to display, search, and launch apps.

Photos and videos you choose for wallpapers or Image widgets are accessed through Android's picker or media permissions. The launcher may retain access to the selected file or keep a private copy so it remains available after a restart. Crops, thumbnails, icon images, and visual-effect caches are generated locally. Gyroscope-driven effects use motion data on the device.

These features do not themselves upload your media or layout. There is an important exception: a home-screen image sent through Qubie can include your wallpaper, photos, widget contents, and labels. See the AI section below.

Widgets from other apps are supplied by those apps. Their providers may receive widget size/configuration updates and handle taps or network requests under their own privacy policies.

Qubie: voice and AI assistance

Voice recognition. With microphone permission, voice mode uses your device's Android speech-recognition service. It listens in repeated recognition sessions while the assistant's voice input is active. Switching to keyboard input or closing the assistant stops that recognition session. Depending on the speech provider and device, audio may be processed online. Classic mode does not send requests to OpenRouter, but voice recognition is not guaranteed to be offline.

AI requests. Where AI mode is available, VoidLauncher sends your typed or recognized words to OpenRouter, which forwards them to the model provider serving the request. Each request also includes the names and component/package identifiers of launchable apps and a catalogue of supported launcher settings and actions. That catalogue describes settings; it is not a copy of all your saved setting values. Qubie's OpenRouter integration sends text and, when requested, an image—not the microphone recording.

Looking at your home screen. During an AI interaction, Qubie can decide to inspect the current page when it would help answer your request. You do not have to explicitly ask for a screenshot, and the current implementation does not show a separate confirmation for each capture. It sends:

• An image rendered from the launcher window, with the assistant panel excluded. Visible wallpaper, widgets, photos, app labels, and other launcher content can appear in it. Sensitive content is not automatically redacted.
• Structured information about the current page and dock: app and folder names, folder contents, component identifiers, item/widget IDs, widget providers, positions, sizes, grid dimensions, and visible bounds. Folder contents can be included even when the folder is closed.

This is an on-demand capture, not continuous screen recording. It does not capture the contents of another app's separate window or separate system overlays. The capture is prepared in memory and is not saved as a gallery screenshot. Once transmitted, it is also subject to the receiving services' handling practices.

Context and actions. When Qubie asks a follow-up question, a short conversation history is kept in memory and sent with your next response. This is not a permanent chat archive; it is cleared when no longer needed for the follow-up, when you switch mode, or when the panel closes. The AI can select supported local actions, including launching apps, moving icons, navigating pages, or changing settings. Responses can be wrong, so check important changes.

Providers and logs. OpenRouter receives the request and connection information, including your IP address; the model provider receives the forwarded inputs. The current model configuration is Qwen through OpenRouter (qwen/qwen3.7-flash); the serving provider may depend on routing. Provider retention and training practices vary; VoidLauncher does not enforce a zero-retention provider route. Read OpenRouter's privacy policy and its data-handling documentation. Qubie's raw AI replies are also written to Android's local diagnostic log in the current implementation. Those replies can repeat information you supplied or information visible on your home screen.

Do not include passwords, payment details, or other sensitive information in AI requests or in visible content you do not want sent. If you do not want home-screen information sent to an AI provider, do not use AI mode; use classic mode where available or close the assistant. Keyboard input avoids microphone use, but AI text requests still go online.

Weather and location

Weather uses Open-Meteo. Automatic location obtains coordinates from Android after location permission is granted; a manually chosen location uses the coordinates you provide. Latitude and longitude are sent to Open-Meteo for current conditions and forecasts. The request does not attach your app inventory or an Android device ID, but the service receives normal network information, including your IP address.

City-name lookup uses Android's geocoder, whose provider may process coordinates online. Forecasts, location labels, and related settings are cached locally. While the weather repository is running, it checks for updates periodically and ordinarily requests a fresh forecast about once a minute; network errors and manual refreshes can change the timing. The widget's local refresh is not a separate network request every time it redraws.

You can choose a manual location and revoke location permission in Android settings. This stops automatic location access, not requests for a saved manual location. See Open-Meteo's terms and privacy information.

Updates, developer news, and notifications

Firebase Realtime Database supplies update information and developer posts. Firebase Remote Config supplies release, availability, and feature configuration. These connections can occur at startup as well as when you open the relevant screen. Google may process installation identifiers, connection information, and service diagnostics to provide these services.

The developer-news screen records whether an Android ID has viewed a post, and increments a view count. When you react, it records that the Android ID has reacted and increments the chosen reaction's count. These are device-linked records, not anonymous counts. Android ID is distinct from the advertising ID.

Firebase Cloud Messaging is used for developer-news and update notifications, including topic subscriptions. It uses an installation/registration token to deliver messages. Turning off notifications in Android controls whether they are displayed; it does not necessarily delete the messaging token or database records.

Remote post images, team images, web search results, and external links are loaded from their respective hosts. Those hosts receive connection information when accessed. See Firebase's privacy information and Google's privacy policy.

Accounts, beta access, and purchases

Where account or Pro features are available, Google sign-in and Firebase Authentication process sign-in credentials and profile information. The launcher's account records can include a Firebase user ID, email address, account creation time, and entitlement status. Availability of these features does not mean every installation creates an account.

Google Play handles payments. VoidLauncher receives purchase information needed to check or restore access, rather than your payment-card number. Verification can send a purchase token, product/plan identifiers, and a Play Integrity token to a Firebase Cloud Function. Google handles its own payment and transaction records.

Builds that require a beta key send the key and Android ID to Firebase for validation and device binding. The record can contain the associated username, activation time, and successful or unsuccessful activation attempts. Uninstalling the launcher does not remove those server records.

For account, entitlement, or beta-record questions, contact us at the address above. Uninstalling the app or deleting its data does not cancel a Google Play subscription; manage subscriptions through Google Play.

Advertising

VoidLauncher uses Google Mobile Ads (AdMob), including ads in settings and some wallpaper-related flows. The SDK may process your IP address, advertising/app-set identifiers, ad interactions, and performance or diagnostic information for ad delivery, measurement, and fraud prevention. This processing is separate from Qubie's requests.

Google's User Messaging Platform is used to request and display applicable consent information. Ad behavior depends on consent, region, and SDK configuration. Android's advertising settings let you manage the advertising ID, but limiting personalization does not stop every advertising-related network request.

See Google's advertising information and the Mobile Ads SDK data disclosures.

Permissions and optional integrations

The permissions you see depend on Android version, build, and enabled features. Declaring a permission does not mean Android has granted it.

• Microphone and location: voice recognition and weather, as described above.
• Photos, videos, files, and audio: selected wallpapers and media, backup import/export, and supported local search features.
• Contacts and calling: optional contact search and contact actions. Contact search reads matching information on the device; it is not automatically sent as an address book to Qubie.
• Notification access: notification dots, previews, and supported media controls. Notifications can contain names and message text. Content visible on the home screen may also appear in an AI capture.
• Usage access and app visibility: supported app suggestions, app discovery, and launcher integrations.
• System controls: wallpaper changes, supported quick actions, vibration, connectivity controls, and settings changes where Android allows them.

You can change permissions and special access in Android settings. Some features will stop working without their required access. Optional web search or online suggestions send search text to the selected provider; local contact/file search and online search are different operations.

Crash reports and support

After a crash, the launcher can create a local report containing the app version, device model, Android/build information, display density, exception, and stack trace. The built-in crash report is not automatically sent to AnonLab. You can choose to copy or share it using another app.

Diagnostic logs may contain AI replies, technical errors, and other context. Review logs, screenshots, and exported files before sending them. If you contact support, we receive your message, contact details, and whatever attachments you choose to share.

Storage, backups, and deletion

Local settings and saved files remain until changed, removed, cleared through Android's app-storage controls, or removed by uninstalling the app. Caches and diagnostic logs may be cleared earlier. Removing a widget is not a guarantee that every cached or privately copied file is immediately erased.

Manual exports go to the destination you choose, which may be a cloud-backed document provider. Android backup or device transfer can also include eligible launcher databases and preferences. Clearing app data does not remove an exported archive, its cloud copies, or your original photos and videos.

AI clarification history and capture buffers are temporary on the device. This does not delete data already sent to OpenRouter or another provider. Their retention rules apply to their copies and service logs.

The app does not automatically expire Firebase account, beta-access, or developer-news records after a fixed number of days. To request access, correction, or deletion of records held by AnonLab, email us and identify the account or feature involved. We may need information to locate the record and verify the request. Do not send passwords or full payment-card details. Payment records, legal obligations, and records controlled independently by service providers may require separate handling.

Your choices and rights

Using the launcher does not require using every optional online feature. You can avoid AI mode, use typed instead of spoken input, choose a manual weather location, limit permissions, and decide whether to share diagnostic reports.

Where data-protection law applies, you may have rights to access, correct, delete, restrict, object to processing, or obtain a portable copy of your data. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing. You can also complain to your local data-protection authority. These rights depend on the circumstances and applicable law; see the European Commission's explanation.

Our online providers may process information outside your country, including outside the European Economic Area. Their policies explain their processing locations and transfer arrangements. We do not promise that all data stays in Hungary or in the EU, or that any system is completely secure.

If a child uses the launcher, a parent or guardian should review online features and permissions with them. Avoid sending children's personal information in AI messages, visible widgets, photos, or support attachments.

Changes and contact

We update this policy when the launcher's data handling changes. The date above identifies this version. A policy update does not itself grant a new Android permission or replace consent where consent is required.

Privacy requests: anonlab.company@gmail.com.