UnMiss Privacy Policy

Last Updated: March 28, 2026 | Version: 1.5

Core Statement: UnMiss follows a "local-first" design. Contact configurations, alert rules, alert history, and most app settings are primarily processed locally on your device; however, in scenarios such as feedback submission, crash diagnostics, remote configuration, push notifications, subscriptions, and updates, relevant data or technical information may communicate with third-party services over the network.

1. Overview

Operating Entity: This app is provided and operated by 誇地科技有限公司 (Quoti Technology Limited) (hereinafter referred to as “we”).

This Privacy Policy applies to the UnMiss mobile application (hereinafter referred to as the “App” or “UnMiss”). We value your privacy. This Policy explains how we collect, use, store, protect, and disclose information related to this App.

1.1 Scope of Application

This privacy policy applies to:

UnMiss Android application
All features and services within the application
Relevant data processed through the application

2. Data Collection and Processing Principles

2.1 Local Processing Commitment

Local-First Processing: UnMiss contact configurations, alert rules, alert history, message center content, and most app settings are primarily processed locally on your device, including but not limited to:

✅ Contact names, phone numbers, and app nicknames
✅ Incoming caller numbers and SMS sender numbers (SMS content is not read)
✅ App notification content (used for local alert matching)
✅ Alert history records
✅ User preference settings

However, in the following scenarios, relevant data or technical information may communicate with third-party services over the network: user feedback submission, user-authorized submission of future crash diagnostic information, remote configuration retrieval, push notification reception, subscription status processing, and update checks.

2.2 Data Minimization Principle

We only collect and process the minimum data necessary for normal application operation, specifically including:

Data Type	Purpose	Storage Location	Upload
Contact basic information	Identify important contacts	Local device database	❌ No
App notification content	Match important message alerts locally	Memory (temporary processing)	❌ No
Call/SMS metadata	Trigger alerts	Local device	❌ No
Alert history records	Record alert events	Local device database	❌ No
App settings	Save user preferences	Local device storage (some settings are encrypted)	❌ No
User feedback content and accompanying device information	Handle user feedback and troubleshoot issues	Firebase Firestore and local device cache	✅ Yes (when voluntarily submitted by the user)
Future crash diagnostic information (only after your explicit consent)	Improve app stability	Firebase Crashlytics	✅ Yes (only for crashes that occur after your consent)
Local abnormal-exit detection flag	Prompt you on the next launch about whether to enable crash diagnostics	Local device (app-private storage)	❌ No
Push message identifiers and topic subscription information	Send service-related or subscription-related notifications	Firebase Cloud Messaging	✅ Yes
Technical information related to remote config requests	Retrieve pricing and campaign configuration	Firebase Remote Config	✅ Yes
Technical information related to subscription status	Subscription purchase, status queries, and result synchronization	Google Play and local device cache	✅ Yes
Technical information related to update checks	Check for available updates	Google Play	✅ Yes (a background check runs when entering the Settings page; another check runs if you manually check again)

We do not directly process your full bank card or payment card details. Related payments are handled by Google Play.

3. Permission Usage Description

UnMiss requires the following Android system permissions to function properly. We strictly use these permissions according to their intended purposes:

3.1 Required Permissions

Phone (READ_PHONE_STATE)
- Purpose: Identify incoming call status to identify calls from important contacts
- Data processing: Only read incoming numbers, do not store call content
SMS (RECEIVE_SMS)
- Purpose: Identify received SMS to identify messages from important contacts
- Data processing: Only read sender numbers, do not store SMS content
Call Logs (READ_CALL_LOG)
- Purpose: Assists in identifying incoming caller numbers on certain Android versions
- Data processing: Only used to identify caller ID, does not read or store call log content
Notifications (POST_NOTIFICATIONS)
- Purpose: Required permission on Android 13 and above to display alert notifications and service status notifications
- Usage scenario: Display special alerts for important contacts' calls/messages, and UnMiss service status

3.2 Optional Permissions

Contacts (READ_CONTACTS)
- Purpose: Link system contacts to obtain avatars and phone numbers
- Usage scenario: Only requested when user chooses "Link System Contacts" feature
Notification Access
- Purpose: Read notifications from other apps to identify messages from important contacts
- Usage scenario: Only requested when user adds "App Notification Rules"
- Handling Method: The app reads notification content or related metadata to identify messages from important contacts; notification content is used only for local alert matching and is not directly transmitted externally by this feature. Any related network communication occurs only in third-party service scenarios separately described in this Policy.
Do Not Disturb Access (ACCESS_NOTIFICATION_POLICY)
- Purpose: Used to enable Focus Mode
- Usage scenario: Only requested when user enables "Focus Mode"
Battery Optimization Whitelist
- Purpose: Help keep the UnMiss service running stably and reduce the risk of missed alerts caused by system restrictions
- Usage scenario: Can be configured in the Settings page

3.3 Other System Capabilities and Operational Mechanisms

