Your account, your hunts and your purchase are different things
LuckyFind starts with an automatically created guest account. Guest does not mean a recoverable email/password login has already been created. Before relying on a hunt as your only record, use the account controls to make that same guest account recoverable.
Both platforms support email/password accounts; iOS also supports Sign in with Apple. When changing phones, sign into the same LuckyFind account that owns the hunts. A different account can correctly show a different—or empty—history.
Account sync for routes and find details does not require Premium.
Core route tracking and find logging are free. LuckyFind Premium unlocks find photos, satellite and hybrid maps, and overlays of previous routes and finds.
Restore checks eligible purchases associated with the store account. It does not restore an unrelated LuckyFind login, transfer hunts between accounts or prove that pending uploads completed. Do not assume an App Store purchase and a Google Play purchase are interchangeable.
Local recording is not the same as cloud backup
Route and find changes have local persistence and pending-sync handling. This lets the apps retain recording work when connectivity is interrupted, but does not make every feature fully offline or guarantee survival of every device failure.
- Local checkpoint or journal
- A saved copy or pending change on this device. It is useful for recovery but is not a second-device backup.
- Pending route sync
- A route/find update waiting to be acknowledged remotely. “Saved locally” and “backed up” are not equivalent states.
- Pending photo upload
- A separate queue for image files. A route can exist in the account before all its Premium find photos finish uploading.
- Map imagery
- Loading map tiles can need a connection even when GPS samples are being recorded. There is no promised downloadable offline-map package.
Open and set up the app while connected before leaving. After a hunt, reconnect and inspect any save or backup status. Keep the current account and device data intact while retrying. Signing out, clearing app data, reinstalling or switching accounts is not a safe first troubleshooting step for unsynced work.
Local recovery does not make force-quitting during a hunt safe. Battery, location permissions, system restrictions and device storage still matter. Account sync is for saved data, not simultaneous editing or live hunt transfer between phones.
What is in the profile record?
In addition to routes and finds, the shared profile model has the following fields. Some may be empty or retained only for compatibility. This describes the app's profile format, not all data held by authentication, purchase or diagnostics services.
- Account identity:
documentID,email,username - Profile identity and account/display details. Guest and provider-linked accounts can have different available values.
- Dates:
signUpDate,lastOpenedDate - Profile timestamps for sign-up and recorded app opening.
- Categories:
itemCategories - The account's reusable find-category names, separate from the category text already saved on each find.
- Purchase metadata:
subscriptionType,subscriptionExpiration,platform - Profile metadata associated with subscription/platform state. These cached fields alone are not the authority for a current Premium entitlement.
- Notification tokens:
deviceTokens - A field for registered device notification tokens, when present. It is not the hunt's GPS coordinate list.
- Compatibility fields:
referralLink,friendIDList,friendRequestsIDList - Fields retained in the profile schema. Their presence does not mean the current apps offer group-hunt sharing or a working friends workflow.
For authentication, purchase providers, device/diagnostic information and broader handling of data, read the Privacy Policy. A record-field list is not a substitute for that policy.
What exactly does Export Routes include?
iPhone: GPX
The Settings export builds a GPX file from the loaded routes and makes it available through Files. Each route is a track with its name and notes. Track points contain latitude, longitude and time; paused gaps create separate track segments.
Find waypoints contain location, name, find time, and a description assembled from category, notes and depth with its saved unit. Invalid find coordinates and the placeholder coordinate 0,0 are omitted as waypoints. That means a find can exist in the app yet be absent from the exported waypoint list.
Android: CSV
The Settings export opens a share flow for luckyfind_routes.csv. It writes one row per find, or a route-only row when a route has no finds, with these columns:
Route, Start Date, Distance, Minutes, Find, Category, Depth, Depth Unit, Found At, Latitude, Longitude.
Distance uses the device's current route-display units, but the CSV's Distance column does not include a separate unit column. Note whether you exported metres or yards. Depth keeps its stored number and unit, including an unknown-unit marker for legacy depths. Dates are formatted as local date/time text, rather than a timezone-labelled interchange timestamp.
The CSV does not contain the full GPS track, route notes or find notes. It repeats route-level distance and minutes on each find row, so summing those columns directly will double-count routes with several finds.
Neither export includes photo files, even with Premium, or provides a complete restorable account backup. Account credentials are not included. These are files for use outside LuckyFind, not a promised re-import or account-restoration workflow. They can contain sensitive hunting locations and free-text details; inspect the file before sharing it.
Permissions are tied to a feature
Location supplies route samples and find positions. Follow the platform location instructions, including precise location; an Always location grant is not required for the documented setup. Android uses a foreground tracking service and can request notification permission for its ongoing status.
Camera/photo access is used when adding Premium find photos. Declining optional photo access does not turn a text-only find into a photo upload. Device permission settings and Premium access are separate controls.
This website's optional analytics preference is separate from native app permissions. Checking the first-hunt checklist does not send your answers to the app or create a hunt record.
Signing out and deleting are not interchangeable
Signing out leaves the account; it is not a request to delete the account's server data. Make the account recoverable and resolve pending saves before leaving it.
The in-app Delete Account flow asks for confirmation and may require a recent sign-in or password verification. It requests deletion of the authenticated account's route/find data and stored images, then its authentication account. A failure can require retrying; do not interpret a dismissed dialog or interrupted connection as confirmed completion.
Deletion is destructive. Export anything you need first, understanding the limits above. Deleting an account is not a substitute for managing or cancelling a subscription through the store where it was purchased. See the Privacy Policy for further data-handling and contact information.