DAMA / PRIVACY
Dama Privacy Policy
Effective and last updated: October 2, 2026
This policy explains notification archiving and advertising data practices in Dama (Android package damian.archive), provided by Damian.
Developer and privacy contact
Developer: Damian
Contact email: lsu011127@gmail.com
Google Play developer account display name: Damian Apps
Notification information processed on your device
After you allow notification access and consent to archiving, Dama processes information exposed by notifications from your configured apps: app names and packages, notification titles, senders or conversation names, message text, receipt or display times, available photos or preview images, and notification categories. New notifications can be archived while the app is closed or your device is locked.
Dama cannot obtain records from before installation, content absent from notifications, or text hidden by Android or the source app. When an image is unavailable or unreadable, only text is archived. Animated images are stored as still previews.
Opening the app picker queries the names and packages of launchable installed apps locally. Archive targets, exclusions, viewed status, bookmarks, searches and reply drafts are also handled on your device.
Purpose and handling of message content
Notification information supports your personal archive, search, conversation views, photo and link collections, bookmarks, manual replies, and backup or restore requests. Dama does not upload messages, images, conversation participants, searches or installed-app lists to a developer server or include them as advertising targeting data. Its archive feature has no account system or developer-operated server.
Google AdMob and advertising privacy
Dama uses Google AdMob and the Google User Messaging Platform. Advertising and consent requests communicate with Google. Google may process IP addresses and approximate locations derived from them, device or app identifiers, ad interactions, and diagnostic or performance information for ad delivery, measurement, service analysis and fraud prevention. Google consent forms and privacy options are provided where required.
Dama requests non-personalized advertising. This does not stop all advertising SDK data processing. Identifiers and ad behavior can vary with your device, Android version, Google settings and consent choices. The current app does not declare the Android AD_ID permission.
Advertising data sent to Google is subject to its retention, deletion and international data-processing policies; transmission uses TLS encryption. See the Google Privacy Policy and advertising privacy information for details.
Retention and deletion
Saved messages and images follow your selected retention period. The default is no time limit; settings offer periods such as 30, 90 or 365 days. Bookmarked records are excluded from retention cleanup. Detailed observation data used to interpret notifications expires after seven days and is removed at the next available cleanup opportunity, such as an app launch or service connection.
You can delete individual messages, conversations, app records or the entire archive. Content-free source identifiers and deletion boundaries may remain locally to prevent deleted records from being re-imported. Uninstalling removes app-private device storage. Backups exported elsewhere must be deleted separately.
On-device storage and protection
Messages and notification images are stored in an encrypted device database, with encryption keys protected by Android Keystore. App selections, consent and preferences are stored in Android app-private settings. Automatic system backup is disabled.
App lock is optional and off by default; you can enable device authentication in settings. Screenshots and screen recording are allowed. People with access to your device or shared screens or backup files may see information, so manage your device and exported files carefully.
Backups you choose to export
You can export or restore a backup encrypted with a password you choose. The system file picker lets you select a device folder or cloud provider. Dama does not send backup files or passwords to the developer.
Cloud folders are subject to the selected provider's transfer and retention policies. External backups can remain after you delete the original archive or uninstall the app. The developer cannot decrypt a backup if you lose its password.
Replies and external links
Replies and opening a source app are requested only when you tap the relevant action, using the action offered by the original notification. Reply text is passed to that app and follows its transmission and privacy practices. Opening an archived link uses an external browser or app. Dama does not automatically send messages to other people.
Withdrawal and your choices
Withdrawing archive consent in settings stops new notification collection and storage. Existing records remain and can be deleted separately. You can also revoke notification access in Android settings. Archive targets, exclusions, retention and app lock can be changed in the app.
Where advertising privacy options are available, you can change Google consent choices. Identifier controls follow Android and Google settings. Contact lsu011127@gmail.com for privacy questions. The developer cannot remotely read or delete an archive stored only on your device.
Children
Dama is not designed as a service directed at children. Contact the developer with questions concerning children's personal information.
Information website and inquiries
The information website is hosted by GitHub Pages and can be read without signing in. Opening it may allow GitHub to process your IP address and normal web-request information under its Privacy Statement. The information pages have no additional visitor-analytics integration.
Information and contact details you provide by email are used to answer your inquiry. Your device archive and backup files are not automatically attached.
Policy changes
If data practices change, this policy and its effective date will be updated. When the scope of archive consent changes, new consent is requested before collection starts. The current policy is available in the app and on the information website.