Deki Privacy Policy
Effective date: October 19, 2026
Deki is an Android lock screen notification app. This policy explains what information Deki may access, how it is used, what stays on the device, and what may be processed by Google SDKs used for ads, analytics, crash reporting, remote configuration, and push notifications.
1. Core Principles
- Deki does not use notification contents for advertising targeting.
- Deki does not upload notification contents, sender names, profile images, notification history, or the wallpaper photo the user picks to Deki servers.
- Deki does not sell notification data.
- Deki does not currently collect payment information, financial information, or purchase history.
- Google SDKs used for ads, analytics, crash reporting, remote configuration, and push notifications may process the data described below according to Google's policies.
- Deki uses an approximate location, rounded to about 10 km, only when the user turns on lock-screen weather, and does not collect precise location.
2. Information Deki May Access
Deki may access the following information only after the user enables notification access in Android settings:
- App name or app icon of the notification sender
- Notification title and text
- Sender name shown in messenger notifications
- Notification icons, large icons, or profile images
- Notification time and notification identifiers
- Android PendingIntent used to open the original notification app or screen when the user taps a notification
Deki may also store app settings locally for lock screen display and feature state:
- Lock screen enabled state
- Clock, date, font, size, position, and weight settings
- Wallpaper, theme, and opacity settings
- Notification archive, notification history, app filter, and retention settings
- The wallpaper photo the user picks and depth-effect settings
- Whether lock-screen weather is on, and the most recently received weather information
If the user turns on lock-screen weather and grants location permission, Deki accesses the device's approximate location to get the current weather. See section 6 for details.
3. How Deki Uses Information
Deki uses the information above only for these purposes:
- Showing notifications on the Deki lock screen
- Showing messenger app names, sender names, and profile images
- Opening the original app or a safe fallback app route when the user taps a notification
- Providing notification archive and notification history features
- Keeping selected notifications after reboot when the user enables that setting
- Saving lock screen theme, clock, wallpaper, and other user settings
- Showing lock-screen weather and providing the wallpaper photo depth effect, when the user turns them on
- Recording privacy-safe diagnostics to improve app reliability
4. Local Storage and Deletion
Notification information is stored locally on the user's device using Android app storage and a Room database. Profile images or icons may be saved in the app's internal files directory.
The wallpaper photo the user picks is stored only in the app's internal storage and is not sent to Deki servers. The depth effect, which places the subject of the photo in front of the clock, is processed on the device using Google ML Kit subject segmentation, and the model it needs is downloaded by Google Play services. Clearing the app data or uninstalling the app also deletes the wallpaper photo.
Stored data is removed when:
- The user deletes notifications inside Deki
- The configured retention period expires
- The user clears Deki app data
- The user uninstalls Deki
Notification archive and history features may have maximum item limits and retention limits.
Clearing app data or uninstalling Deki removes notification information and settings stored locally by Deki. Advertising, analytics, diagnostics, or app-installation identifiers already processed by Google AdMob or Firebase may be retained or deleted separately under Google's policies and retention periods. Uninstalling the app does not guarantee their immediate deletion.
5. Permissions
Deki may request or guide the user to enable these permissions:
- Notification access: used to read notifications for lock screen display, archive, and history features
- Notification permission: used for foreground service notifications, fallback notifications, update notices, and advertising notifications for which the user has explicitly opted in
- Display over other apps: used to show the Deki lock screen quickly when the screen turns on
- Battery optimization exclusion: used to keep lock screen behavior stable
- Full-screen display permission: used to show the user-enabled Deki lock screen above the system lock screen when direct activity launch is restricted. On supported Android versions, the user can manage this permission directly.
- Network state access: used by Google SDKs such as Google AdMob and Firebase to check network connectivity. Deki does not read network traffic contents.
- Boot completed: used to restore lock screen behavior after device reboot
- Wake lock: used briefly for lock screen timing
- Foreground service: used to observe screen state and keep the user-enabled lock screen feature stable
- Approximate location: used only to get the current weather when the user turns on lock-screen weather in Customize. Deki does not request precise location permission.
- Set alarm (SET_ALARM): used to open the Clock app's timer screen from the timer shortcut on the lock screen
- Turn screen on (TURN_SCREEN_ON): used to turn on the screen when a new notification arrives so that the notification can be shown on the Deki lock screen
Users can disable notification access or other permissions at any time in Android settings. Some app features may stop working after permission removal.
6. Lock-Screen Weather and Location
Lock-screen weather is optional and off by default. It works only if the user turns it on in Customize.
When weather is turned on, Deki requests Android's approximate location permission. Deki does not request precise location (GPS) permission.
Deki rounds the device's location to about 10 km and sends only that rounded location to the Deki weather server (weather.bymysidelabs.com) to get the current weather. Weather is refreshed at intervals only while the lock screen is showing.
The Deki weather server does not store or log the location it receives, and the location is not used for advertising. Only the most recently received weather information is stored on the device.
Weather data is provided by the Norwegian Meteorological Institute (MET Norway) under the CC BY 4.0 license. The Deki weather server requests weather data from MET Norway using only the rounded location and does not pass on any information that identifies the user.
Users can turn weather off in Customize, or revoke Deki's location permission in Android settings, at any time.
7. Ads
Deki shows Google AdMob banner ads at the bottom of the Customize and Settings screens. All Deki features are free, and there are no rewarded ads or paid premium features.
In regions where consent for ads is required, Deki uses Google User Messaging Platform (UMP) to obtain the user's consent, and advertising information such as the advertising ID is processed according to the user's choices. Users in those regions can change their choices at any time under “Ad privacy settings” in Deki Settings.
Google Mobile Ads SDK may process data such as advertising ID, app interactions, ad impressions or clicks, diagnostics, device information, network information, and approximate location inferred from IP address according to Google's policies and the user's ad settings.
Deki does not send notification titles, notification contents, sender names, profile images, or notification history to Google AdMob for advertising targeting.
Approximate region may be inferred from an IP address for advertising and fraud prevention. Deki does not use the approximate location obtained for lock-screen weather for advertising or pass it to Google AdMob, and does not request precise GPS location permission or collect precise location.
8. Analytics, Crash Reporting, Remote Config, and Push Notifications
Deki uses Firebase/Google Analytics, Firebase Crashlytics, Firebase Remote Config, and Firebase Cloud Messaging to improve app quality, respond to release issues, configure features, and deliver benefit or promotional messages when the user has consented.
These services may process:
- App version and version code
- Android version, device manufacturer, and broad device model family
- App language, country/region, and theme
- Product-flow events such as screen views, settings changes, and permission steps
- Privacy-safe diagnostic codes such as lock screen launch delay, system authentication error, or notification open failure
- Crash, ANR, stack trace, and app stability information
- Remote configuration values for update notices or feature flags
- Firebase installation identifiers and app-version information needed to deliver push notifications
- Notification interaction information such as whether a benefit or promotional message was opened or dismissed
Deki analytics and diagnostics are designed not to include notification title, notification text, sender name, app package name, notification key, profile image, or user-entered text.
Service/update notices and advertising information may be introduced in one continuous notification setup flow. However, Deki does not treat Android notification permission itself as consent to receive advertising information. Advertising notifications are shown only after Deki clearly identifies their advertising purpose and the user gives explicit prior consent in the app. The Android notification permission dialog may then appear once as the next step. Users can withdraw advertising consent in Deki Settings or block all Deki notifications in Android Settings. Where required by regional law, nighttime advertising requires separate consent or is suppressed. Service update and permission notices may still be shown independently from advertising consent.
Advertising notifications include an advertising label, sender information, and an opt-out method. Deki may count privacy-safe received, posted, and opened states without attaching the notification title, body, URL, or message identifier to those analytics events.
9. Payment and Financial Information
Deki does not currently use the Google Play Billing SDK, and does not collect or upload payment information, financial information, or purchase history to Deki servers.
All Deki features are provided free of charge, and there are no paid premium features or rewarded ads.
10. Third-Party Processing
Deki does not send notification contents to Deki servers or third-party servers.
The following Google services may process data for service delivery, advertising, analytics, diagnostics, fraud prevention, security, and compliance:
- Google AdMob
- Firebase Analytics / Google Analytics
- Firebase Crashlytics
- Firebase Remote Config
- Firebase Cloud Messaging
- Google Play services (including Google ML Kit)
For more information, review:
- Google Privacy Policy: https://policies.google.com/privacy
- Privacy and Security in Firebase: https://firebase.google.com/support/privacy
- Firebase Android data disclosure: https://firebase.google.com/docs/android/play-data-disclosure
- Google Mobile Ads SDK data disclosure: https://developers.google.com/admob/android/privacy/play-data-disclosure
11. Security
Deki stores notification data inside the app's private storage area. Data processed by Google SDKs is encrypted in transit. Users should still treat notification history as sensitive because notification contents may include personal messages or private information.
12. User Choices and Rights
Users can disable notification access, notification permission, display over other apps, full-screen display, or battery optimization exclusion at any time in Android or Deki settings. Users can delete stored notifications, clear app data, and withdraw advertising-information consent under “Offers and ads” in Deki Settings. Turning off Android notification permission blocks all Deki notifications, including updates and advertising.
13. Children
Deki is not designed for children. Notifications may contain personal or sensitive information, so guardians should manage device permissions and app use.
14. Contact
For privacy questions, contact:
Operator: By My Side Labs
mark@bymysidelabs.com