Privacy policy
How the Beacon View Android app handles network traffic, permissions and settings backups.
Last updated
Data and network traffic
Beacon View has no telemetry, ads or crash reporting. Traffic goes only to your Frigate server and cameras, plus OpenFreeMap tiles when the map is open (OpenFreeMap sees your IP address and the map area you view). The app does not use Google Play Services or Firebase Cloud Messaging.
Map data © OpenFreeMap, OpenMapTiles and OpenStreetMap contributors.
App permissions
| Permission | Why it’s used |
|---|---|
| Notifications | Frigate alerts. |
| Foreground service, run at startup | Keep the direct connection to Frigate for push alerts (only while push is on) and resume it after a reboot. |
| Approximate location | Center the camera map when no camera is pinned yet. The app never stores or sends this location. |
| Network, Wi-Fi multicast | Reach Frigate and cameras, and discover ONVIF cameras on the LAN. |
| Cleartext HTTP | Many LAN cameras and servers only support http:// or rtsp://. Your Frigate login is unencrypted over http://. Use https:// when connecting from outside your LAN. |
Data stored on your device
Your Frigate login secrets are encrypted with the Android Keystore. Your camera list (including GPS coordinates of cameras you pin on the map), settings and event cache are kept in a local database and app preferences. Snapshots you choose to save go to Pictures/BeaconView. None of this is sent to the developer.
Deleting your data
Signing out of Frigate removes the stored session. Uninstalling the app or clearing its storage in Android settings removes all app data. Exported settings backups are files you control; delete them yourself.
Settings backups
Settings backups can contain RTSP passwords. Keep them private.
Children
Beacon View is not directed at children under 13, and we do not knowingly collect data from them.
Changes to this policy
We’ll publish any changes on this page and update the date above.
Contact
For privacy questions, email info@beaconview.app.