Privacy Policy for Broken Screen Wallpaper

Last updated: August 30, 2026

This Privacy Policy explains how Broken Screen Wallpaper (Android package: omarapps22.broken.screen.wallpaper), provided by lion apps, handles information when you use the app.

Privacy contact: saif1212kr@gmail.com

1. Overview

Broken Screen Wallpaper does not require you to create an account. The app provides wallpapers, live/video wallpapers, broken-screen visual effects, local photo-to-wallpaper/video tools, entertainment features, and optional advertising-supported functionality.

Photos that you deliberately choose through Android's system document picker are processed on your device for the feature you selected. The app does not upload those selected photos to our Firebase database.

The app uses network services to retrieve remote content, Google Mobile Ads to display advertising, Google's User Messaging Platform (UMP) to manage privacy and consent choices where required, and Firebase services for content catalogs, limited popularity statistics, and app-integrity protection.

2. Information Handled by the App

Wallpaper, Effect, and Popularity Activity

When Firebase-backed features are enabled, the app may transmit limited information needed to operate content and popularity features. This can include wallpaper, effect, or filter identifiers; validated HTTPS content references associated with those items; actions such as setting a wallpaper, applying an effect, or liking a wallpaper; timestamps; and aggregate counters.

For wallpaper likes, the app creates a random installation identifier and stores it locally on the device. This identifier may be used as the document identifier for an anonymous wallpaper-like record in Cloud Firestore. It is not your name, email address, Android ID, or advertising ID, and the app does not use it to create an account or personal profile. The app excludes this local installation identifier and pending popularity queues from Android cloud backup and device-to-device transfer.

Local file paths, Android content-provider URIs, and media generated from a photo you selected are not placed into the Firestore popularity queue. Only validated remote HTTPS content references are accepted by that synchronization flow.

Photos and Generated Media

When you choose a photo, the app uses Android's system document picker and receives access only to the item that you selected. The selected photo is processed locally for features such as previews, filters, wallpaper effects, or generated video/wallpaper media.

Generated media may be kept temporarily in the app's private storage or saved to public Pictures or Movies locations when you explicitly request a save. On current Android versions the app uses Android's scoped media APIs. On Android 9 and earlier, legacy storage access may be requested only when needed to save media to shared storage.

We do not upload the photo you select through this picker to our Firebase database.

Local Preferences and Settings

The app may store local settings such as favorites, sorting choices, notification preferences, wallpaper/effect settings, cached popularity values, and feature configuration. Most of this information remains on your device until you clear the app's data or uninstall the app.

Android may back up eligible preferences according to your device and Google backup settings. The app explicitly excludes device-specific or disposable data such as its random installation identifier, pending Firebase statistics queues, selected custom-effect media, WorkManager data, and certain Firebase service metadata from cloud backup and device transfer. Some non-sensitive preferences, such as favorites, may remain eligible for Android backup.

Feedback Email

If you choose the in-app feedback option, the app opens an email application chosen by you and prepares a draft. The draft can include the message that you entered, the app version, Android version/API level, and device manufacturer/model to help diagnose the issue.

Nothing is sent by this feature until you choose to send the email using your email application. Your email provider and our email provider process the message according to their own terms and privacy practices.

Standard Network Information

When the app retrieves a wallpaper, video, preview, effect, sound, or other remote file, the hosting or delivery provider necessarily receives standard network/request information required to deliver that file, which can include an IP address, request time, and user-agent or connection information.

Remote content may be served by third-party hosting providers, including Google-hosted services and HTTPS content hosts used by the app. Their processing is governed by their own privacy terms.

3. Advertising and Consent

The app uses the Google Mobile Ads SDK (AdMob) to display advertising and Google User Messaging Platform (UMP) to request and manage privacy choices where required.

According to Google's disclosures for the Mobile Ads SDK, the SDK may automatically collect and share information such as an IP address, which can be used to estimate general location; app launches, taps, video views, and other product interactions; diagnostic and performance information; and device or account identifiers such as the advertising ID or app set ID where available and permitted.

Google uses this information for purposes that can include advertising, analytics, and fraud prevention. The exact processing can vary according to region, device settings, consent choices, and Google advertising configuration.

Where UMP indicates that privacy choices are required, the app provides a Privacy choices entry so that available consent choices can be revisited. Android also provides system controls for the advertising ID where supported.

4. Firebase and App Integrity

The app uses Cloud Firestore to retrieve app content metadata and popularity information and to synchronize the limited popularity events described in this Policy. Firestore client writes are restricted by application logic and Firebase Security Rules to expected identifiers, allowed fields, timestamps, content references, and bounded counter changes.

Firebase SDKs can automatically process Firebase service metadata needed to provide, maintain, and secure Firebase. Firebase's Android disclosure states that the Firebase user agent can contain device and app/service metadata such as Android OS version, device name/model/brand/form factor, installer information, and Firebase SDK names and versions. Google states that this Firebase user-agent information is used internally for Firebase service operation and improvement and is not linked to a user or device identifier.

The app also uses Firebase App Check with Play Integrity in production. This can process a Play Integrity attestation token and related service information to help verify that backend requests come from a legitimate app installation. Firebase components may also use service-specific installation identifiers when required by their SDK functionality.

