BuckFinder Privacy Policy
Lapp's Online Dynamics LLC publishes BuckFinder and is responsible for the data it collects. Lapp's Online Dynamics LLC builds and runs the app as its developer. This policy describes what data BuckFinder collects, why, how it is shared, and how you can delete it.
BuckFinder is a mobile app (iOS and Android) that connects deer hunters with FAA Part 107 licensed thermal-drone pilots to recover downed deer, and provides hunting GPS map features.
Data we collect
Email address (account identity)
Purpose: Account creation, login, session management
Linked to your identity: Yes: it is your account identity
Shared with a third party: No
User ID (account UUID)
Purpose: Linking your account across features (waypoints, pilot listings)
Linked to your identity: Yes
Shared with a third party: No
Name (pilot accounts: full name)
Purpose: Pilot marketplace listing shown to hunters in-app
Linked to your identity: Yes
Shared with a third party: No (displayed in-app to authenticated hunters as core marketplace functionality)
Phone number (pilot accounts: contact phone)
Purpose: Hunter-to-pilot call and text handoff: hunters call or text the pilot from their own phone
Linked to your identity: Yes
Shared with a third party: No (disclosed in-app for the user-initiated call handoff)
Precise location: map waypoints and offline map regions
Purpose: Hunting map features: your saved waypoints and offline-map region bounds
Linked to your identity: Yes: waypoints sync to your account
Shared with a third party: No
Precise location: pilot service-area GPS (pilot accounts)
Purpose: Nearest-pilot discovery; hunters see the pilot's distance and service location in listings
Linked to your identity: Yes
Shared with a third party: No
Push notification / device token (Firebase Cloud Messaging registration token)
Purpose: Delivering push notifications from the app to your device
Linked to your identity: Yes: the token is stored against your user ID
Shared with a third party: No (Firebase acts as the push-delivery processor)
Pilot verification photos (FAA Part 107 license and drone-proof photos; pilot accounts)
Purpose: Manual pilot verification, reviewed by an administrator; stored in a private, access-controlled bucket
Linked to your identity: Yes
Shared with a third party: No (admin review only)
Device / usage diagnostics (Mapbox SDK telemetry)
Purpose: The Mapbox map SDK collects map-usage telemetry (device metadata, approximate map-interaction data) for Mapbox's billing and product improvement; map tile requests carry approximate viewport location to Mapbox servers. The telemetry Mapbox receives can include your precise and approximate location, an identifier the Mapbox SDK assigns, how you use the map, map performance data and other diagnostics, used by Mapbox for analytics and to run the map. You can turn Mapbox telemetry off from the map's info (“i”) button
Linked to your identity: No: not keyed to your BuckFinder account (Mapbox uses its own identifier, not your BuckFinder account ID)
Shared with a third party: Yes: the Mapbox SDK sends it to Mapbox, the map service operator
Crash and error reports (Sentry)
Purpose: Finding and fixing app crashes: the error, the account ID, device model, OS version and app version
Linked to your identity: Yes: the account ID only (never your email, name or phone)
Shared with a third party: Sentry processes them as our service provider; no location is ever included
Pin deletion records (Sentry)
Purpose: Restoring a map pin you deleted, when you ask within 30 days: a record that a pin was deleted and when, with the account ID, device model, OS version and app version
Linked to your identity: Yes: the account ID only (never your email, name or phone)
Shared with a third party: Sentry processes them as our service provider; the pin's name and location are never included
Admin portal and backend error reports (Sentry)
Purpose: Finding and fixing errors in the BuckFinder admin portal and backend: the error, the route or function where it happened, and the release
Linked to your identity: Only by an account ID the report scrubber keeps (in the admin portal, the administrator's account ID); email addresses, tokens and other personal fields are removed before sending
Shared with a third party: Sentry processes them as our service provider; no location is ever included
Service providers
BuckFinder uses these services to run. The data each one handles is listed with it.
Supabase
Role: Backend hosting: authentication, database, file storage, realtime updates
Data it handles: All account data listed above (email, user ID, locations, tokens, pilot documents)
Mapbox
Role: Map rendering and offline map tiles
Data it handles: SDK telemetry (map-usage data: precise and approximate location, a Mapbox SDK identifier, map interaction, performance and diagnostic data) and approximate map-viewport location (see diagnostics row above); you can turn the telemetry off from the map's info (“i”) button
Firebase Cloud Messaging (Google)
Role: Push notification delivery
Data it handles: Push registration token and delivery metadata
Sentry (Functional Software, Inc.)
Role: Crash and error reporting; pin deletion records
Data it handles: App crash and error reports with your account ID, device model, OS version and app version; a record of each map pin you delete, with the same fields; admin portal and backend error reports with the error, route and release; never location
Summary
We do not track you. BuckFinder contains no advertising SDKs and does no cross-app tracking. The Mapbox map SDK that draws the map sends map-usage data to Mapbox (see the Mapbox rows above); you can turn this off from the map's info (“i”) button. The app uses Sentry only to receive crash and error reports so we can fix crashes, and a record each time you delete a map pin (your account ID, never the pin's name or location) so we can restore it if you ask; that is not tracking. No data is used for advertising or tracking purposes, and we do not sell your data.
Most data is linked to your account. BuckFinder features run behind an authenticated account, so data such as your email, location pins, and push token are associated with your user ID.
You choose who gets your location: when you (a hunter) contact a pilot, you call or text them from your own phone. If you text, the app pre-fills your pin's coordinates in the message, and you decide whether to send it. BuckFinder itself sends no location to any pilot.
You can delete your account and data at any time, in the app or by email.
What we do not collect
We do not collect: profile photos or avatars, contacts, messages, browsing history, health data, financial or payment information, or any advertising identifiers.
Contacting a pilot
When you want a deer recovered, you choose a pilot in the app and call or text them from your own phone. If you text, the app opens your phone's messaging app with your pin's coordinates pre-filled in the message; nothing is sent until you send it yourself, and it goes from your phone to the pilot you chose. BuckFinder's servers send no location to any pilot. Pilots are independent operators (not employees or processors of Lapp's Online Dynamics LLC).
Tracking and advertising
BuckFinder does not use your data for tracking as defined by Apple's App Tracking Transparency framework or Google Play's Data Safety program. The app contains no ads, no advertising SDKs, and no cross-app or cross-site tracking. The Mapbox map SDK, which draws the map, sends map-usage data to Mapbox for Mapbox's analytics (see the Mapbox rows above); it is not linked to your BuckFinder account, and you can turn it off from the map's info (“i”) button. The app uses Sentry only to receive crash and error reports, linked to your account ID, so we can find and fix crashes, and a record, linked to your account ID, each time you delete a map pin, so we can restore it if you ask; Sentry acts as our service provider, and this is not tracking. We do not sell your data.
Data retention
Your data is retained while your account is active. When you delete your account, your account data (profile, pilot verification documents, waypoints and push tokens) is deleted from our systems. The account deletion page gives the exact in-app steps, what is removed, and an email request path if you no longer have the app installed.
Deleting a single pin (map waypoint) works differently from deleting your account. A pin you delete is removed from your map but kept on our systems for 30 days. Within those 30 days you can get it back by emailing sammy@lappsonlinedynamics.com. After 30 days it is permanently deleted. Deleting your account still removes all of your waypoints, as described above.
Crash and error reports and pin deletion records are kept by Sentry for Sentry's retention period for our account, then deleted. Deleting your account removes your account ID from our systems, but reports and records Sentry has already received are not removed by the deletion; they are deleted on that same retention schedule.
Security
Data is stored with our backend provider (Supabase) behind authenticated access controls, including row-level security rules that restrict each user's data to their own account. Pilot verification photos are stored in a private bucket accessible only to the pilot who uploaded them and administrators performing verification.
Children
BuckFinder is not directed at children and is intended for use by adults engaged in lawful hunting and wildlife-recovery activity.
Feedback
If you send feedback from inside BuckFinder, it goes to Lapp's Online Dynamics LLC as the app's developer.
Deleting your account
You can delete your BuckFinder account and its data at any time. The steps are on the Delete your BuckFinder account page.
Contact
Questions about this policy or your data can go to Lapp's Online Dynamics LLC at sammy@lappsonlinedynamics.com or through https://lappsonlinedynamics.com/#contact.
Changes to this policy
If these data practices change, this page is updated and its effective date is revised.