Flua Launcher Global Privacy Policy

This Global Privacy Policy explains how Thiago de Medeiros Mendes, based in João Pessoa, Paraíba, Brazil (we, us, or our), processes personal data when you use the Flua Launcher Android application (the App).

We are the controller of the personal data described in this Policy. For privacy questions or to exercise your rights, contact us at contact@flualauncher.com. Additional rights may apply depending on where you live; see Section 11 (Regional disclosures).

1. Summary

Flua Launcher is designed to keep your launcher content on your device. We do not sell personal data, do not serve advertising, and disable collection of the Android advertising identifier in Firebase Analytics.

The App uses Firebase Analytics and Firebase Crashlytics by default for pseudonymous usage measurement and crash diagnostics. You can disable each service independently in Settings > About > Legal; neither service has a checkbox in onboarding. The App also uses Google Play for optional purchases, Google Drive for Android system backup and for the App's separate optional backup feature, a self-hosted Quackback feedback portal hosted on Railway when you choose to use it, Cloudflare R2 to deliver curated wallpapers, and Open-Meteo for weather forecasts and city geocoding. These providers may process data in multiple countries.

2. Data we process

2.1 Data stored on your device

The App stores launcher data locally to provide its features, including:

• settings for layout, appearance, fonts, icons, widgets, wallpapers, and presets;
• any custom font file you import for launcher typography;
• your selected Home shortcuts and folders, including app package identifiers and any folder labels you create;
• local references to selected wallpapers and, when necessary, locally stored wallpaper image files;
• widget configuration, including selected calendar identifiers for an agenda widget;
• Premium trial and entitlement state; and
• an installation-specific random identifier used only to help manage backup snapshots.

This data is not sent directly to us merely because you use the App. Some eligible local data may be backed up by Android as described in Section 2.6.

2.2 App, device, and analytics data

Firebase Analytics is enabled by default. Google Firebase processes pseudonymous technical and usage data while the Analytics toggle is enabled. This can include an app-instance or installation identifier, device model, operating-system and App version, language or region, session and engagement information, IP address, and an approximate location derived from the IP address. This data is not anonymous because identifiers and connection data may distinguish an App installation or device. The App does not enable the Android Advertising ID, Google Signals, User-ID, or user-provided data collection.

The App sends carefully limited, controlled analytics events and properties. The event groups are:

• onboarding and retention progress, using step, entry-point, reason, and milestone buckets;
• feature use and feature errors, using controlled feature, action, operation, result, source, and error-category values;
• aggregate Home inventory buckets for apps, folders, and widgets, without sending app names, app package names, or folder names;
• default-launcher status;
• icon-pack adoption as the boolean property custom_icon_pack, never as a package name;
• a conservative set of Home settings useful for product decisions, such as display mode, label/icon visibility, font-family category, notification features, widget-related feature flags, folder style, index behavior, status-bar visibility, haptic feedback, swipe-up action, and double-tap-to-lock;
• paywall and purchase-flow events, including the controlled Premium feature and the Google Play product identifier; and
• user properties for access tier/status, display mode, custom icon-pack use, Home app-count and widget-count buckets, backup status, notification-access status, and default-launcher status.

The home_setting_state event does not include exact sizes, spacing, opacities, colors, or other similarly granular visual values. The preset_type value used in onboarding is a controlled category; the App does not send a preset_id.

We deliberately do not send your installed-app list, selected app package list, folder names, notification content, calendar-event content, Google Drive access tokens, purchase tokens, payment-card data, User-ID, account identifiers, free-form text, or exception messages to Firebase Analytics. The App does not use setUserId or create advertising profiles.

2.3 Firebase Crashlytics

Firebase Crashlytics is enabled by default and is controlled independently from Analytics. When enabled, Crashlytics may process crash logs, stack traces, App and operating-system versions, device model, technical installation/session identifiers, and other diagnostic information needed to investigate crashes. The App does not add custom Crashlytics keys, User-ID values, free-form logs, notification content, app or folder names, account identifiers, or user-created content, and it does not manually record exception messages as Crashlytics data.

When Crashlytics is disabled in Settings > About > Legal, the App disables collection and discards pending unsent reports so they are not sent later. Disabling Crashlytics does not disable Analytics, and disabling Analytics does not disable Crashlytics.

2.4 Weather location and city search

When you use the automatic-location option of the weather widget, the App may request Android approximate location permission and send the resulting latitude and longitude to Open-Meteo to obtain a forecast. Older versions may request precise location instead. Automatic location is optional and is used only for weather lookup. A city selected through manual search is not treated as the user's precise location.

When you type a city into the weather search field, the App sends the search text to Open-Meteo's geocoding service at geocoding-api.open-meteo.com to find matching cities. This is an in-app search query and may be stored locally as part of the selected weather-widget configuration. The query is not sent to Firebase Analytics. Open-Meteo may process request metadata and states in its current policy that logs may contain geographic coordinates and may be retained for up to 90 days; this processing is therefore not described as ephemeral.

2.5 Notifications and calendar data

If you grant notification access, the App reads active notifications to show notification badges and a shortcut sheet. If you grant calendar access, the App reads calendar names and events to provide the agenda widget. The App processes this data on your device for those features and does not send it to us or to Firebase Analytics.

You can revoke these permissions at any time in Android settings. Revoking a permission disables the related feature.

2.5.1 Contact search

If you enable contact search and grant access to contacts, the App searches your device's contacts to show matching results in the app list. It reads contact identifiers, display names, and thumbnail references; the Android contacts provider may also match your search against other contact fields. To find approximate name matches, the App may read contact names beyond the initial matches. Search results are processed on your device, and tapping a result opens the contact in an appropriate app. The App does not send contact search results to us or to Firebase Analytics. You can disable contact search in the App or revoke contacts permission in Android settings; the rest of the launcher remains available.

2.5.2 AccessibilityService API for optional screen-lock gestures

If you choose to use the optional double-tap or swipe-up screen-lock gesture, Flua Launcher asks you to enable its Android AccessibilityService. The service is used only to perform Android's lock-screen action after you trigger the configured gesture. It does not retrieve window content, read or record your screen, text, passwords, notifications, audio, calls, or other app data, and it does not transmit, store, or share data through the AccessibilityService. You can decline or disable this access at any time in Android settings; the rest of the launcher remains available.

2.6 Android system backup

The App participates in Android's system backup and device-transfer mechanisms. Depending on your device, Android version, manufacturer, and Google account settings, Android may automatically back up eligible App preferences and files to storage associated with your Google account or transfer them directly to another device. Google and your device manufacturer control these system services; the App does not receive your Google login or directly access the system backup created by Android.

The App excludes selected operational, backup-coordination, scheduling, Premium-entitlement, and background-work data from Android system backup. Other eligible local settings and files, including an imported custom font, may be included. You can manage Android backup through your device or Google account settings. Android system backup is separate from the optional Flua Launcher backup described below.

2.7 Optional Flua Launcher backup

If you choose to enable Flua Launcher's Google Drive backup, the App creates versioned backup snapshots in the private appDataFolder of the Google account you authorize. A snapshot can include launcher settings, selected Home app package identifiers and folder labels, presets and schedules, widget configuration including selected calendar names and account metadata needed to restore a calendar selection, an imported custom font file, wallpaper references, and embedded wallpaper image data when needed to restore a local image. This is a separate, user-authorized backup flow; the restrictions on Firebase Analytics and Crashlytics telemetry do not prevent data that you explicitly choose to back up from being sent to Google Drive.

The App requests only the Google Drive drive.appdata scope. It does not request access to your ordinary Google Drive files. Google processes the authorization and stores the backup under the terms and privacy policies applicable to your Google account. You can disable this backup in the App and choose whether to keep or delete existing Flua Launcher snapshots. Those controls do not delete a separate Android system backup.

2.8 Purchases

Premium purchases are processed by Google Play Billing. Google Play may process your Google account, order information, payment method, payment status, purchase token, and related fraud-prevention information. The App receives the purchase state needed to provide access, stores a local entitlement flag, and does not transmit purchase tokens to our servers.

The App may send the Google Play product identifier and a controlled Premium-feature category to Firebase Analytics as purchase-flow metadata when Analytics is enabled. This is purchase history/product metadata, not payment or financial information. We do not receive or store your full payment-card information.

2.9 Support and feedback

When you follow the App's feedback link, you access the Flua Launcher feedback portal at feedback.flualauncher.com. It runs a self-hosted installation of Quackback and is operated by us as a support and feedback channel; Railway provides the cloud infrastructure that hosts it.

