Application Legal & Privacy

AlarmNest Privacy Policy

Application: AlarmNest (in.bitmask.alarmnest) Developer: BitMask LLP / Bitmask Technologies Last updated:

This Privacy Policy explains how BitMask LLP ("we", "us", or "our") collects, uses, and discloses information when you use the AlarmNest mobile application ("App"). This policy is designed to meet the strict requirements of the Google Play Store, specifically regarding prominent disclosures for sensitive data such as location.

Your use of the App is also subject to our general BitMask Privacy Policy and the AlarmNest Terms & Conditions.

1. Data Collection and Usage

AlarmNest is primarily an on-device application. We do not require you to create an account to use the core features, and we do not collect personal information like your name or email address unless you optionally use Google Sign-In to sync your settings across devices.

2. Prominent Disclosure: Location Data Access, Collection & Use

Google Play Location Data Policy Disclosure

Prominent Disclosure: Location Data Access, Collection & Use

AlarmNest accesses, collects, and processes device location data—including precise GPS location (ACCESS_FINE_LOCATION), approximate location (ACCESS_COARSE_LOCATION), and background location (ACCESS_BACKGROUND_LOCATION).

  • What Location Data is Collected: Real-time latitude/longitude coordinates, map pin coordinates, and geofence boundary radii configured by the user.
  • Why Location Data is Needed (Purpose & Use): Location data is accessed and monitored—even when the app is closed, backgrounded, or not in active use—solely for the core function of detecting when your device enters or leaves your configured geofences (arrival/departure triggers) and sounding location-based alarms.
  • Sharing & Data Privacy: Location data is never sold, rented, or shared with third-party ad networks, data brokers, or marketing entities. Coordinates are shared strictly with Google Maps SDK to render map interfaces and enable place searches.
  • Local Storage: Geofence evaluation occurs locally on your device. Location logs are not transmitted to or stored on external servers.
  • User Permission Control: Location permissions are opt-in. You may grant or revoke location permissions at any time via Android device settings (Settings → Apps → AlarmNest → Permissions → Location).

3. Comprehensive Device Permission Disclosures

To deliver precise alarm timing, full-screen lock-screen notifications, and location-triggered alerts, AlarmNest requests specific Android permissions.

A. Location & Geofencing Permissions Sensitive Data

android.permission.ACCESS_COARSE_LOCATION
Approximate Location

Accesses network-based location for initial map positioning and general area selection.

android.permission.ACCESS_FINE_LOCATION
Precise GPS Location

Accesses precise GPS coordinates to detect exact arrival or departure at user-defined geofenced zones.

android.permission.ACCESS_BACKGROUND_LOCATION
Background Location Access

Allows location monitoring when the app is closed or backgrounded so location alarms trigger on arrival or departure.

android.permission.FOREGROUND_SERVICE_LOCATION
Location Foreground Service

Supports continuous adaptive GPS tracking for location-triggered alarms when tracking mode is enabled.

B. System Wake & Alarm Permissions

We also require several non-privacy sensitive permissions to ensure alarms ring correctly, including SCHEDULE_EXACT_ALARM, USE_EXACT_ALARM, POST_NOTIFICATIONS, USE_FULL_SCREEN_INTENT, WAKE_LOCK, and foreground service permissions for media playback. These are strictly used for sounding the alarms as disclosed in our Terms & Conditions.

4. Third-Party Integrations & Content

AlarmNest integrates the following third-party SDKs and service providers which may collect data according to their own privacy policies:

  • Google Maps SDK & Places API: Used for map display and location searches. Use is subject to the Google Privacy Policy.
  • Firebase Authentication: Manages optional Google Sign-In authentication.
  • Google AdMob: Serves banner ads and rewarded video ad units. AdMob may use advertising IDs to serve personalized or non-personalized ads.
  • Google Play Services: Powers Play Billing, location providers, and system exact alarm APIs.

5. Contact Information

If you have questions, feedback, or concerns regarding this Privacy Policy, please reach out to us:

BitMask LLP / Bitmask Technologies

Package Name: in.bitmask.alarmnest

Support Email: support@bitmask.in / hello@bitmask.in

Location: Thane, Maharashtra, India