Installed App Visibility (QUERY_ALL_PACKAGES)
- Purpose: Used to display and select apps installed on the device so that you can configure alert rules for specific apps
- Data Handling: Used only for app matching and rule configuration; your app list is not directly uploaded because of this permission
Network Permission (INTERNET)
- Purpose: Used for communications related to feedback submission, crash diagnostics, remote configuration, push notifications, subscriptions, and updates
Network State Permission (ACCESS_NETWORK_STATE)
- Purpose: Used to detect when network connectivity is restored and to sync locally pending feedback when the network becomes available
Boot Completed Permission (RECEIVE_BOOT_COMPLETED)
- Purpose: Used to restore necessary alert services after device restart or app update so that enabled alert features can continue to function

4. Third-Party Service Integration

4.1 Google Play Billing Service

Purpose: Handle in-app subscription purchases
Data Handling: Google Play handles subscription purchase, renewal, order, and payment-related processes; we only receive subscription status results within the app and do not directly process your complete payment information
Privacy policy: Follows Google Play's privacy policy
User control: Subscriptions can be managed in Google Play at any time

4.2 Firebase Crashlytics (Optional)

To improve app stability and fix potential issues, we provide optional crash reporting functionality:

4.2.1 Information Collected

Crash reports contain the following technical information:

Device Information: Device model, manufacturer, operating system version, screen size, total memory and other hardware specifications
App Information: App version number, build version, package name, specific code location and call stack at crash
System Status: Memory usage, available storage space, network connection status, battery level and other runtime environment data
Time Information: Exact timestamp of crash occurrence (UTC timezone) and app runtime duration
Error Details: Exception type, error message, thread information and related system log fragments

4.2.2 Content We Do Not Actively Write

Under the current implementation, we do not actively write the following content into the crash diagnostic process:

Your contact names and phone numbers
SMS content
Call content
App notification body text
Feedback text that you actively submit

4.2.3 User Choice and Control

Initial Dialog Choices:

Yes: Future crashes will automatically send reports
No: You will still be asked whether to send after crashes
Later: Ask for your choice again after 6 hours

Settings Page Control:

On: Future crashes will automatically send reports
Off: You will still be asked whether to send after crashes

Post-Crash Dialog Choices:

Yes: Will permanently enable automatic crash report sending
No: Will not send this time, still ask on next crash

4.2.4 User Control and Technical Boundaries

⚠️ Crashlytics is off by default and applies only to future crashes

Please note the following facts:

Default state: Firebase Crashlytics is off by default and is enabled only after your explicit consent.
Scope: After being enabled, only crash diagnostic information from crashes that occur after your consent is sent to Firebase Crashlytics.
Local detection: The app may locally detect whether the previous run may have ended abnormally, so it can ask on the next launch whether you want to enable crash diagnostics.
Not the same as sending: Local abnormal-exit detection does not mean that historical crash information has already been sent to Firebase.
No retroactive upload: Even if you consent only after an abnormal exit, previously recorded historical crash information will not be automatically uploaded to Firebase.

4.2.5 Local Abnormal-Exit Detection Mechanism

Local state: The app stores limited local state to determine whether the previous run may have ended abnormally.
Purpose: This mechanism is used only to show a prompt on the next launch about whether to enable crash diagnostics.
Storage location: This state is stored locally in app-private storage on your device.
No retroactive upload: This local state will not cause any previously detected abnormal exit or historical crash information to be automatically uploaded to Firebase if you later consent.

4.3 Firebase Firestore (User Feedback)

Purpose: Handle user-submitted feedback and troubleshoot issues
Collected Content: Feedback content, device information, app version, and time information
Local Cache: If submission fails or the network is unavailable, feedback is first stored locally on the device and automatically synced after the network is restored
User Notice: Please avoid including unnecessary sensitive information in feedback

4.4 Firebase Remote Config

Purpose: Retrieve pricing, campaign, and subscription display configuration
Data Handling: The app requests remote configuration from Firebase, and related technical request information may be handled by Firebase
Scope: Remote Config is not used to upload your contact configuration, SMS content, or alert history

4.5 Firebase Cloud Messaging (FCM)

Purpose: Send service notifications, campaign notifications, and subscription-related messages
Data Handling: Firebase may process device message identifiers (token) and topic subscription information
Grouping Explanation: The app manages relevant topic subscriptions based on subscription status
Local Storage: Received push message content is stored in the local message center for your review

4.6 Google Play Update Check

Purpose: When you enter the Settings page, the app performs a background check for available updates; if you manually check for updates, another query is made
Data Handling: Update check requests are handled by Google Play

5. Data Security Measures

5.1 Technical Security Measures

Local Storage Protection: Contact configurations, alert history, message center content, and similar data are stored in the local device database or app-private storage
Partial Encrypted Storage: Some settings data is stored using Android-provided encrypted storage mechanisms
Permission Minimization: Only permissions required for app functionality are requested
Secure Transmission: Communications with third-party services use HTTPS encryption

5.2 Risk Notice

Risk Notice: No technical system can guarantee absolute security

6. User Rights

6.1 Basic Rights

You enjoy the following rights:

Right to Know: Understand the data processing methods described in this Policy
Right of Access: View locally stored data currently visible within the app
Right to Rectification: Modify or correct contact information and related settings
Right to Deletion: Delete individual contact configurations or single message center messages
Right to Manage Permissions: Grant, revoke, or adjust permissions through Android system settings
Right to Contact Us: Contact us regarding privacy issues, data processing, or deletion requests

6.2 How to Exercise Rights

In-App Controls: You can modify contact configurations, delete individual contacts, and delete single message center messages within the app
System-Level Controls: You can manage permissions, clear app data, or uninstall the app through Android system settings
Contact Us: For requests that cannot currently be completed directly within the app, you may contact us by email

7. Data Retention and Deletion

7.1 Data Retention Principles

Retention by Function: Different types of data are retained for different periods depending on functional needs
Local-First: Most business data is stored locally on the device until you delete it, the system clears app data, or the app is uninstalled
Backup Exception: Uninstalling the app usually removes app data from the device, but if system backup, device transfer, or manufacturer backup services are enabled, some data may still be retained or restored by the system

7.2 Specific Retention Periods

Data Type	Retention Period	Deletion Method
Contact configuration	Until deleted by the user	In-app deletion; system app-data clearing; app uninstall (may be affected by system backup)
Alert history	Stored locally on the device until app data is cleared by the system or the app is uninstalled (may be affected by system backup)	System app-data clearing; app uninstall
App settings	Until modified by the user, app data is cleared by the system, or the app is uninstalled	In-app modification; system app-data clearing; app uninstall (may be affected by system backup)
Local feedback cache	Locally cached feedback records (including feedback content, accompanying device information, time information, and sync status) remain stored on the device until app data is cleared by the system or the app is uninstalled	System app-data clearing; app uninstall
Local message center messages	Up to the most recent 20 messages, until replaced by newer messages, deleted by the user, or app data is cleared by the system	In-app single deletion; system app-data clearing; app uninstall (may be affected by system backup)
Local abnormal-exit detection flag	Stored locally on the device, typically for the abnormal-exit prompt shown on the next launch; removed after the related flow is completed, app data is cleared by the system, or the app is uninstalled	System app-data clearing; app uninstall
Crashlytics crash diagnostic information	Retained according to Firebase/Google policies	Handled according to Firebase/Google policies

After a contact configuration is deleted, snapshots of the contact name or phone number already written into local alert history may still remain in the history records; the current version does not provide an in-app function to delete history records individually, and such history is usually removed only when app data is cleared by the system or the app is uninstalled.

8. Children's Privacy Protection

UnMiss is not specifically designed for children under the age of 13. We do not intentionally collect personal information from children under 13. If we discover, or are informed by a guardian, that such information exists, we will handle it as soon as possible after verification.

9. International Data Transfer

The core contact configurations, alert rules, alert history, and app settings of UnMiss are primarily stored locally on the device.

When you submit feedback, related information is processed through Firebase Firestore
When you agree to send crash diagnostic information for future crashes, related technical information is processed through Firebase Crashlytics
When the app retrieves remote configuration, receives push notifications, processes subscriptions, or checks for updates, related technical requests are processed through Firebase or Google Play
Because the above third-party services may use global infrastructure, related data or technical requests may be processed on servers outside your region

10. Privacy Policy Updates

10.1 Update Notifications

Major changes: Will be prominently prompted in the app
General updates: Update version number and date
Continued use: Continued use of the app indicates acceptance of updated policy

10.2 Version History

v1.5 (March 28, 2026): Based on a review of the current code implementation, refined the descriptions of Do Not Disturb access, Focus Mode, and related reminder mechanisms, and updated the stated purposes of related permissions so that this Privacy Policy remains aligned with the app's current functional boundaries.
v1.4 (March 23, 2026): Added the operating entity; corrected the local-first and third-party service descriptions; added feedback, push notification, remote configuration, permission, backup, and data retention rules; removed inaccurate or unsupported statements.
v1.3 (January 23, 2026): Added Do Not Disturb mode smart detection and reminder notification feature description
v1.2 (January 12, 2026): Simplified permission naming, removed unused Call Phone permission, added Battery Optimization Whitelist description, streamlined contact categories
v1.1 (June 19, 2025): Enhanced crash reporting technical implementation description, corrected reminder timing, optimized data processing explanation
v1.0 (June 4, 2025): Enhanced international compliance, added user rights description, first official version

⚠️ Important Reminder

Although UnMiss follows a local-first design, please note:

Device security, system permissions, and third-party service settings may affect your privacy and data security
If system backup, device transfer, or manufacturer backup services are enabled on the device, some app data may still be retained or restored by the system
Rooted or jailbroken devices may have additional security risks

11. Contact Us

If you need to contact us, please send an email to: contact@quotitech.com

To better serve you, please indicate the issue type in the email subject:

[Data & Privacy] - Privacy policy and data rights related questions
[Technical Support] - Usage issues and other inquiries

Response Time: We will reply to your inquiry within 7 business days

Where applicable under the law, you also have the right to contact relevant data protection regulatory authorities in your jurisdiction to understand your rights.

Thank you for trusting UnMiss!