# STALKR canonical public knowledge

Last verified: 2026-08-23
Release channel: TestFlight beta

## Feature availability

### Account authentication [BETA]
Create an account, sign in, reset or change a password, sign out, and permanently delete the account.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/getting-started/create-account
Offline: Authentication and account changes require the service.
Background: None.
Limitations: Email delivery and network access are required for password recovery.

### Profile and profile photo [BETA]
Edit display name, nickname or call sign, avatar, phone, and optional emergency medical information.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/settings/change-profile-photo
Offline: Saving profile changes and uploading an avatar require the service.
Background: None.
Limitations: A failed image upload leaves the previous photo in place.

### Crews [BETA]
Persistent trusted groups for scoped location sharing, markers, statuses, and field coordination.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/crews/what-is-a-crew
Offline: Previously cached Crew membership may remain visible, but creating or changing a Crew requires the service.
Background: Crew membership persists; location behavior is described separately.
Limitations: A Crew list fetch failure is shown as unavailable, not as an empty account.

### Crew invites, codes, and join requests [BETA]
Share a Crew link or code; a new person asks to join and a Crew admin accepts or declines the request.
Platforms: ios, web-invite.
Help: https://navtrl.com/stalkr/help/crews/join-crew
Offline: Submitting and deciding requests require the service.
Background: None.
Limitations: A shared SMS or email is not delivered until the user completes the system share flow.

### Live Crew location sharing [BETA]
Publishes the current authorized position, direction, accuracy, status, and available battery information to the active Crew scope.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/location-sharing/go-live
Offline: There is no durable offline outbox. Failed live writes are not queued for later delivery.
Background: Background updates are implemented when Always location is granted; see Background Location.
Limitations: LIVE can show a delivery warning when repeated writes are not reaching the Crew. Stationary presence is refreshed by a heartbeat, subject to OS execution.

### Dark [BETA]
Stops current location sharing to the selected Crew scope; authorized viewers retain the last location row marked offline rather than receiving new fixes.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/location-sharing/what-does-dark-mean
Offline: PARTIAL: the local choice changes, but the Crew may not receive that change until connectivity and execution resume.
Background: The selected state persists, but an offline change made without connectivity is not queued for the Crew.
Limitations: Dark is not a deletion of the last authorized location. Dark cannot override Tracking Enforced.

### Tracking Enforced [BETA]
A Crew rule that keeps every member, including the owner, Live in that Crew until enforcement is disabled in Crew settings.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/crews/tracking-enforced
Offline: No durable offline outbox.
Background: Uses the same background behavior as Live sharing.
Limitations: The owner must turn enforcement off in Crew settings; the Live/Dark control cannot bypass it.

### Crew member markers and presence [BETA]
Shows authorized Crew members on the map with identity, facing direction when available, accuracy, status, battery when reported, and live/stale/unknown presence.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/map/find-a-crew-member
Offline: Cached in memory only and lost when the app process ends.
Background: Remote member updates arrive when the app can receive realtime events.
Limitations: A direction cone is omitted when the member has no trustworthy heading. Stale data is labeled rather than presented as current.

### Journeys [BETA]
A destination-based live travel session shared with selected watchers until arrival, cancellation, or manual completion.
Platforms: ios, web-watcher.
Help: https://navtrl.com/stalkr/help/journeys/start-journey
Offline: PARTIAL: local progress can continue, but watcher delivery, server position persistence, arrival, and overdue escalation require connectivity.
Background: Last position is persisted while location execution continues; arrival and overdue processing also rely on deployed server functions and schedules.
Limitations: External SMS/email flows require the user to complete the composer. A Journey requires a destination and service access to start.

### Journey overdue escalation [PARTIAL]
When an expected arrival is set, STALKR can nudge the traveler, allow an ETA extension, and escalate to watchers if there is no response.
Platforms: ios, server.
Help: https://navtrl.com/stalkr/help/journeys/expected-arrival-alerts
Offline: Escalation cannot be guaranteed without server connectivity.
Background: Depends on deployed scheduled/server functions and push/email configuration.
Limitations: This is an aid, not a guaranteed emergency-service dispatch system.

