RouteWake Privacy Policy

Privacy Policy

RouteWake is a destination based alarm app that alerts users when they approach a selected location. The app is developed by Lasanda Manupiya and is distributed for Android under the package name com.lasanda.routewake.

This policy is intended to help you understand what information the app may use, why it is used, and the choices available to you.

Information We Collect

RouteWake does not require you to create a user account. You can use the app without providing a name, email address, password, or other account registration details.

Depending on how you use the app and the permissions you grant, RouteWake may handle the following information on your device:

• Selected destination locations used to create destination alarms.
• Your device location, when location permission is granted, to calculate distance from the selected destination.
• App preferences and related app data, such as alarm settings or saved destination alarm details.
• A name and date of birth, if you choose to provide them during onboarding, used only to personalise greetings and your in-app avatar.

Selected destinations, preferences, profile details, and related app data are stored locally on your device. They are not transmitted to a server operated by the developer.

Separately, the advertising component of the app collects a limited set of data that does leave your device. This is described in the Advertising section below.

Location Data

RouteWake may request Android location permissions, such as precise location or approximate location, so it can calculate the distance between your current location and a destination you select. Location data from these permissions is used only for the core destination alarm functionality: monitoring your distance to the selected destination and triggering an alert when you approach it.

The GPS location collected under these permissions is processed on your device and is not sent to the developer or to advertising partners.

Please note that the advertising component described below receives your IP address, which may be used to estimate your general area. This is separate from, and much less precise than, the GPS location used for your alarms.

RouteWake does not sell personal data or location data.

Background Location

RouteWake may continue to access location while the app is running in the background, when the screen is locked, or when the app is not actively open. This is necessary for a destination alarm app because the alarm must be able to operate during travel even if you are not viewing the app.

Background location access is used only to support active destination alarms and distance checks for the selected destination. You can control location access at any time through Android system settings.

How Information Is Used

RouteWake uses information for the following purposes:

• To calculate the distance between your current location and your selected destination.
• To trigger a destination based alarm or notification when you approach the selected location.
• To save local preferences and alarm settings on your device.
• To support normal Android app functionality, such as notifications and device services needed for alarms.
• To display advertising in the app, as described in the Advertising section.

The GPS location used for your destination alarms is not used for advertising or profiling, and RouteWake does not sell user data.

Advertising

RouteWake displays advertisements supplied by Google AdMob. Advertising is what allows the app to remain free to use.

To serve and measure ads, the Google Mobile Ads SDK included in the app automatically collects and shares the following with Google:

• Advertising identifiers, including the Android advertising ID and app set ID.
• IP address, which may be used to estimate the general location of the device.
• App interaction data, such as app launches, taps and ad views.
• Diagnostic information, such as app launch time and performance data.

This data is used for advertising, analytics, and fraud prevention and security. It is transmitted in encrypted form. RouteWake itself does not receive or store this data, and the developer does not sell it.

Google's handling of this information is governed by its own privacy policy, which you can read at https://policies.google.com/privacy. Information about how Google uses data from apps that use its services is available at https://policies.google.com/technologies/partner-sites.

Your advertising choices

• If you are in the United Kingdom, the European Economic Area or Switzerland, RouteWake asks for your consent before serving personalised advertising. You can change or withdraw that choice at any time from Settings → Ad privacy options inside the app.
• You can reset or delete your Android advertising ID, or opt out of ad personalisation entirely, from your device's Android settings under Settings → Privacy → Ads.

Data Storage and Retention

RouteWake is designed to store selected destinations, preferences, profile details, and related app data locally on your Android device. Local data remains on your device until you delete it, clear the app data, or uninstall the app.

Data collected by the advertising component is retained by Google according to Google's own retention practices, which are described in its privacy policy. The developer does not control that retention period.

If Android system backups are enabled on your device, Android may handle backup or restore behavior according to your device and Google account settings. RouteWake does not control Android system backup settings.

Data Sharing

RouteWake does not sell personal data or location data. RouteWake does not require a user account, and your selected destinations, saved places and profile details are not shared with a developer-operated backend server.

RouteWake does share data with Google for advertising purposes, through the Google Mobile Ads SDK. The categories of data involved are listed in the Advertising section above.

Information may also be processed by Android or Google services when your device provides system functionality such as location, notifications, maps, or other device services. Those services process information under their own privacy policies and settings.

Third Party Services

RouteWake relies on the following third party services:

• Google AdMob and the Google User Messaging Platform, for displaying advertising and for gathering advertising consent where required.
• OpenStreetMap, for map tiles displayed in the app.
• Android and Google platform services, for location, notifications and other device functionality.

These third party or platform services are governed by their own privacy policies. You can review Google's privacy practices at https://policies.google.com/privacy.

This privacy policy page itself is a static page and does not include analytics scripts, advertising scripts, tracking pixels, cookie banners, or third party libraries.

Permissions

RouteWake may request Android permissions that are necessary for destination alarm functionality, including:

• Location permissions, such as precise location, approximate location, and background location where required by Android, to calculate distance and operate active destination alarms.
• Notification permission, where required by Android, to show alarm or status notifications.
• Foreground service permissions, where required by Android, to keep an active destination alarm running reliably while the app is not in the foreground.
• Internet permission, needed for map tile loading, advertising, location-related platform services, and other network-based device functionality.

You can grant or deny permissions through Android system prompts and can change granted permissions later in your device settings. Some features may not work correctly if required permissions are disabled.

Data Security

RouteWake aims to limit data handling to what is needed for the destination alarm feature and for advertising. Locally stored app data is protected by the security controls of your Android device and operating system. Data sent to Google by the advertising component is encrypted in transit. However, no device, app, or storage method can be guaranteed to be completely secure.

Children's Privacy

RouteWake is not intended to collect personal information from children. The app does not require a user account. If you believe a child has provided personal information through the app, please contact the developer so the concern can be reviewed.

User Rights and Controls

You remain in control of important privacy settings on your device. You may:

• Disable precise, approximate, or background location permissions in Android settings.
• Disable notification permissions in Android settings.
• Change or withdraw your advertising consent from Settings → Ad privacy options in the app, where that option is shown.
• Reset or delete your Android advertising ID, or opt out of ad personalisation, in Android settings.
• Delete saved destinations or preferences using app features where available.
• Clear RouteWake app data through Android settings.
• Uninstall RouteWake at any time.

If you disable location permissions, RouteWake may not be able to calculate your distance from a destination or trigger destination alarms reliably.

If you are in the United Kingdom or the European Economic Area, you also have rights under data protection law in relation to personal data held about you, including rights of access, correction, erasure and objection. Because RouteWake does not operate a server or hold an account for you, requests relating to advertising data are generally best directed to Google using the contact details in its privacy policy. You are welcome to contact the developer using the details below and we will assist where we can.

Changes to This Privacy Policy

This Privacy Policy may be updated from time to time to reflect changes to RouteWake, Android platform requirements, legal requirements, or privacy practices. When the policy is updated, the "Last updated" date at the top of this page will be revised.

Contact Us

If you have questions about this Privacy Policy or RouteWake's privacy practices, please contact: