Privacy Policy
EarLocAlert · Android · iOS
EarLocAlert ("the app") alerts you by vibration or earphone sound when you arrive at or leave a place you registered. This document explains what the app handles, what it sends outside your device, and what it does not.
All location matching happens on the device. The app does not transmit your coordinates or movement history to any server. The developer cannot see where you have been.
1. Information collected and stored
The following is stored only on your device and is never transmitted.
| Item | Purpose | Retention |
|---|---|---|
| Current location (latitude/longitude) | Determine arrival at or departure from registered places | Only while needed for matching; not stored separately |
| Registered places (name, coordinates, radius, alert settings) | Manage alert targets | Until you delete them |
| Arrival/departure history | Prevent duplicate alerts, review past alerts | Deleted automatically after 90 days |
| Activity log (diagnostics) | Investigate why an alert did not arrive | Up to 2 MB; oldest entries removed beyond that |
| App settings (alert volume, vibration strength) | Preserve your preferences | Until you uninstall the app |
The activity log includes the coordinates used for matching. It is stored in the app's private storage where other apps cannot read it, and leaves the device only when you tap "Export" yourself — in which case you choose the destination.
2. Information transmitted outside the device
The app communicates externally only in the following cases.
Advertising identifier — Google AdMob
The app shows a full-screen ad after you dismiss an alert and a banner ad at the bottom of the home, settings and place screens, using the Google AdMob SDK. AdMob collects and transmits your advertising ID (AAID on Android, IDFA on iPhone) and device information to serve and measure ads.
This processing follows Google's policies: Google Privacy Policy · AdMob policies
You can reset or delete your advertising ID in Android Settings → Privacy → Ads.
On iPhone, manage tracking permission in Settings → Privacy & Security → Tracking. If you do not allow it, your advertising ID (IDFA) is not shared.
Place search queries — Google Places API
If you search for a place by name when registering it, the search text you type is sent to the Google Places API to retrieve candidates. Nothing is sent if you do not use search.
Only the search text is sent; your current location is not included.
Map display — Google Maps SDK
The Google Maps SDK requests map data to render the map screen, subject to Google's Maps service terms.
3. Information not collected
- Personally identifying information such as name, email, or phone number — there is no sign-up
- Contacts, photos, files, or call logs
- Any server-side accumulation of your routes or location history
4. Why each permission is used
| Permission | Reason | If denied |
|---|---|---|
| Location (precise) | Determine arrival at and departure from registered places | The app's core function does not work |
| Background location | Required to alert you without opening the app | Alerts work only while the app is on screen |
| Notifications | Display arrival and departure alerts | No alerts are shown |
| Ignore battery optimization | Deliver alerts on time even in power-saving states | Alerts may be delayed or missed |
| Display over other apps | Show the alert screen while you use another app | Only a notification appears |
| Full-screen notification | Show the alert screen when the display is off | Only a notification appears |
Battery optimization exemption, display over other apps, and full-screen notification are optional. The app works with notifications and vibration if you decline them.
5. Deleting your information
- Registered places — delete individually in the app
- Activity log — Settings → Activity log → Clear
- Everything — uninstalling the app removes all stored information
Because the app keeps nothing on a server, there is no data held by the developer to request deletion of.
6. Children
This app is not directed to children under 13 and does not knowingly collect information from them.
7. Changes to this policy
Changes will be posted on this page with an updated date. Changes that add collected items or transmission destinations will be announced together with an app update.
8. Contact
For questions about privacy, please contact:
| Data controller | Saechan Suh (서새찬) |
|---|---|
| Contact | chan4760@gmail.com |
Last updated: October 2, 2026
EarLocAlert · Saechan Suh