### Interactive map [BETA]
The primary field surface for self position, Crew members, markers, zones, trails, Routes, Checkpoints, Journeys, search, and map tools.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/map/use-the-map
Offline: Google map tiles may be opportunistically cached but no downloadable offline map is supported.
Background: The visible map is foreground UI.
Limitations: No supported offline-region download. Only one authoring/map tool can own the map at a time.

### Self marker [BETA]
Shows your current GPS fix, accuracy halo, identity, facing direction when trustworthy, and controls for recentering and self details.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/map/self-marker
Offline: GPS can work without cell service, but the base map and server sharing are not guaranteed offline.
Background: The map representation is foreground; the location pipeline may continue separately.
Limitations: Direction is omitted for an invalid compass fix. Indoor or obstructed GPS may have a large accuracy halo.

### Measure tool [BETA]
Measures straight-line distance and bearing between map points without creating a saved object.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/map/measure-distance
Offline: The geometry calculation is local; useful map tiles are not guaranteed offline.
Background: None.
Limitations: It measures point-to-point map distance, not a planned navigable Route.

### Markers and waypoints [BETA]
Crew-scoped map points for waypoints, dangers, safe places, camps, vehicles, animal signs, evidence, supply caches, and custom notes.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/markers/create-marker
Offline: Existing loaded markers may remain in memory; create, move, edit, and delete require the service and are not queued.
Background: Arrival monitoring can continue with background location permission.
Limitations: A move is saved only after pressing SAVE; a failed write restores the original position.

### Marker arrival alerts [PARTIAL]
Optionally detects arrival within a configured marker radius and records/notifies the transition.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/markers/arrival-alerts
Offline: The local transition ledger prevents duplicates, but Crew event/push delivery is not queued offline.
Background: Background updates and iOS region monitoring are implemented; force-quit and OS scheduling constraints apply.
Limitations: Poor GPS accuracy can delay a decision. Departure from a marker is recorded but does not buzz.

### Zones [BETA]
Crew-scoped geographic circles or polygons with appearance, visibility, monitoring, and enter/leave alert settings.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/zones/create-zone
Offline: Loaded geometry may remain visible in memory; changes and remote alerts require the service and are not queued.
Background: Monitored Zones can be evaluated by background location and iOS region monitoring when Always access is granted.
Limitations: Hiding the Zones layer changes drawing only; it does not disable monitoring. Monitoring and arrival/leave notification toggles are separate settings.

### Tracks [BETA]
Records movement that actually occurred as a timestamped GPS breadcrumb trail with activity, duration, distance, movement/rest statistics, and quality diagnostics.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/tracks/start-track
Offline: A Track cannot start offline because the server row must be created first. The active line is local while recording, but there is no durable offline point outbox.
Background: The recorder uses the shared high-accuracy location pipeline; background location implementation is pending full physical-device validation.
Limitations: Pausing a Track pauses recording only; Crew Live sharing continues. Do not force-quit during a recording if background continuity matters.

### Checkpoints [BETA]
Meaningful saved points captured at the current GPS fix; created during a Track they belong to that Track, otherwise they are standalone personal Checkpoints.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/checkpoints/add-checkpoint
Offline: Creation and edits require the service.
Background: Checkpoint arrival alerts follow the marker/geofence background pipeline.
Limitations: A Checkpoint requires a current GPS fix. Its coordinate is captured when the creation sheet opens, not when Save is pressed.

### Routes [BETA]
Reusable paths made deliberately from completed Tracks, displayed or followed later with progress and next-Checkpoint context.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/routes/open-route
Offline: Route geometry must have been loaded; there is no supported offline Route download/cache guarantee.
Background: Following is foreground map guidance; no turn-by-turn background navigation service is implemented.
Limitations: A Route is not created automatically when a Track finishes. The actively followed Route remains visible even if the global Routes layer is hidden.

### Marker, Zone, Checkpoint, and profile photos [BETA]
Capture or choose photos, view them in a shared gallery/viewer, add captions where supported, and delete only with object-specific authority.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/photos/add-photos
Offline: Uploads and remote retrieval require connectivity; no upload queue exists.
Background: Uploads are foreground operations.
Limitations: Unsupported local URI schemes are rejected by upload normalization. A failed image is suppressed rather than retried forever.

