Dynamic Island — Privacy Policy
Effective date: 13 October 2026
For Google Play listing and in-app publication
Publication note: Before publishing, replace {{SUPPORT_EMAIL}} and {{PRIVACY_POLICY_URL}} with the real public support email and the HTTPS URL where this policy is hosted. Do not publish with placeholders.
1. Overview
This Privacy Policy explains how the Android application “Dynamic Island” (the “App”) accesses, processes, stores, and shares information when you use it. The App is designed to provide a floating, island-style interface for supported notifications, media status, charging information, and other device events.
The App is designed around local, on-device processing. Notification content used by the Dynamic Island feature is processed in volatile memory and is not uploaded by the App’s island code to our servers. The App does not require you to create an account.
2. Information the App Accesses
The App may access limited device information that is necessary to provide its core features. Access occurs only after you enable the relevant Android permission or special access.
Notification content: If you voluntarily enable Android Notification Access, the App can receive eligible notifications posted by other apps so it can display supported notification information inside the Dynamic Island interface. This can include the source app, notification title/text, status, actions, and notification artwork where Android makes those items available.
Media and activity information: For supported media or ongoing activities, the App may process information that Android exposes through notification/media APIs, such as playback state, track information, progress, and available controls.
Device event information: The App may process local device events needed for features such as charging status, screen on/off state, and user-present state.
Preferences and settings: The App stores local preferences such as selected island style, colors, language, appearance, motion settings, notification-preview preferences, and feature toggles.
3. Notification Access — Why It Is Needed
Notification Access is a core permission for the App’s primary function. Without it, the App cannot reliably show supported notifications from other apps in the floating Dynamic Island interface.
When Notification Access is enabled, notification information is processed locally on the device. The App’s island code does not log notification text, save notification content to persistent storage, or transmit notification titles, text, or artwork to AdMob, Firebase Remote Config, or our servers.
Notifications marked by Android as VISIBILITY_SECRET are excluded from processing. Notifications marked VISIBILITY_PRIVATE are redacted when the device is locked or when the App’s privacy/preview settings require redaction. The in-memory notification store is bounded and temporary.
If you use a supported notification action, such as a reply or another action exposed by Android, the App invokes the Android-provided notification action locally. The App does not route the notification content through an independent server.
4. Display Over Other Apps (Overlay Access)
The App requests Android’s “Display over other apps” special access (SYSTEM_ALERT_WINDOW) only so it can draw the floating Dynamic Island capsule above other apps. Android requires you to grant this access manually through system settings.
This permission does not give the App permission to read the visual content of another app, capture the screen, access passwords, or access files belonging to other apps. It is used to position and display the App’s own floating interface.
You can revoke this access at any time from Android system settings. If revoked, the floating overlay feature will stop working until access is granted again.
5. Foreground Service and Ongoing Status Notification
When you enable the Dynamic Island service, the App uses an Android foreground service so the floating capsule can remain available while you are actively using the device. The service is user-initiated and displays an ongoing status notification with a Stop action.
The App monitors screen-off, screen-on, and user-present events so the overlay can hide when the screen is locked or off. The foreground service itself is not used to collect notification content for advertising or profiling.
You can stop the service from the App or from the ongoing notification.
6. Notification Permission
On Android versions that require POST_NOTIFICATIONS permission, the App may request permission to display its notifications, including the ongoing service-status notification. Denying this permission may limit status-notification behavior but does not by itself grant the App access to notification content from other apps.
7. Local Storage and Retention
App preferences are stored locally on your device, primarily through Android local preference storage. These settings remain until you change them, clear the App’s storage, or uninstall the App.
Notification titles, text, and artwork used by the island interface are not persistently stored by the App’s island code. They exist in bounded volatile memory for current functionality and are discarded as events expire or when the process is terminated.
The App does not provide cloud accounts or server-side storage for your notification history.
8. Advertising, Consent, and Third-Party Services
Some distributed versions of the App may include Google Mobile Ads (AdMob), Google User Messaging Platform (UMP), and Firebase Remote Config. Advertising can be controlled by build configuration and remote configuration.
Google Mobile Ads and related Google services may process information such as device or advertising identifiers, IP-derived network information, diagnostics, consent status, and advertising interactions as permitted by your settings, consent choices, applicable law, and Google’s own policies. This processing is performed by Google SDKs rather than by the Dynamic Island notification-processing code.
Where required, the App uses Google UMP to request and manage advertising consent before initializing or requesting advertising that depends on that consent. Privacy options can be made available again from the App settings where required.
Firebase Remote Config is used to obtain configuration values such as feature or advertising settings. The App does not send notification titles, notification text, or notification artwork to Firebase Remote Config.
Google service privacy information is available from Google’s Privacy Policy, advertising technology disclosures, and Firebase privacy documentation.
9. Ads Are Kept Out of Sensitive Contexts
The App is designed so ads are not shown inside the floating Dynamic Island overlay, notification-content UI, permission explanations, notification-access flow, overlay-access flow, onboarding, language selection, privacy views, or reply activity. This separation is intended to prevent advertising from being confused with system controls or sensitive notification content.
10. Data We Do Not Intentionally Collect Through the Island Feature
The Dynamic Island feature does not intentionally collect your contacts, SMS database, call-log database, precise GPS location, photos, videos, files, health data, financial information, passwords, or screen contents.
The App does not sell notification content or use notification text to build advertising profiles.
11. Data Sharing
The App’s island code does not share notification titles, notification text, or notification artwork with advertisers, Firebase Remote Config, or our servers.
If the monetized version is used, Google SDKs may receive technical, advertising, consent, and diagnostic information according to Google’s role as a third-party service provider and according to the user’s consent choices and applicable law.
We may disclose information if required by law or to protect users, the App, or legal rights, but the App does not maintain a server-side notification-content database to disclose.
12. Data Security
We use data-minimization measures intended to reduce privacy risk. Sensitive notification content is handled locally, secret notifications are excluded, private content can be redacted, app backup is disabled, and sensitive app components are configured to limit external access.
Network communications performed by supported Google SDKs use the security mechanisms provided by those SDKs and Android. No method of electronic processing can be guaranteed to be completely secure.
13. Your Choices and Controls
You can control the App by: disabling Notification Access in Android settings; revoking “Display over other apps” access; denying or revoking notification permission; stopping the Dynamic Island foreground service; disabling notification previews or sensitive-content previews where available; changing consent/privacy choices where advertising privacy options are available; clearing App storage; or uninstalling the App.
14. Data Deletion
The App does not require an account and does not maintain a server-side notification history. To delete locally stored App preferences, you can clear the App’s storage in Android settings or uninstall the App. Temporary in-memory notification content is discarded as events expire or when the App process ends.
Information processed independently by third-party Google services is governed by Google’s retention and deletion controls and applicable privacy policies.
15. Children’s Privacy
The App is a general Android utility and is not designed to knowingly collect personal information from children through its own island-processing code. If the App is distributed to audiences that trigger additional child-protection requirements, the developer will apply the applicable Google Play Families and legal requirements for that distribution.
16. International Processing
If the monetized version uses Google services, technical information processed by Google may be handled in countries where Google or its service providers operate. Such processing is subject to Google’s applicable privacy terms and safeguards.
17. Changes to This Privacy Policy
We may update this Privacy Policy when the App’s functionality, SDKs, permissions, or legal requirements change. The effective date at the top of this policy will be updated when material changes are made. The version published in the App and on the Google Play listing should always describe the behavior of the currently distributed version.
18. Contact
If you have questions about this Privacy Policy or the App’s privacy practices, contact:
Support email: zeesigntech017@gmail.com
19. Important Permission Summary
Notification Access (NotificationListenerService): Used to receive eligible notifications for local display in the Dynamic Island interface. Secret notifications are excluded; private content is redacted according to lock-screen and preview settings; notification content is not persistently stored or transmitted by the island code.
Display over other apps (SYSTEM_ALERT_WINDOW): Used only to render the floating Dynamic Island capsule above other apps. It does not authorize screen capture or reading another app’s screen contents.
Foreground service / special use: Used to keep the user-enabled floating island available while the device is in use, with an ongoing status notification and Stop action.
POST_NOTIFICATIONS: Used where required by Android for App/service notifications. It is separate from Notification Access.
Internet/network access (monetized version): Used by Google Mobile Ads, UMP, and Firebase Remote Config. Notification content is not sent to those services by the island code.
20. Play Store / Data Safety Consistency Notice
The Google Play Data safety form must be kept consistent with the exact build distributed on Google Play and with the third-party SDK versions included in that build. If advertising, Firebase, permissions, or data handling changes, this Privacy Policy and the Data safety declaration must be reviewed and updated before publishing the change.