1. Information FlockOff uses
Location and motion context
With your permission, FlockOff uses precise location, course, speed, timestamp, and accuracy information to center the map, calculate distance to known cameras, generate proximity alerts, plan routes, and create a draft camera sighting. A short rolling history of recent fixes is held in memory to compensate for the delay between seeing a camera and reporting it.
Widgets and Live Activities
To show your current area on the Home Screen and Lock Screen, FlockOff creates a small location-derived map image. The image may reveal your approximate location to someone who can view your device. A full snapshot is stored locally in the shared App Group container and replaced as the displayed area changes. While Monitoring is active, a tightly compressed thumbnail is also held in Apple-managed ActivityKit state so iOS can render the Live Activity while the device is locked. These images contain no GPS metadata, are not accumulated into a travel history, and are never sent to FlockOff's developer.
Preferences and local app data
Alert distances, sound choices, appearance, monitoring state, cached camera records, and draft reports are stored in the app's private container on your device. An OpenStreetMap access token is stored in the iOS Keychain if you connect an OSM account.
Optional report content
A draft camera report can contain the camera's coordinates, direction, manufacturer, mount, operator, and a note. The draft remains local unless you explicitly submit it.
Drive Log
While Monitoring is on, FlockOff treats that session as a drive. When you turn Monitoring off, a completed drive of meaningful length (or any drive with at least one camera alert) is saved as a Drive Log entry containing: the start and end time, the total distance traveled, and, for each camera that triggered an alert during the drive, that camera's ID, name, coordinates, and the time it was first encountered. This is a persistent local record, distinct from the roughly 30-second in-memory location buffer described above — it is what powers the Drive Log screen's recaps and lifetime totals (drives logged, distance driven, cameras encountered). It is never sent off your device.
2. Information sent off your device
- OpenStreetMap Overpass: To request nearby camera records, FlockOff sends a bounding box derived from your current location or the map area you choose. The service also receives ordinary network information such as your IP address. FlockOff does not receive or store a server-side copy of this request.
- Apple MapKit and system surfaces: Apple provides base maps, local place search, and driving directions. Map and route requests, including origin and destination, are processed by Apple under Apple's privacy terms. WidgetKit and ActivityKit display the locally prepared current-area map on system surfaces such as the Home Screen, Lock Screen, Dynamic Island, and supported paired devices.
- OpenStreetMap editing: If you connect your OSM account and tap Submit, the reviewed camera coordinates and tags are sent to OSM. The edit, changeset, and supplied text become public and are associated with your OSM account. Your recorded speed and travel course are not uploaded.
These services are used only to provide app functionality. FlockOff does not sell data, use it for advertising, or permit tracking across apps and websites. Service providers acting on FlockOff's behalf must protect information consistently with this policy; Apple, OpenStreetMap, and independently operated Overpass instances also process information under their own published terms and policies.
3. Retention and deletion
- Recent location fixes are kept in memory for roughly 30 seconds and disappear when the process ends.
- The shared App Group keeps one fallback location and one current-area map snapshot for widgets. They are replaced in place, not accumulated into a location history, and remain until replaced or FlockOff is deleted. The smaller ActivityKit thumbnail exists only as part of the active Live Activity; FlockOff requests its immediate removal when Monitoring ends.
- Camera data is stored in iOS Caches. Records are treated as stale after seven days, but last-known data may remain available until a successful refresh replaces or prunes it, you use Clear Cache in Settings → Storage, you delete FlockOff, or iOS clears the cache.
- Preferences remain locally until you change or reset them, or uninstall the app. Pending and submitted report records remain until you remove them or uninstall the app.
- Drive Log entries are stored as a file in the app's private Application Support directory on your device, protected by iOS file encryption until your device is first unlocked after a restart. FlockOff keeps at most your 200 most recent drives; older entries are dropped automatically as new ones are recorded. There is currently no in-app control to remove an individual Drive Log entry — deleting FlockOff removes the entire Drive Log along with the rest of the app's local data.
- You can delete a pending report at any time before submission. Signing out removes the OSM access token from FlockOff.
- A submitted OSM edit is part of OpenStreetMap's public edit history. Removing the local FlockOff record does not remove that public history. Use OpenStreetMap's tools or support process to correct or remove inaccurate public map data.
FlockOff's developer does not retain a server-side account, location history, analytics profile, or report database and therefore has no such developer-held record to provide or delete.
4. Your controls
You can pause monitoring in FlockOff Settings, change or revoke Location access in iOS Settings, delete pending reports, remove submitted report records from the device, and sign out of OSM. You can still browse the map with reduced functionality if you do not grant location access. A Clear Cache control in Settings → Storage immediately deletes the locally cached camera map data and re-downloads it for your current area — this does not affect your Drive Log, alert preferences, or report records. As noted above, Drive Log entries can currently only be cleared by deleting the app.
5. Security
Network requests use HTTPS. OSM authentication uses OAuth 2 with PKCE, so FlockOff never sees your OSM password. The access token is stored in Keychain, and sensitive pending-report files and the shared widget map use iOS file protection. No security method is perfect, but the app limits what it stores and has no developer-operated user database.
6. Children
FlockOff is designed for licensed drivers and is not directed to children under 13. We do not knowingly collect children's personal information.
7. Third-party policies
8. Changes and contact
We may update this policy when app behavior or legal requirements change. The effective date above will be revised when that happens. Questions, privacy requests, or support inquiries can be sent to support@flockoffapp.com.