Geo Privacy Policy
Geo is an Android app that lets users create location-based scenarios and trigger actions such as alarms, ringer changes, notifications, connected-service commands, bot messages, and authorized shared-device location workflows.
Short version: Geo uses location data to make user-created location scenarios work. Background location is used only when the user enables saved scenarios that need to trigger automatically while the app is not open. Geo does not sell personal data.
Developer and contact
Developer: Federico Granato
Contact email: granatojap@gmail.com
Information Geo may collect or process
- Location data: approximate and precise device location may be used to display the map, place markers, monitor geofences, trigger saved scenarios, and support shared-device GPS features when enabled.
- Background location: if the user enables active scenarios, Geo may use location while the app is in the background or closed so that scenarios can trigger automatically.
- Account information: if the user signs in with Google, Geo may process the user ID, email address, and authentication status through Firebase Authentication.
- Scenario data: scenario names, marker names, marker coordinates, radius values, selected days, enabled state, selected actions, and action settings may be stored locally and, when the user is signed in, synchronized with Firebase.
- Shared Devices data: if the user enables location sharing, Geo may store the device name, unique app device ID, last latitude and longitude, last update time, online/offline status, accuracy, and battery level.
- Messaging action data: for LINE and Telegram actions, Geo may store selected recipient identifiers or display names and the message text needed to send the selected action through the configured bot service.
- Google Home data: if the user connects Google Home, Geo may process Google Home structures, rooms, compatible device names, device identifiers, supported commands, and selected commands so that Geo can show and run compatible actions.
- Home Assistant and IFTTT data: if configured, the Home Assistant server URL, discovered entities and commands, and IFTTT event settings may be synchronized. Home Assistant access tokens and IFTTT Webhooks keys are stored only in encrypted local app storage and are not synchronized to Geo cloud storage.
- SmartThings data: after authorization, Geo may process SmartThings locations, rooms, devices, scenes, capabilities, and commands. OAuth access and refresh tokens are stored in the private server-side integration area and are not exposed through the app database.
- Purchase status: Google Play Billing handles subscriptions. Geo receives subscription status and product information, but Geo does not receive or store credit card numbers or full payment details.
- Advertising data: for free users, Google Mobile Ads may process advertising identifiers and related ad-delivery data to show rewarded ads. Where required, Google User Messaging Platform asks for privacy choices before ads are requested.
- Technical data: Firebase, Google Play services, Google Maps, Google Home APIs, and other SDKs may process diagnostics, device or app identifiers, crash/performance-related data, and network request metadata needed to provide their services.
How Geo uses information
- To provide the core location-triggered scenario functionality.
- To monitor active geofences and trigger user-selected actions.
- To synchronize scenarios and shared-device data across authorized devices.
- To authenticate users and protect account-specific data.
- To display maps and location-related UI.
- To send user-configured LINE or Telegram bot messages.
- To list and control compatible Google Home devices after the user grants permission.
- To connect to user-configured Home Assistant, IFTTT, or SmartThings services and execute selected commands.
- To manage Premium subscription entitlement through Google Play Billing.
- To show ads to free users and help keep the free version available.
- To improve reliability, security, and app functionality.
Sharing and third-party services
Geo uses third-party services to operate the app. Depending on the features used, data may be processed by:
- Google Firebase Authentication, Firestore, and Cloud Functions for login, synchronization, backend messaging flows, and shared-device features.
- Google Maps Platform for map display and location UI.
- Google Play Billing for Premium subscriptions.
- Google Mobile Ads / AdMob for ads shown to free users.
- Google Home APIs for compatible Google Home device discovery and control after user authorization.
- Home Assistant APIs for a Home Assistant instance explicitly configured by the user.
- IFTTT Webhooks for events explicitly configured by the user.
- Samsung SmartThings APIs for compatible device and scene discovery and control after user authorization.
- LINE Messaging API and Telegram Bot API for bot-based message actions configured by the user.
Geo does not sell personal data. Geo does not use location data for advertising targeting created by Geo. Third-party SDKs and services may process data according to their own terms and privacy policies.
User choices and controls
- Users can choose whether to grant location permissions. Some core features require location permission.
- Users can disable scenarios, delete scenarios, revoke shared-device access, or stop sharing location.
- Users can manage app permissions in Android settings at any time.
- Users can manage Premium subscriptions through Google Play.
- Users can disconnect or stop using connected-service integrations at any time.
- Where required, users can review advertising privacy choices from Settings.
Data retention and deletion
Geo keeps locally stored settings and scenarios until the user deletes them, signs out, clears app data, or uninstalls the app. Cloud data associated with signed-in accounts is retained as needed to provide synchronization, active scenarios, shared-device features, and connected integrations.
Signed-in users can permanently delete their Geo account and associated cloud data directly from Geo Settings. The Geo account and data deletion page provides the same instructions and an email fallback. Some minimal records may be retained where required for security, legal, billing, or abuse-prevention purposes.
Security
Geo uses encrypted network connections, account-scoped Firestore rules, Android Keystore-backed local encryption for supported integration secrets, authenticated backend endpoints, and server-side secret storage for bot and OAuth credentials. No method of electronic storage or transmission is completely secure, but Geo is designed to limit data access to app functionality and authorized accounts.
Children
Geo is not designed for children and is not intended to target children as its primary audience.
Changes to this policy
This policy may be updated when Geo changes features, integrations, or legal requirements. The effective date at the top of this page will be updated when material changes are made.