### Background location [PARTIAL]
Registers background location updates and iOS region monitoring for location sharing, Zone transitions, marker arrivals, and Track continuity when the OS permits execution.
Platforms: ios, android-implemented-not-released.
Help: https://navtrl.com/stalkr/help/permissions/background-location
Offline: Local transition baselines and a ledger persist, but remote writes are not queued for later delivery.
Background: Implemented in code and configured in platform manifests; physical-device validation remains a release gate.
Limitations: Force-quitting stops ordinary background updates; iOS region monitoring may still wake for eligible circle regions but is OS-controlled. Background execution is never an emergency-service guarantee.

### Notifications and activity [PARTIAL]
Local and push alerts plus an in-app notification center/activity feed for Crew, Zone, arrival, Journey, check-in, and SOS events.
Platforms: ios, server.
Help: https://navtrl.com/stalkr/help/notifications/manage-alerts
Offline: Local alerts can be created from local detection; remote delivery and shared activity require connectivity.
Background: Push delivery depends on APNs/Expo/server configuration; local notifications depend on OS permission.
Limitations: The OS can suppress notifications. A missing push token or server configuration prevents remote delivery.

### SOS [BETA]
A deliberate press-and-hold emergency action on the map that creates a panic incident and attempts to alert the active Crew.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/safety/send-sos
Offline: PARTIAL: the app reports when it could not reach the server; SOS is not queued for later delivery.
Background: The trigger is a foreground hold action; recipients may receive push alerts.
Limitations: SOS does not contact public emergency services. A failed network request means the Crew may not receive it.

### Check-in timer and dead-man switch [BETA]
Arms a one-time check-in or repeating dead-man timer and escalates a missed acknowledgement to selected people.
Platforms: ios, server.
Help: https://navtrl.com/stalkr/help/safety/check-in-timer
Offline: Creating, resolving, and escalating timers require service connectivity.
Background: Server-side escalation depends on deployed scheduling/functions and notification infrastructure.
Limitations: Not a substitute for emergency services; server and notification delivery are dependencies.

### Low-signal and stale-risk monitor [BETA]
Labels location presence as live, stale, or unknown and can surface low-signal risk instead of pretending old data is current.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/troubleshooting/member-location-stale
Offline: Loss of connectivity naturally makes remote positions age to stale/unknown.
Background: Relies on incoming location heartbeats and timestamps.
Limitations: It detects stale information; it cannot restore missing connectivity.

### Rally points [BETA]
Lets an authorized Crew owner set an active meeting point that members can see with bearing and distance.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/safety/rally-point
Offline: Creating or changing the point requires connectivity.
Background: Foreground map coordination.
Limitations: Bearing depends on a usable self position.

### Emergency contacts [BETA]
Stores people who can be selected as Journey watchers or safety escalation recipients.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/safety/emergency-contacts
Offline: Saving changes requires connectivity.
Background: Contacts are referenced by safety workflows; no passive contact access.
Limitations: Selecting a contact does not itself send a message.

### Subscriptions and entitlements [PARTIAL]
Free and Pro capability/limit checks with RevenueCat purchase and restore integration when offerings are configured for the build.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/settings/subscriptions
Offline: A persisted last-known plan may remain, but purchase/restore requires the store service.
Background: Entitlements refresh from RevenueCat or the server.
Limitations: Purchase UI reports that subscriptions are unavailable if the build has no configured offering. Displayed fallback price is not proof an App Store product is available.

### Approximate location [BETA]
Allows a location to be represented as approximate where the current sharing mode or OS accuracy requires it.
Platforms: ios.
Help: https://navtrl.com/stalkr/help/privacy/approximate-location
Offline: No durable delivery queue.
Background: Follows Live sharing.
Limitations: Approximation is not a promise of anonymity; authorized viewers still receive a location area.