The reviewed version does not intentionally integrate Firebase Analytics, Firebase Storage, Flurry Analytics, Facebook login, or an in-app user account system.

5. Permissions and Device Features

The app may use Internet and network-state access to retrieve remote content, communicate with Firebase, and load advertising.

The Set Wallpaper permission is used to apply a wallpaper selected by the user to the home screen, lock screen, or both where Android supports those options.

Notification permission is optional on Android versions that require it. Notifications can be used for wallpaper/drop alerts and for notifications or controls associated with optional features enabled by the user. Related notifications may not be available if notification permission is not granted.

Display over other apps is an optional special access used only for an optional broken-screen visual overlay deliberately activated by the user. Android controls this access through system settings. The effect can be stopped and the special access can be revoked in Android settings.

A foreground service can be used for the user-initiated, time-limited overlay service so that Android can keep the effect controllable while it is active. The service exposes a visible notification or system control when required by Android.

Vibration may be used for optional visual and entertainment effects and tools when enabled.

Legacy shared-storage write access may be used on Android 9 and earlier only when those Android versions require it to save media to shared storage. The app does not request Android's broad “all files access” permission.

The Advertising ID permission may allow Google Mobile Ads to access the Android advertising identifier where the platform, user choices, policy, and advertising configuration permit it.

The live/video wallpaper service is protected by Android's wallpaper-service binding permission and operates as an Android wallpaper service.

Some optional functionality can use the device proximity sensor locally on supported devices. This local sensor use is not uploaded to our Firebase database by that feature.

The reviewed app does not request permissions for contacts, call logs, precise or coarse device location, camera, microphone, broad photo-library access, or Android's all-files access.

6. How Information Is Used

Information handled by the app and its service providers is used only for purposes related to providing and operating app functionality, retrieving and ranking content, remembering user choices, operating optional features selected by the user, displaying and measuring advertising, managing consent choices, preventing fraud and backend abuse, maintaining service security, and diagnosing feedback that the user chooses to send.

We do not sell photos that you select in the app or the feedback messages that you send to us.

7. Sharing and Service Providers

Information may be processed by service providers only as needed for the relevant services. These can include Google services used for advertising, consent management, Firebase/Firestore, Play Integrity, and Google Play functionality; remote content-hosting providers; and email providers when you deliberately send feedback.

A user-initiated share or email action can also transfer content to an application or recipient selected by you. Once content leaves the app through a service or application selected by you, that third party's privacy terms apply.

Information can also be disclosed where reasonably necessary to comply with applicable law, legal process, protect users or the service, investigate fraud or abuse, or as part of a lawful business transfer subject to applicable obligations.

8. Retention and Deletion

Local app data can generally be removed by clearing the app's storage or uninstalling the app. Media that you separately saved to public Pictures or Movies locations is not deleted automatically when the app is uninstalled and must be removed using Android's gallery or file-management tools.

Aggregate Firestore counters and anonymous wallpaper-like records may be retained to preserve popularity totals, prevent duplicate operations, and maintain service integrity. Clearing app data or uninstalling the app does not automatically remove a previously synchronized anonymous Firestore record or aggregate counter. Because the app does not require an account and the random installation identifier is not associated by the app with your contact information, we may not always be able to identify a particular anonymous record as belonging to you after that local identifier is lost.

Feedback emails may be retained for as long as reasonably necessary to respond, troubleshoot, prevent abuse, and meet applicable legal obligations. Google and other service providers apply their own retention rules to information they process.

You may contact us at saif1212kr@gmail.com with a privacy question or deletion request. We may need sufficient information to identify the relevant record, and some anonymous aggregate, security, or legally required records may not be individually identifiable or removable.

9. Security

The app is configured to reject clear-text network traffic, and supported app-controlled remote content references are restricted to HTTPS. Firebase and Google Mobile Ads state that supported collected data is protected in transit using HTTPS/TLS. Firestore Security Rules and application-side validation restrict client writes to the structures and operations expected by the app.

We use reasonable technical safeguards appropriate to the app, but no transmission, device, or storage system can be guaranteed to be completely secure. Communications that you send using an external email or sharing application are also subject to the security and privacy practices of the provider you choose.

10. Children

Broken Screen Wallpaper is intended for a general audience and is not designed specifically for children. We do not knowingly ask users to create an account or provide a child's name, contact list, precise location, camera/microphone data, or broad photo-library access.

If you believe that a child has provided personal information to us through a feedback email, contact us so that we can review the request and take appropriate action. If the app's intended audience, advertising configuration, or legal obligations change, we will update the app and this Policy as needed to apply the appropriate child-directed data and advertising protections.

11. International Processing

Google and other service providers may process information in countries other than the country where you live. Such processing is subject to their applicable privacy terms, contractual safeguards, and legal requirements.

12. Changes to This Policy

We may update this Privacy Policy when app functionality, SDKs, service providers, data practices, or legal and Google Play requirements change. The “Last updated” date will be revised when this Policy is materially updated.

13. Contact

For privacy questions or requests concerning Broken Screen Wallpaper, contact:

lion apps
Email: saif1212kr@gmail.com