Policy center

Safety & Field Check-ins

The owner-adopted limitations for maps, location sharing, Field Check-ins, and field delivery.

Effective Content revision September 1, 2026

Current release status

This owner-adopted Safety disclosure is scheduled to become effective prospectively with the exact version shown and is not represented as reviewed by licensed counsel. Field Check-ins and consent-aware party-map records exist, but no push, SMS, or outbound safety-email delivery channel is launch-approved.

Do not rely on LimitLine to summon help, deliver an urgent message, continuously track a person, or confirm that someone is safe. This limitation remains in force unless a later effective Safety version expressly identifies an enabled, production-proven channel.

Not an emergency or rescue service

LimitLine does not monitor trips as emergency dispatch, contact public-safety agencies, guarantee rescue, provide medical advice, or replace 911 or the appropriate local emergency number. In an emergency, use the most reliable available means to contact emergency services and people who know the area.

Field Check-ins

A Field Check-in is a user-created plan and record. It may include an expected return, selected contacts, and discrete location captures. An intended guardian must accept the relationship before authorized sharing. A check-in can be late because of missed input, power loss, poor service, device settings, clock errors, or provider failure.

A late, missing, or stale update does not prove distress. A recent update does not prove safety. Users and guardians need an independent plan that defines when and how to act.

Party location

Party-map locations are explicit, permission-based observations, not continuous or guaranteed background tracking. The interface must show capture time and staleness. Users must not infer movement, route completion, or current presence from an old point.

Maps, routes, weather, and analysis

Suggested routes and stand options may miss houses, roads, fences, water, cliffs, restricted areas, weather changes, other people, or ground conditions. Map and analysis output is planning context, not a safety score or instruction to enter an area.

Verify access, permission, structures, roads, terrain, weather, fire conditions, daylight, water, communication coverage, and personal ability using current independent sources.

Independent safety plan

LimitLine will not describe safety delivery as dependable unless recipient verification, provider authorization, retries, receipts, dead-letter handling, monitoring, response coverage, device and carrier tests, outage behavior, and two-account production journeys pass on the exact release.

  • Tell a trusted person where you are going and when to act even if LimitLine is unavailable.
  • Carry appropriate navigation, power, communications, weather protection, water, first aid, and emergency equipment for the trip.
  • Use device and carrier tools designed for the remoteness and risk of the area.

Content identity

sha256:1e04fc6d8ba0e4cd799211ebe51f478f6c914eea848b8fc634e61f972d5f3c73