Privacy Policy
This policy explains how MBCSOFT LLC ("we", "us") processes personal information when you use EasyGeoFinder. Features and data processing vary by platform, version, permissions and the services you use. Our contact details appear below.
1. Information we process
- Account information: your phone number, device identifier, account status and registration/activity timestamps. The updated iOS app offers phone-based sign-in for location sharing and sharing permissions. It no longer offers new Apple or Google sign-ins. Existing sessions created in earlier versions may continue to use Firebase Authentication to preserve access to the same service records. Earlier account records may include an email address (including an Apple relay address), provider identifier and profile name. We do not receive your Apple or Google password.
- Location and activity: precise coordinates, recorded times, location history, derived addresses, saved places and entry/exit events. Where available, related records include speed, movement/activity status, battery level, charging status, sound mode and indicators of simulated location. Background location may be collected when the app is not on screen if the relevant device permission is enabled.
- Sharing information: phone numbers or identifiers you enter to connect with other users and the location-sharing permissions you manage. This does not mean we upload your entire address book.
- Notification information: on supported iOS versions, Firebase Cloud Messaging registration tokens, installation identifiers, the associated account, platform, language preference, registration state and timestamps. Notifications about a saved place can include the relevant phone number and place name.
- Subscription information: purchase and subscription identifiers, selected plan, entitlement and renewal status, and transaction information provided by the store and RevenueCat. Payment card details are handled by the store and are not entered into EasyGeoFinder.
- Technical and usage information: network/IP information, approximate country derived from IP, device/app details, diagnostics, crash reports, and events such as sign-in and purchases. The updated iOS app does not supply your email address, an email-derived user identifier or your phone number to Google or Meta for advertising matching. It clears previously configured Analytics user IDs and Meta matching data from its SDK settings. This does not itself delete information already processed by those providers in earlier versions. Usage and advertising measurement may still use device or installation identifiers and event information subject to applicable permissions and SDK settings.
- Support information: information you provide when contacting us, including your contact details and the content of your request.
2. Why we use information
We use this information to authenticate accounts, associate devices, provide location sharing and history, process saved-place events, deliver notifications in the selected language, manage subscriptions, respond to support and deletion requests, troubleshoot failures, measure usage and purchases, and protect the service against misuse.
Where data protection law requires a legal basis, processing needed to provide a requested service is based on the contract with you; optional processing requiring consent relies on that consent; security, troubleshooting and service administration may rely on legitimate interests where permitted; and legally required processing relies on the applicable obligation. Required location and tracking permissions are handled separately from acceptance of our service terms. A device permission does not replace another person's consent to share their location.
3. Recipients and service providers
- Other users: location-sharing features disclose location, related status and saved-place information to other users through the application's sharing features. Review the people you connect with and your sharing permissions.
- Apple and Google/Firebase: platform services, store transactions, diagnostics, analytics, and authentication for existing sessions from earlier app versions. iOS notifications in version 2.0.5 use Firebase Cloud Messaging and Apple Push Notification service (APNs). The former OneSignal integration has been removed from this version; older installed versions may still contain its SDK.
- IPWHOIS.IO (ipwho.is): the app makes an encrypted request to estimate its network's country for regional measurement settings. This provider receives the connection's public IP address and may process network and request information under its privacy policy. We request only a success indicator and country code; the request does not include your phone number, email, GPS coordinates, device identifier or account token. The country decision is held temporarily in app memory and is not treated as your consent or as proof of your residence.
- RevenueCat: subscription and entitlement management using store purchase information and an app user identifier.
- Google Maps and OpenStreetMap/Nominatim: maps and coordinate-to-address lookups. Relevant map or coordinate information and network information may be sent to the provider when these features are used. A map application you choose to open receives the destination you select.
- Google Analytics for Firebase, Firebase Crashlytics and Meta/Facebook App Events: usage measurement, diagnostics and purchase/sign-in measurement. These services may process identifiers and event information according to their SDK settings and applicable permissions. New phone sign-ins are measured as events without sending the entered phone number as an analytics event parameter. Earlier app versions may have used email-derived identifiers or email matching; hashing does not make such information anonymous.
- Hosting and operational tools: our hosting and database infrastructure processes service records. Operational alerts sent through Telegram can include account email or phone number, device identifier, approximate country and subscription events, depending on the event. These alerts are used by our operational team.
We may disclose information when legally required, to address fraud or security incidents, or as part of a business transfer subject to applicable data protection requirements. Providers may process data in countries other than yours. Applicable transfer requirements and protections depend on the provider and the relevant data protection law.
Provider information: Firebase privacy, Google privacy, Apple privacy, RevenueCat privacy, Meta privacy, IPWHOIS.IO privacy, OpenStreetMap privacy, and Telegram privacy.
4. Permissions and your choices
You can change location, background location and notification permissions in your device settings. Disabling a permission can prevent the related feature from working; disabling notifications does not itself disable location collection. You can review sharing permissions in the app. Entering a phone number does not by itself grant access to another person's location; the app's sharing-permission flow still applies. Information already received by another person may remain on that person's device.
On iOS, tracking permission is managed through Apple's tracking prompt and Settings. This is separate from location and notification permission. Crash diagnostics and information needed to operate your account are distinct from advertising tracking. Contact us with questions about analytics or to exercise applicable objection and withdrawal rights.
The updated app applies regional checks to Meta event measurement as well as Google's advertising measurement settings. Meta advertising identifier collection and automatic app-event logging also depend on Apple's tracking permission. Regional eligibility is not treated as consent. These measurement settings do not change your subscription entitlement or location-sharing permissions.
Notification text may be visible on a lock screen or on connected devices, depending on your Apple/device settings. Configure notification previews if you do not want that content displayed.
5. Retention, deactivation and deletion
We retain account, location and other personal records for as long as needed for the purposes described here, with a maximum retention period of six years unless a specific legal obligation requires otherwise. Retention and deletion are managed manually; uninstalling the app, signing out or deactivating an account does not automatically erase server records.
The in-app account control currently deactivates the account; it does not perform permanent data deletion. You can request permanent deletion of your account and associated personal and location records by emailing info@mbc-soft.com. Requests are handled manually. Once your request and account ownership have been verified, we complete deletion of the relevant records under our control within 60 days, subject to specific legal retention obligations. Shorter deadlines required by applicable law take precedence. Include enough information to identify the account, such as its registered phone number or an email used to sign in with an earlier version; never send a password or verification code. We may need to verify ownership before acting.
Some records may need to be retained to meet a specific legal obligation or resolve a dispute; where relevant we will explain this in response to your request. Service providers' independent records and backups are subject to their applicable retention rules. Deleting an EasyGeoFinder account does not automatically cancel an Apple or Google subscription; cancellation is managed separately through the store.
6. Your data protection rights
Depending on the law that applies to you, you may have rights to access, correct, delete or obtain a copy of your information, restrict or object to processing, withdraw consent, and complain to a competent data protection authority. Contact us using the details below to make a request. Withdrawing consent does not affect the lawfulness of earlier processing.
7. Children
The service is not directed to children under 13. Do not submit a child's personal information in circumstances that require verified parental consent unless the applicable requirements have been met. If you believe a child under 13 has provided information without the required authorization, contact us so that we can investigate and address the records.
8. Security and policy changes
No internet service or device can guarantee absolute security. Protect your account and device and report suspected unauthorized access to us. We may update this policy as the service changes. The date above identifies the current version; material changes and any necessary consent will be handled as required by applicable law.
9. Contact
MBCSOFT LLC is responsible for the processing described in this policy. Email info@mbc-soft.com, or write to 8 The Green, Suite A, Dover, DE 19901, United States.