Privacy Policy

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.

1. Information collected and stored

The following is stored on your device and is not transmitted, except your registered places when you turn on Google Drive sync.

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.

Google Drive sync — Google Sign-In · Google Drive API (optional, Pro feature)

If you turn on Google Drive sync in Settings, the app saves your registered places (name, coordinates, radius, direction, alert settings) to your own Google Drive and reads them back, so your places return when you reinstall the app or sign in with the same Google account on another device. Nothing is sent if you do not turn it on.

• Only one permission is requested — drive.appdata (a hidden folder for this app). The app can read and write only the files it created; it cannot see your other Drive files, photos or documents.
• The data is stored only inside your account on Google's servers. It does not pass through the developer's servers, and the developer cannot access it.
• Information received through Google Sign-In (account email, Drive access) is used only for sync, never for advertising, analytics, or sharing with third parties.

The app's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

3. Information not collected

• Personally identifying information such as name or phone number — there is no sign-up (if you turn on Google Drive sync, the account email is stored only on your device)
• Contacts, photos, files, or call logs
• Any server-side accumulation of your routes or location history

4. Why each permission is used

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 on the device
• Places saved in Google Drive — Settings → Google Drive sync → Disconnect, then choose to delete the places stored in Drive. If you already removed the app, delete the app's hidden data in Google Drive on the web → Settings → Manage apps, and revoke access in Google Account → Third-party connections

Because the app keeps nothing on the developer's servers, there is no other 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:

Last updated: November 7, 2026
EarLocAlert · Saechan Suh