### Scoped privacy and security [BETA]
Uses Crew membership, object ownership, role checks, RLS, storage policies, and capability-scoped Journey watch tokens to limit access.
Platforms: ios, server.
Help: https://navtrl.com/stalkr/help/privacy/who-can-see-my-location
Offline: Cached data can remain on the device until app storage is cleared or account state resets.
Background: Background tasks use a locally published authorized watchlist and authenticated/server-authorized writes where applicable.
Limitations: A Journey watch link is a capability: anyone who has the link may be able to view that Journey until it ends or the capability is revoked by product behavior.

### Android release [IMPLEMENTED_NOT_RELEASED]
Android configuration, permissions, package identity, and internal-track submission settings exist, but repository evidence does not show a public Android release.
Platforms: android.
Help: https://navtrl.com/stalkr/help/getting-started/current-availability
Offline: Same architectural limits as iOS.
Background: Foreground-service configuration exists and still requires release/device validation.
Limitations: Do not tell users STALKR is available on Google Play based on current repository evidence.

### Downloadable offline maps [PLANNED]
A designed future MapLibre/PMTiles offline map system; it is not in the current product.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/limitations/offline-maps
Offline: No downloadable regions or guaranteed offline basemap exist today.
Background: Not implemented.
Limitations: Google Maps cache behavior is opportunistic and must not be called offline map support.

### Offline-first sync and outbox [PLANNED]
A future durable local database and store-and-forward design; current mutations are not queued for later sync.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/limitations/offline-use
Offline: Current remote writes can fail and are not durably replayed.
Background: Not implemented.
Limitations: Do not promise that offline-created Tracks, markers, Zones, SOS messages, or Crew sharing changes will sync later.

### Garmin and inReach integration [PLANNED]
Investigated roadmap work only; there is no current Garmin or inReach connection in STALKR.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/limitations/garmin-inreach
Offline: Not implemented.
Background: Not implemented.
Limitations: No device pairing, MapShare ingestion, or satellite relay is present.

### Satellite transport [NOT_SUPPORTED]
STALKR does not currently send Crew locations, SOS, or Journey data over Apple, Android, or third-party satellite transport.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/limitations/satellite-support
Offline: Not supported.
Background: Not supported.
Limitations: A phone's system satellite emergency features are separate from STALKR and must not be represented as app transport.

### Expedition Mode [PLANNED]
A roadmap concept for off-grid and battery-aware operation; it is not a selectable current mode.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/limitations/expedition-mode
Offline: Not implemented.
Background: Not implemented.
Limitations: Do not describe expedition battery modes as available.

### Route planning and route intelligence [NOT_SUPPORTED]
Current Routes are created from completed Tracks; drawing, importing, optimizing, or turn-by-turn planning a new Route is not supported.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/routes/route-planning-limitations
Offline: Not supported.
Background: Not supported.
Limitations: Following a saved Route is not turn-by-turn navigation.

### Nearby mesh networking [PLANNED]
Roadmap research only; phones do not currently exchange STALKR Crew data directly without infrastructure.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/limitations/offline-use
Offline: Not implemented.
Background: Not implemented.
Limitations: No Bluetooth, Wi-Fi Aware, Nearby Connections, or cross-platform mesh transport exists.

### Weather overlay [PLANNED]
A disabled future flag; there is no current weather layer in the map.
Platforms: not available.
Help: https://navtrl.com/stalkr/help/limitations/current-limitations
Offline: Not implemented.
Background: Not implemented.
Limitations: Do not describe weather data as a current STALKR feature.

### In-app STALKR AI assistant [PLANNED]
The knowledge foundation is being prepared, but no in-app AI safety or help assistant is currently enabled.
Platforms: not available.
Help: https://navtrl.com/stalkr/ai
Offline: Not implemented.
Background: Not implemented.
Limitations: Public documentation is AI-answerable; that is not the same as an in-app assistant.

## Answering rules
Use https://navtrl.com/stalkr/help for focused task instructions and https://navtrl.com/stalkr/help/faq for natural-language questions. Do not describe PLANNED, EXPERIMENTAL, IMPLEMENTED_NOT_RELEASED, PARTIAL dependencies, or NOT_SUPPORTED capabilities as generally available.