Privacy Policy

1. About This Privacy Policy

This Privacy Policy applies to the Sweet Alarm Android application, package name com.asgenlabs.sweetalarm, developed and published by ASGENLABS.

This policy explains the Android permissions and device capabilities used by Sweet Alarm, how alarm-related information is handled, how advertising services may process information, and what privacy controls may be available to users.

2. Core Alarm Information

Sweet Alarm may store information required to provide alarm and time-management functionality locally on your device.

This information may include:

• Alarm time and schedule
• Repeat preferences
• Alarm labels
• Alarm sounds and volume-related preferences
• Vibration preferences
• Alarm stop-method settings
• Theme and interface preferences
• Timer, stopwatch and other application preferences

Sweet Alarm does not require users to create an ASGENLABS account for normal alarm-clock functionality.

3. Android Permissions and Capabilities

Sweet Alarm requests Android permissions and system capabilities that support reliable alarm delivery and presentation.

4. Internet and Network Connectivity

Sweet Alarm may use Internet connectivity when a feature or integrated third-party service requires network communication.

This includes Google AdMob / Google Mobile Ads when advertisements are requested or displayed.

Internet connectivity itself does not provide Sweet Alarm with access to your camera, microphone, contacts or personal files.

5. Google AdMob and Google Mobile Ads

Sweet Alarm uses Google AdMob / Google Mobile Ads SDK to display advertisements.

Google Mobile Ads is a third-party advertising service provided by Google. According to Google's published Mobile Ads data-disclosure information, the SDK may automatically collect and share certain data for advertising, analytics and fraud-prevention purposes.

This may include:

• IP address, which may be used to estimate the general location of a device.
• User-product interactions, such as app launches, taps and video views.
• Diagnostic information, including information related to application or SDK performance.
• Device and account identifiers, which may include Android advertising ID, app-set ID or other applicable identifiers.

The precise data processed may depend on the Google Mobile Ads SDK version, application configuration, advertising settings, user privacy choices, region and applicable law.

ASGENLABS does not independently sell personal information collected through Sweet Alarm.

6. Advertising Purposes

Information processed through Google Mobile Ads may be used by Google for purposes such as:

• Displaying advertisements
• Advertising measurement
• Analytics
• Application and advertising performance
• Security
• Fraud and abuse prevention

7. Personalized, Non-Personalized and Limited Advertising

The advertising mode used by Google may vary based on region, applicable privacy requirements, user consent, application configuration and user device settings.

Depending on these factors, Google may provide personalized, non-personalized, limited or other supported forms of advertising.

8. Privacy Consent and Google UMP

Where applicable and where implemented in the distributed application, Sweet Alarm may use Google's User Messaging Platform (UMP) or other Google-supported privacy tools to provide required consent notices and privacy choices.

Available options can vary by user region, applicable law, Google advertising configuration and app version.

9. Data Collection and Sharing Summary

Sweet Alarm's core alarm functionality primarily handles alarm-related preferences locally on the user's device.

Third-party SDKs integrated into the application, including Google Mobile Ads, may transmit certain information from the device as described above.

10. Permissions Sweet Alarm Does Not Declare

Based on the Android permission configuration currently provided for Sweet Alarm, the application does not declare permissions for:

• Camera access
• Microphone recording
• Contacts
• SMS messages
• Call logs
• Precise location
• Approximate location
• Calendar

This section may be updated if future Sweet Alarm versions introduce functionality that requires additional permissions.

11. Lock-Screen and Screen-Wake Behavior

Sweet Alarm's alarm experience is designed to support presentation while the device is locked and may turn on the display when an alarm requires attention, subject to Android operating-system rules and user settings.

12. Device Restart and Direct Boot

Certain Sweet Alarm components support Android direct-boot scenarios. This is intended to help preserve or restore alarm functionality around supported device-restart situations.

13. Android Backup and Restore

Sweet Alarm permits Android application backup functionality.

Where backup is enabled and supported, eligible application data may be backed up or restored by Android or the user's configured backup provider according to application backup rules, device settings and the applicable provider's policies.

14. Data Retention

Alarm-related preferences and other locally stored settings may remain on the device while Sweet Alarm is installed.

Local data may be removed when applicable information is deleted, app data is cleared or Sweet Alarm is uninstalled, subject to Android backup and restore behavior.

Information processed by third-party providers may be retained according to those providers' respective policies.

15. Data Security

Sweet Alarm is designed to minimize unnecessary web-facing functionality in its core alarm experience and uses Android platform capabilities for core alarm operations.

ASGENLABS takes reasonable technical and organizational measures appropriate to the application to help protect information handled by Sweet Alarm.

No software, device, network or electronic storage system can be guaranteed to be completely secure in every circumstance.

16. Your Choices and Controls

Depending on Android version, device, region and applicable configuration, users may be able to manage:

• Notification permission
• Exact-alarm access
• Full-screen alarm access where supported
• Advertising ID settings
• Advertising or privacy choices
• Application data
• Battery and background behavior
• Android backup settings

Disabling Android capabilities required by an alarm application may affect Sweet Alarm's ability to deliver alarms reliably.

17. Children's Privacy

Sweet Alarm is a general-purpose alarm and utility application and is not designed specifically to solicit personal information from children.

Where third-party advertising or platform services are used, their applicable age requirements, privacy policies and platform rules also apply.

18. Google Play Data Safety

Sweet Alarm's Google Play Data Safety disclosure is intended to reflect the application's actual data practices, including relevant behavior of third-party libraries and SDKs included in versions distributed through Google Play.

If Sweet Alarm's permissions, SDK configuration, features or data practices change, ASGENLABS may update both this Privacy Policy and applicable Google Play disclosures.

19. Third-Party Services

Third-party services integrated into Sweet Alarm may process information according to their respective privacy policies, terms and technical configurations.

Users are encouraged to review applicable Google privacy information relating to Google Mobile Ads and other Google services used by the app.

20. Changes to This Privacy Policy

ASGENLABS may update this Privacy Policy when Sweet Alarm's functionality, Android permissions, advertising configuration, third-party integrations, legal requirements or privacy practices change.

Updates will be published on this page and the last-updated date may be revised when appropriate.

21. Contact Us