Privacy policy — X Finder MD and X-Map Log

Version 1.4 · Updated 8 October 2026. This policy describes actual data processing in X Finder MD, X-Map Log and the related X-Map account, mapping and community features.

Who is responsible for the data

Controller: LLC “X-Finder” (ТОВ «Ікс Фаіндер»), 26555, Ukraine, Kirovohrad region, Pobuzke, Teatralna Street, building 6, apartment 29. Personal data contact: x.finder.detector@gmail.com.

This policy covers the X Finder MD and X-Map Log mobile apps and their related APIs, account, maps, search logging and community. General online store orders may have separate processing rules.

What data we process

• Account and sign-in: your Google identifier, email address, name and selected profile image/link when you sign in with Google; or your address, password hash, address verification and recovery data when you use email and password. We do not receive your Google password. We also process session data, profile settings and short-lived tokens needed for authentication.
• Location: precise GPS coordinates, time and accuracy for your position, routes and finds. With explicit consent, recording continues while the app is minimized or the screen is locked; points are stored on the phone and synchronized to your account on the X-Finder server. A persistent notification indicates active recording and allows you to stop it. Both apps can start a route manually without a coil. XFinder also supports separately authorized automatic recording when a coil connects: this recording ends on disconnection and its remembered automatic start can be disabled. Disconnecting the coil does not end a separately started manual route. A start point with coordinates, time and accuracy is saved to help return to the route start; it synchronizes to the account when signed in and online.
• Metal detector data: VDI, signal measurements, timestamps and search session parameters. Coil signal processing and sound alerts run on the device. Data is sent to the server when logging is enabled and synchronization occurs. If you separately start and submit a diagnostic signal test, we receive the signal samples, test settings and description you add.
• Data you add: finds, descriptions, categories and photos; routes and search logs; custom maps and their settings; an avatar; community posts, comments, reactions, subscriptions, saved materials and private messages. Community safety: we store the version and time of rules acceptance, your chosen blocks, report reasons, a copy of reported content and moderator decisions. When you report a received private message, that specific message is made available to an authorized moderator for review; this does not grant access to your entire conversation. This data is used to prevent abuse and review reports.
• Push notifications: a Firebase Cloud Messaging token associated with your account and technical delivery information if you enable notifications.
• Technical data: IP address, request time and type needed to operate the web service; session and account security data; and diagnostic information about the app version, device or errors when the app or web map sends an error report. For signed-in users, account-linked visible app-session logs (app, UUID, start, last activity and end times) and coil-connection logs (MAC address, UUID, times and end reason) are processed for usage history and service operation. These are separate logs, not consent to GPS recording. An offline queue synchronizes later after network interruptions. Permanent account deletion removes these server logs and start points.

Android may request access to location, camera, Bluetooth and notifications for the corresponding features. Photos are uploaded only after your action. The apps do not have permission to record from the microphone.

Purposes and legal bases

• Account, sign-in, synchronization, saving finds and routes: to provide the features you request (Article 6(1)(b) GDPR, where GDPR applies).
• GPS, VDI and search data: to display your location, route and signals and synchronize records when you enable these features (Article 6(1)(b)). GPS access is controlled by Android permissions and the app’s logging state; features requiring GPS do not work without permission.
• Community publishing, photos and messages: at your request, to provide the selected feature and display material to your chosen audience (Article 6(1)(b)). Other users can see public materials.
• Push notifications: if enabled, to deliver notifications based on your choice; you can withdraw that choice by disabling notifications in the app or Android.
• Protecting accounts and the service, preventing abuse and diagnostics: for security, reliability and moderation based on the controller’s legitimate interests where permitted (Article 6(1)(f)).
• Compliance with mandatory legal obligations: only where such an obligation applies (Article 6(1)(c)).

An account requires an email address or Google sign-in. Without GPS permission, current location, GPS routes and location assignment to finds are unavailable. Photos, push notifications and community publishing are optional actions.

Public and private materials

You can mark finds and routes as private or publish them. Private materials are not displayed in the public community. After publication, other users can see the published description and location on the map. A private message is delivered to the other participant; after you delete your account, an already delivered copy may remain in that person’s archive marked “Account deleted”.

Who receives data and where it is processed

• X-Finder server: accounts, synchronized GPS/VDI records, finds, photos, routes and community data are stored on the main app server in Ukraine.
• Google: Google Identity is used for sign-in and token verification; Firebase Cloud Messaging is used for push notifications. Google receives the data needed for these features, including sign-in identification data or a notification token.
• Map providers: depending on the selected layer, map requests go to OpenStreetMap, Esri ArcGIS or Protomaps. The provider receives your IP address and requested tile or style parameters; these can identify the map area you view or download for offline use. These requests do not send the provider your entire saved GPS route. Downloaded offline regions and custom layers are stored on the device; availability after downloading depends on the saved coverage.
• Service email delivery: mail.x-finder.com.ua runs on a Contabo VPS in the USA solely as an outgoing SMTP relay for address verification emails and other account operations. It is not the app database or storage for profiles, GPS/VDI records, finds, photos, routes or community materials. Transmission through the mail server processes the recipient’s address, an email with a one-time code or token link and technical delivery information. Retention periods for mail queues and server logs have not been confirmed. As of this policy’s date, DPA/SCC arrangements for the Contabo service have also not been confirmed; we do not claim that specific international transfer safeguards for this hosting have been formalized.

Automatic Contabo backups are disabled and the previous archive there has been deleted. The controller may create manual recovery copies in local working storage; these have no automatic rotation and are deleted manually once no longer needed for recovery. Data deleted from the working system may remain in these copies until they are deleted.

We do not display ads in the apps or use Android Advertising ID for advertising profiles. We do not make solely automated decisions about users that have legal or similarly significant effects.

How long we retain data

• Account data and content you save: while your account is active or until you delete the corresponding materials.
• Once an account deletion request is confirmed, the account is disabled and its public materials are hidden. You can cancel the request and restore the account within 30 days. A reminder is sent 7 days before the deadline; the email also lets you confirm permanent deletion earlier. After permanent deletion, the working server removes the profile and associated data. Instructions and exceptions are described on the account deletion page.
• Already delivered private messages may remain in the recipient’s archive with an anonymized sender.
• Unsent X Finder MD GPS/VDI records may remain in the phone’s local database until synchronization or until app data is cleared/the app is uninstalled. A web request cannot clear this local queue.
• Web server logs rotate daily and are retained for up to 14 rotations. Backend operational events are automatically deleted by type after approximately 7 days for heartbeats, 30 days for errors and 90 days for regular events.
• Service emails and mail system backups may have separate retention periods set by their providers. The recipient controls the copy of an email in their personal mailbox.

Your rights and requests

Where GDPR applies to you, you can request access, correction or deletion, restriction of processing, portability where provided by law, object to processing based on legitimate interests and withdraw consent for features based on consent. You can also complain to the competent data protection authority. Send requests to x.finder.detector@gmail.com; we may request only information needed to verify that you own the account. Do not send your Google password or sign-in codes.

Rights requests are answered without undue delay, normally within one month, with possible extensions in cases provided by law. Account deletion can also be requested through your account in the app/X-Map or through the public account deletion page.

Age and policy changes

The apps are intended for adults aged 18 and over and are not designed for children. If you believe a child has provided personal data to us, contact the address above so we can investigate.

The current policy will be published on this page. If our data processing changes, we will update the text and revision date.