The portal permits anonymous participation. You do not need to create an account, provide your name, or provide an email address to submit feedback, vote, or comment where those features are available. The portal may still process a session or other pseudonymous identifier and technical connection information, such as IP address, browser type, device information, timestamps, and essential cookies, to operate the service, prevent abuse, and maintain the session. It also processes the content you choose to submit, including feedback, votes, comments, screenshots, attachments, and any personal information you include. Posts and comments may be visible publicly; do not submit confidential information, payment data, or personal data you do not want to share.

2.10 Wallpaper delivery and external links

The App retrieves its curated wallpaper catalog and images from Cloudflare R2. Cloudflare may receive standard connection data, such as your IP address and request metadata, when delivering those files. External links are opened outside the App and are governed by the destination's privacy practices.

3. Purposes and legal bases

Where applicable law requires a legal basis, we rely on the bases shown below. The exact name and scope of a legal basis may vary by jurisdiction.

Analytics and Crashlytics are enabled by default and have independent controls in Settings > About > Legal. Disabling either service stops future collection by that service; disabling Crashlytics also discards pending unsent crash reports. These controls do not affect the App's core features. Where applicable law requires consent or another control for a particular use, we will apply the legally required approach for that use.

Where we rely on legitimate interests, those interests include operating, securing, supporting, diagnosing, and improving the App. We balance those interests against your rights and use data-minimizing measures, including local processing, controlled event values, independent opt-out controls, and no advertising identifiers.

4. Sources of personal data

We receive data:

• from you, when you choose settings, enable backup, make a purchase, or contact support;
• automatically from the App or your device, but only for the technical operations described in this Policy;
• from Google Play, for purchase and entitlement status; and
• from service providers, when needed to operate support, analytics, backup, and content delivery.

We do not use personal data for automated decisions that produce legal or similarly significant effects, and we do not create advertising profiles.

5. How we disclose data

We do not sell personal data or share it for cross-context behavioral advertising. We disclose or make data available only as described below:

At the time of this update, the Firebase/Google Analytics property has no Google Ads or BigQuery link, and Google Signals is disabled. The App does not export Analytics or Crashlytics data to BigQuery and does not send it to Google Ads. These statements describe the configuration verified for the current release and must be reviewed if integrations or account settings change.

We may also disclose data where necessary to comply with law, protect rights or safety, investigate fraud or security incidents, or complete a lawful business reorganization, subject to applicable law.

6. International processing and transfers

We are based in Brazil. Google, Firebase, Railway, Cloudflare, device manufacturers, and their service providers may process data in Brazil, the United States, and other countries where they operate. Those countries may have privacy laws that differ from the laws where you live.

Where transfer restrictions apply, we use or rely on a legally recognized mechanism appropriate to the service and transfer, such as an adequacy decision, contractual safeguards including applicable standard contractual clauses, or another mechanism permitted by law. For Firebase services, Google's applicable data-processing terms incorporate data-transfer solutions and standard contractual clauses for restricted European transfers where required. You may contact us to request information about safeguards relevant to your personal data.

7. Retention

• On-device launcher data: retained until you change or delete it, clear the App's data, or uninstall the App.
• Android system backup: retained according to Android, Google, your device manufacturer, and your account settings. We cannot directly view or delete this system-controlled backup.
• Flua Launcher Google Drive backups: the automatic backup feature keeps the five newest snapshots plus up to four weekly recovery points. Snapshots remain until replaced under that rotation or deleted by you through the App, subject to Google Drive behavior.
• Firebase Analytics and Crashlytics data: retained according to the current Firebase and Google Analytics service settings and provider policies. This Policy does not promise a specific retention period because the effective retention configuration may change and has not been fixed here. We do not configure a BigQuery export for either service.
• Open-Meteo weather and geocoding requests: Open-Meteo's current policy states that logs may contain geographic coordinates and may be retained for up to 90 days. These requests are not treated as ephemeral processing.
• Support and feedback: retained while the submission remains useful for support, product development, community history, dispute resolution, or legal compliance. You may request deletion, subject to applicable law and technical limitations for content that has already been incorporated into the product or de-identified. For anonymous submissions, include the post URL or enough detail for us to locate the content.
• Purchase records: retained by Google Play under Google's policies. We retain any records we separately create only as needed for support, accounting, tax, legal, and fraud-prevention purposes.

When retention ends, we delete or de-identify data where reasonably possible. Backup copies and provider systems may take additional time to cycle out data.

8. Security

