FinderCat

FinderCat — Privacy Policy

Policy last updated: September 23, 2026.

FinderCat helps you find nearby Bluetooth devices using radio signal strength. The app works locally on your device and does not require an account. FinderCat is published by Vladislav Stepanenko under the developer name “Duck Does Stuff”.

Bluetooth discovery

FinderCat processes Bluetooth discovery data on-device. No FinderCat account is required, and there is no FinderCat backend or cloud synchronization. FinderCat uses no advertising SDK, analytics SDK or remote logging.

To find devices, FinderCat receives information made available by Android about nearby Bluetooth devices. This may include a device name, Bluetooth address or other temporary identifier, device type, pairing state, RSSI signal strength, and BLE advertising data.

This information is processed only on your device and is used to detect devices, identify their type, and evaluate changes in signal strength. BLE advertising data may be used, for example, to recognize Find My devices, iBeacon, and Eddystone. Raw advertising packets are not stored.

Permissions

On Android 12 and newer, FinderCat uses Nearby devices / Bluetooth permissions. On Android 11 and earlier, Android requires location permission for Bluetooth discovery. FinderCat does not obtain, store, or transmit your GPS coordinates or location history.

Locally stored data

If you add a device to Favorites, FinderCat may store its Bluetooth address, name, type, pairing state, last-seen time, and most recent available signal value locally. App and widget settings are also stored locally.

Bluetooth data and settings remain in the app storage on your device. Android cloud backup is disabled for FinderCat data. For Premium purchases, only the native cached entitlement state is persisted locally; FinderCat does not persist purchase tokens.

Retention and deletion

Temporary scan results are kept only while the app is running. Favorite device data is retained until you remove the device from Favorites or delete the app data.

You can remove saved devices through Favorites. You can delete all locally stored FinderCat data by clearing the app data in Android settings or uninstalling FinderCat. The developer has no server-side copy of this local Bluetooth data. These actions do not delete correspondence you sent or purchase records held by Google Play.

Google Play Billing

Google Play processes the one-time Premium purchase. FinderCat uses Google Play Billing to obtain product details and the formatted price, open the purchase flow, check ownership and purchase status, restore Premium, acknowledge completed purchases, and reconcile refunded or revoked ownership. During this lifecycle, the native app receives metadata required by the Billing API, including purchase status and purchase tokens. Tokens are not exposed to the WebView or sent to a FinderCat backend; there is no such backend or server-side verification. FinderCat does not receive payment-card numbers or payment credentials. Google Play’s terms and privacy practices apply to the purchase flow.

Support and external actions

Contact developers opens your external email app only when you choose that action, with recipient duckdstuff@gmail.com and subject “Отзыв FinderCat”. FinderCat leaves the body empty, inserts no app or device diagnostics and adds no attachments. FinderCat does not send the email: you write and review it and explicitly choose whether to send. Anything you voluntarily send travels through your chosen email service under its privacy practices. Rate app and Tell a friend also open the appropriate external service when selected.

Security

FinderCat data is stored in the app’s local storage protected by Android. FinderCat does not use cloud backup for user data and does not transmit Bluetooth data over the internet.

Contact and support correspondence

Privacy/support: duckdstuff@gmail.com. Correspondence reaches the developer only if you explicitly send it. Voluntary support correspondence may be retained only as reasonably necessary to respond, troubleshoot the reported issue and keep relevant support history, or where retention is required for legitimate legal or security reasons. You may request deletion of that correspondence at duckdstuff@gmail.com.