Fieldwatch Privacy Policy

Last updated: October 19, 2026.

Developer and privacy contact: Mustafa Bütün — single.develooper@gmail.com.

Public policy: https://fieldwatch.pro/privacy

Short version: room records and detection results stay on your phone. There is no account or advertising. The only feature that uses a Fieldwatch server is the optional [AI room review](#ai-room-review-optional), which sends photos you take, only after you agree. Crash reports and paywall analytics are sent to Sentry, Firebase and MySuperwall (see [below](#crash-reports-analytics-and-paywalls)); they never contain scan results, radio addresses or device names. Optional Internet connection checks contact Cloudflare only after you start a test and accept the in-app disclosure. Optional network camera checks send discovery queries on the connected local network when you start them. Purchases contact the store/RevenueCat. Detection results are not uploaded; they leave the device only when you export or share.

What the app collects, and where it lives

DataSourceStoredWhere
Radio identifiers (Wi-Fi BSSID, BLE address on Android, per-app peripheral UUID on iOS)Broadcasts your phone hearsYes, in the audit logEncrypted SQLCipher database in app-private storage
Advertised names, SSIDs, service UUIDs, manufacturer data, RSSI, channelSameYes, in the audit logSame
Signature matches, categories, co-travel scoresComputed on deviceYes, in the audit logSame
This phone's location (latitude, longitude, accuracy)OS location service, only if you grant permission and enable itYes, attached to sightingsSame
Inspection sessions: name you give, start / end time, steps done or skipped, source coverage, every distinct broadcast heard during the session with first / last seen and signal summary, the catalog match snapshot and your notesComputed on device and typed by youYes, when you start an inspection (kept as a draft until you save or discard it)Same encrypted database
Phone positions attached to an inspectionOS location service, only if you switch on "note where my phone was"YesSame encrypted database
Photos you attach to an inspectionCamera or gallery, your choiceYesApp-private storage as separate files. They are not separately encrypted; the encrypted database holds only a reference. Deleting the inspection deletes them.
Your labels on single broadcasts ("this one is mine"): name, note, identity type, an expiry for changing addressesYouYesSame encrypted database
Stays (a name you give, an optional room / area, optional check-in and check-out dates, notes) that group inspectionsYouYesSame encrypted database. No location is needed or stored for a stay.
Measured spots (the name you give a place and a short summary of signal strength heard there: packet count, typical, lowest and highest level)Computed on device while you stand still and measureYes, with the inspection in progressSame encrypted database. A spot is where the phone stood, never where a device is.
Lens re-checks (the reflection you marked, your note, your conclusion) and their photosYouYesThe text in the encrypted database; the photos as separate app-private files (not separately encrypted), deleted with the inspection
Network camera checks: local IPs, reported names/types/endpoints, scan time, outcome and optionally requested manufacturer/model/firmware/servicesUser-started ONVIF discovery repliesYesEncrypted database. Attached checks are deleted with the inspection; standalone checks retain the latest 20 and can be deleted individually.
PDF reportsGenerated on requestTemporarily, in the app's temporary folder, until the system clears it or you delete the inspectionApp-private storage. A report leaves the phone only through the system share sheet when you pick a target.
Settings and preferencesYouYesApp-private storage
Database encryption keyGenerated on first launchYesAndroid Keystore-backed secure storage / iOS Keychain
Live scan buffer (recent sightings for the correlation window)ScannerMemory onlyDiscarded when the app stops

Location is this phone's position when a radio was heard. It is never the position of the other device. It is off until you allow it, is read only while a scan or inspection is running, and is never uploaded.

What the app does not do

A separate information action can request manufacturer, model, firmware and service namespaces from the same local private IP using ONVIF SOAP. HTTP can be unencrypted. It does not fetch video, follow redirects or try credentials.

[below](#crash-reports-analytics-and-paywalls)) runs only if you agree in onboarding, and on iPhone only if you also allow App Tracking. Firebase Analytics itself is built without IDFA support and has ad IDs turned off.

The separate user-started ONVIF check actively requests local service announcements.

governed by your OS settings; the database is encrypted and its key is not included in a portable form.)

AI room review (optional)

Only when you open this feature, take photos and press the send button after ticking the consent box. Never in the background and never for scan results.

WhatDetail
Sent3 or 4 room photos you took inside the feature (shrunk by the camera, JPEG), your app language, and, to check your Pro purchase and give one free review per phone, the RevenueCat app user ID (a random application identifier, not a payment-card number, your name or email) and a device id (a random id kept in the iPhone Keychain, or the Android ID). The raw identifiers are transmitted to the Fieldwatch server; RevenueCat receives its app user ID for entitlement checks. Fieldwatch stores keyed hashes of identifiers, not their raw values
Received byThe Fieldwatch analysis server, which passes the photos to the AI provider named on the consent screen, currently OpenRouter routing to Google’s Gemini 2.5 Flash Lite. The consent screen links to this policy, including the provider links below
Kept by FieldwatchThe server does not persist photos or AI responses or log their content. It stores keyed identifiers, free-review usage and quota counters; Pro review reservation records are retained for a rolling 30-day quota window. Free-review usage remains until a deletion request is fulfilled. Request logs contain generated request IDs, response status, duration, photo count and, for some failures, a sanitized error category. IP addresses are processed for connectivity and hashed rate limiting
Kept by the providerUnder the provider's own rules, which can include short retention for abuse checks. Read them before you agree. Fieldwatch does not claim zero retention
On your phonePhotos are temporary files while you review them, removed when you leave the feature or remove them (removal can fail if the app is killed). After a review, the answer and a copy of its photos are kept in the AI tab of the history so you can read it again: the answer in the encrypted database, the photos as app-private files (not separately encrypted). Only the newest 20 reviews are kept, and you can delete any of them one by one. Uninstalling the app removes them
Not sentScan results, radio addresses, device names, location, your other inspections

Photos can contain private details. Keep people, screens and papers out of them. Fieldwatch does not strip metadata itself and asks the camera not to attach full metadata; do not assume it is removed. The review points to places worth a closer look. It cannot confirm or rule out a camera.

Reminders and tips

If you press Allow in onboarding (or switch it on in Settings), Fieldwatch schedules local notifications on your phone: in the evening, thinning out if you stop opening the app, and a short series if you leave setup unfinished. They can include offers for Fieldwatch Pro. They are scheduled by your phone; no server, push token or account is involved, and nothing about you is sent anywhere to create them. Switch them off in Settings or in the system's notification settings.

Crash reports, analytics and paywalls

Release builds that were given the matching keys use these services. Builds without a key leave that service off, and debug builds send nothing to Firebase.

ServiceWhat is sentWhat is never sent
Sentry (crash and error reports)Error type and message, stack trace, app version, OS and device model, screen (route) namesYour IP address, user ID, the device's name, screenshots, on-screen text, taps, console output. MAC addresses, UUIDs and IP addresses in error messages are replaced with placeholders before sending (sendDefaultPii is off)
Firebase CrashlyticsError message and stack trace (scrubbed the same way), app version, OS and device model, an installation IDWidget diagnostics (which can contain on-screen names), scan results
Firebase AnalyticsPaywall funnel events (paywall shown / closed, plan picked, purchase started / completed, restore) with the trigger or plan name, plus Firebase's automatic session and app-version data and an app-instance ID and approximate region derived from IP addressAdvertising ID, ad personalisation, scan results, room records, location from this app
Facebook App Events (optional, ad attribution)Only after you press Allow in onboarding, and on iPhone only if you allow App Tracking: app installs and opens, onboarding finished, paywall shown (with the trigger name) and checkout started, with Meta's standard device and advertising identifiersScan results, room records, device names, radio addresses, location, photos. Turn it off by deleting the app or revoking App Tracking in iOS Settings
MySuperwallPaywall requests and events (shown, closed, product tapped, purchase result) with a random anonymous ID it generates on the device, app version, language, OS version, device model, session and paywall-view counts, days since install and, on iOS, the device name the system reports (generic "iPhone" on iOS 16 and later)Scan results, purchase receipts, payment details. Purchases are handled only by the store and RevenueCat

None of these services receives detection results: the scan, inspection and audit-log data described above stays in the encrypted database.

Exports and sharing

When you export the audit log (JSON or CSV), the file is written in plaintext and handed to the system share sheet. From that moment the file is outside the app's control: whoever you send it to, or whatever app you save it in, can read it, including any coordinates it contains. Review exports before sharing.

Deleting your data

PDF report fonts

PDF reports are generated locally. The app includes the Inter font for Latin and Cyrillic text. When a report needs Arabic, Japanese or Chinese characters, it downloads the required Noto font files from Google Fonts (fonts.gstatic.com) and caches them in app-private storage for later offline use. No report text, notes, device names or photos are sent in font requests. Google receives the network request, including the IP address and requested font URL. A first-use font download requires an Internet connection. See Google privacy policy.

Third parties

Local discovery, store purchases (Apple / Google, RevenueCat), crash reporting (Sentry, Firebase Crashlytics), paywall analytics (Firebase Analytics) and remote paywalls (MySuperwall) and on-demand PDF fonts (Google Fonts) use network access. Detection results are not sent to any of them. The BLE plugin is pinned to a BSD-licensed release without build-time license pings. See [NOTICE](NOTICE).

Children

The app is not directed at children. Optional AI processing, purchases and configured diagnostics/analytics process the information described in this policy; do not submit children’s personal information in photos.

Changes

Changes to this document are tracked in the repository history and [CHANGELOG.md](CHANGELOG.md).

Contact

For privacy questions or deletion requests, email single.develooper@gmail.com. Do not send room photos, purchase receipts, API keys or passwords in your initial request. We will explain how to identify the relevant records privately. No app account is required. Removing the app does not automatically remove provider-side purchase records or server-side quota records. Deletion may be subject to applicable retention obligations; removing quota records may also affect trial eligibility.

Language choice is stored locally. Optional reminders store one chosen time and a generic notification message with the operating system; they do not scan in the background or send detection details in notifications.

Belongings guard (Android)

The user can arm a separate, visible foreground service to observe phone movement, optional ambient-light increases and external-power disconnection. No camera, microphone, location or remote transmission is used for this feature. The phone must remain with the belongings. Event timestamps and types, session status and sensor/settings metadata are encrypted using an Android Keystore AES-GCM key in app-private preferences. The latest ten sessions retain at most 100 events each; history can be cleared when protection is stopped. Protection expires after eight hours, is not automatically restarted after reboot/process death, and may be interrupted by Android/device restrictions. No events does not prove that no intervention took place. An optional short local beep is off by default.

Phone privacy check (Android)

Only explicitly listed package identifiers in the bundled Echap indicator catalog are queried in the current Android user profile. Fieldwatch does not request QUERY_ALL_PACKAGES for this feature. Matching visible package names, display labels, versions, current signing-certificate fingerprints, enabled state and selected granted sensitive permissions are processed locally, in memory only. Results are not persisted, uploaded or used for analytics. No application is launched, removed or disabled by the check. App settings and the external support website open only when selected. The catalog ships with the app; updates require a reviewed app release. Package or certificate matches do not prove active spying, and an empty result does not prove a device is free of spyware.

iOS RoomPlan

Optional, user-started camera/LiDAR scans create room geometry and parametric 3D models locally. RoomPlan files (USDZ, geometry JSON and metadata) are stored under app-private Application Support with complete iOS file protection and excluded from backups. Up to 20 models may be retained; users can delete models individually. Inspection-linked models are removed with their inspection. Camera video is not recorded or uploaded. Quick Look allows users to view a saved model and explicitly share/export it; exported files may reveal private room layouts.

Camera-glasses view

The dedicated view filters existing BLE observations for selected camera-glasses catalog families. Its additional visit history and optional alert deduplication are memory-only; the shared scanner's existing audit storage still applies. No connection/pairing, remote lookup or recording-status query is made. Optional foreground screen feedback uses a banner and system haptic; no background notification service is added. Candidate identity is not proof of recording.

Optional accommodation Wi-Fi measurement

The user starts each short test after accepting its disclosure. HTTPS requests to speed.cloudflare.com/__down and /__up transfer up to approximately 14 MB of measurement payload, plus protocol overhead. Cloudflare receives the public IP address and ordinary request/traffic information. Fieldwatch does not send room names, Bluetooth observations, photos, findings or result summaries to this service; the Cloudflare JavaScript SDK and its results-logging APIs are not used. Normal OS routing applies, including VPNs or cellular fallback. Completed measurements are saved only on request, linked to a chosen stay in the existing encrypted local database (at most 20 per stay). They can be deleted individually and are removed when their stay is deleted. Closing the page or backgrounding the app cancels the active test.

Providers, retention and international processing

Optional cloud AI uses OpenRouter and the selected model provider, currently Google. Requests require supported parameters and exclude model endpoints marked as collecting data; this is not a guarantee of zero retention. Provider logging and retention settings remain subject to their terms. Do not submit photos you cannot authorize for this processing. Processing may occur outside your country.

Other providers: RevenueCat, Firebase/Google, Sentry and MySuperwall as described above. Store payments are handled by Apple or Google; Fieldwatch does not receive card numbers. SDK identifiers are not automatically anonymous merely because they are random. We do not use them for cross-app advertising tracking or sell room records.

Precise phone location, Bluetooth/Wi-Fi observations, RoomPlan geometry and ordinary inspection records are processed locally, except when you explicitly export/share them. Analytics providers may derive approximate region from network IP independently of phone location permission. Server infrastructure and providers necessarily process connection IP addresses even when the app strips IP text from crash payloads. Configured third-party retention settings govern diagnostic, analytics and transaction records. Contact us to request access, correction or deletion of data under our control.