We use reasonable technical and organizational measures intended to protect data. Network requests use encrypted connections where the relevant provider supports HTTPS, access to services is limited, and Analytics and Crashlytics collection can be disabled independently in the App. No method of electronic storage or transmission is completely secure, so we cannot guarantee absolute security.

Keep your device, Android account, Google account, and backups secure. Do not post sensitive information in the support forum.

9. Your choices and privacy rights

Depending on applicable law, you may have the right to:

• know whether and how we process your personal data and obtain access to it;
• correct inaccurate or incomplete data;
• request deletion, anonymization, blocking, or restriction;
• obtain portability where applicable;
• object to certain processing or ask us to review it;
• withdraw consent at any time;
• receive information about disclosures and international-transfer safeguards;
• appeal our response where applicable; and
• complain to a competent privacy or data-protection authority.

To make a request, email contact@flualauncher.com with the subject line Privacy Request. Describe your request and provide enough information for us to locate the relevant data and reasonably verify that the request concerns you. We will use verification information only to handle the request. You may use an authorized agent where applicable law permits, but we may request proof of authorization and verification of your identity.

We will respond within the period required by applicable law. If we deny a request, we will explain the reason and any available appeal or complaint process. We will not discriminate against you for exercising a privacy right.

Some data remains only on your device or is controlled directly by third parties. You can manage App data and Android permissions in Android settings, Android system backup in your device or Google account settings, Google Play purchases in Google Play, Flua Launcher backups in the App, and feedback-portal submissions through the portal where available. To request access to or deletion of an anonymous submission, contact us with the post URL or enough detail to locate it. We will explain relevant limits when responding to a request.

10. Children

The App is intended for people aged 13 and older and is not directed to children under 13. We do not knowingly collect personal data from a child under 13. If you are under the age at which you can independently consent to data processing or enter into a binding agreement where you live, use the App only with the authorization of a parent or legal guardian and do not enable optional analytics or submit information to the support forum unless they approve.

If a parent or guardian believes that a child under 13 provided personal data through analytics, the support forum, or another connected service, contact us at contact@flualauncher.com. We will investigate and take appropriate steps, including deletion where required and reasonably possible.

11. Regional disclosures

These disclosures supplement the rest of this Policy. They apply only when the listed law governs our processing and do not limit rights available under another applicable law.

11.1 Brazil

Under Brazil's General Data Protection Law (LGPD), the controller is Thiago de Medeiros Mendes. The purposes and legal bases for processing are described in Section 3. Depending on the circumstances, we rely on consent, performance of a contract or preliminary procedures you request, legitimate interests, exercise of rights, and compliance with legal or regulatory obligations.

You may request confirmation of processing, access, correction, anonymization, blocking, deletion, portability where applicable, information about sharing, review of certain automated decisions, and revocation of consent. You may also object to unlawful processing and complain to the Autoridade Nacional de Proteção de Dados (ANPD).

11.2 European Economic Area, United Kingdom, and Switzerland

For processing governed by European data-protection law, the legal bases are described in Section 3. You may have rights of access, rectification, erasure, restriction, portability, objection, and withdrawal of consent. You may complain to the data-protection authority where you live, work, or believe an infringement occurred.

Where required, we conduct a balancing assessment before relying on legitimate interests. We do not conduct solely automated decision-making that produces legal or similarly significant effects. For questions or requests, contact the controller directly using the details in Section 13.

11.3 United States

Depending on the state where you live and whether the relevant law applies to us, you may have rights to know, access, correct, delete, or obtain a portable copy of personal data and to appeal a denied request. We do not sell personal data, share it for cross-context behavioral advertising, use it for targeted advertising, or process it for qualifying automated decisions. We therefore do not provide a sale, sharing, or targeted-advertising opt-out mechanism.

For California residents, the categories collected in the preceding 12 months may include identifiers, internet or other electronic-network activity, commercial information related to purchase status, and information you submit to support. The sources, business purposes, and categories of recipients are described in Sections 2, 4, and 5. We do not use or disclose sensitive personal information for purposes that require a right to limit under California law.

11.4 Canada

Where Canadian privacy law applies, you may request access to and correction of personal information we hold about you and challenge our compliance. We obtain meaningful consent where required and limit collection, use, and disclosure to identified and appropriate purposes. You may withdraw consent, subject to legal or contractual restrictions and reasonable notice.

12. Changes to this Policy

We may update this Policy to reflect changes to the App, legal requirements, or our data practices. We will publish the updated Policy with a revised Last updated date and provide additional notice before material changes where required by law.

13. Contact