Find Lost Device Track Locator

Find Lost Device Track Locator helps you find nearby Bluetooth devices and plan a search. This policy explains the information used by the app and its services. For questions or requests, use our support form.

Bluetooth and location

The app reads nearby Bluetooth advertisements, including device names, signal strength, manufacturer information and supported service identifiers. Your saved devices, local names, favorites, sightings and finds are stored on your phone or tablet. Scanning and Guard operate while you use the app; it does not provide a background location-tracking service.

Location access is optional. With permission, the app records where your phone saw a Bluetooth signal and uses the operating system's geocoding service to show a place name. Without permission, history can retain the time without a place. Opening Maps or sharing a result passes the information you select to that service or recipient.

Find Assistant and device identification

AI features contact our server only when you request them. A search-plan request includes your answers, device category and, when available, the last-seen time and place from matching device history. Identification sends the selected device's advertised name, manufacturer and service information, category and signal readings. Follow-up questions and content reports are also sent to our server.

We use OpenRouter and OpenAI to process AI requests and generate responses. Avoid entering passwords, financial information or other private details. Suggestions can be wrong and do not establish a device's ownership or whether someone is following you.

Firebase creates an anonymous account for AI access. An installation identifier and public verification key associate requests with your installation. Firebase App Check and signed requests help prevent unauthorized use. The server uses request timing, usage counts, cost and a network-address-derived identifier to enforce limits and investigate abuse. Connections necessarily expose a network address to the services carrying them.

Purchases and analytics

Apple or Google processes purchases and payment details. The app reads store product and entitlement information to provide paid features and restore access; it does not receive your payment-card details. On iOS, Qonversion also observes purchase receipts.

Firebase Analytics and Crashlytics receive app interactions, installation/device information and diagnostic reports to help understand usage and failures. On iOS, AppsFlyer receives install, app-event and in-app purchase information for attribution and usage measurement; the tracking permission below decides which identifiers it may use. Firebase Analytics and Qonversion do not collect advertising identifiers. On Android, the app collects no advertising ID and does not use AppsFlyer. The app does not display third-party advertisements.

Tracking permission on iOS

While Usage analytics is on, iOS asks once whether the app may track your activity across other companies' apps and websites. The request appears on the Nearby tab after onboarding and the plan offer close, once you have answered the Bluetooth permission request. If you completed onboarding earlier and iOS has no recorded answer, it appears the next time you open Nearby.

Allow: while usage analytics is on, AppsFlyer receives your device's advertising identifier (IDFA) and the

app's vendor identifier (IDFV). It attributes installs, app events and in-app purchases to the advertising campaign that led to the install and may share that attribution result with the advertising network that ran the campaign.

Ask App Not to Track, tracking restricted on the device, or no answer yet: AppsFlyer runs without the

advertising identifier or vendor identifier, and sharing with advertising partners is blocked.

Storage and deletion

Local sightings are limited to 30 days or 5,000 records. Device choices and saved search plans stay on your device until you remove them or the app's local data. Deleting a saved plan removes the local copy; it does not by itself delete the server copy.

Our server removes AI request and response content after 30 days and content reports after 90 days. In Settings, Cloud AI data lets you export your server data or request its deletion. Deletion removes AI content and reports associated with the anonymous account and then deletes that Firebase account. If interrupted, the app retains the deletion request so you can retry. AI stays disabled until you explicitly restart it with a new identity.

Minimal account/installation identifiers and security, usage and deletion records may remain to enforce deletion and service limits; deleted AI content is not restored by those records. Service providers process information under their own applicable retention practices. Support messages are kept as needed to handle the request. Use the support form for access, correction or deletion requests, including requests after you stop using the app.

Cloud deletion does not erase local device history or saved plans and does not cancel a subscription. Manage subscriptions in your Apple or Google account. No purchase is required to reach the app's privacy, support or cloud-deletion controls.

Your choices

You can deny or revoke Bluetooth and location permissions in system settings, and change the iOS tracking permission in iOS Settings at any time. Turning off Usage analytics in the app's Settings stops Firebase Analytics, crash collection and all AppsFlyer collection, including after you allowed tracking. Store entitlement checks, Qonversion receipt processing and security needed for AI still operate. You can also remove locally saved plans, export or delete cloud AI data, and stop using AI without losing the local Bluetooth tools.

Data may be processed in countries where our service providers operate. We use HTTPS, authenticated requests and access controls to protect data in transit and restrict access.