> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enigm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Key Overview

> Public architecture model for Enigm Key emergency alerting.

Enigm Key is the physical emergency key device in the Enigm ecosystem. It is designed to help a user trigger an SOS alert from a dedicated compact device without requiring phone unlock or direct app interaction at the moment of activation.

Enigm Key links with an Enigm account through Enigm App and communicates securely with the Enigm platform when an emergency workflow is activated. It is a supporting product: it does not replace Enigm App, secure messaging, secure calls, Device Trust, emergency services, or user account security.

## Overview

Enigm Key is a compact emergency connectivity device with embedded mobile data capability, GNSS positioning, a physical activation button, vibration feedback, and battery-state indicators.

When activated, Enigm Key is designed to:

* Send an emergency alert.
* Notify user-selected contacts inside the Enigm platform.
* Share event-bound location during the active emergency workflow.
* Authenticate device communication.
* Protect communication with encrypted and signed requests.
* Remain dormant during normal non-emergency operation to support user privacy.

## Product Responsibilities

Enigm Key is designed to support:

* Emergency alerting from a dedicated physical device.
* Privacy-preserving standby behavior.
* Secure account association.
* Initial linking through Enigm App.
* User-selected emergency contacts.
* Event-bound location sharing during emergencies until user cancellation.
* Device administration through Enigm App and Enigm Command.
* Device lifecycle revocation if the device is lost, stolen, retired, or replaced.
* Minimal routine data exposure.

The objective is to provide emergency communication capability while preserving Enigm's privacy-first design principles.

## Documentation Map

* [Hardware Model](/key/hardware-model) explains the public device architecture, embedded connectivity, GNSS, power model, and physical interaction design.
* [Emergency Workflow](/key/emergency-workflow) explains activation, contact notification, cancellation, and event lifecycle.
* [Security Model](/key/security-model) explains authentication, request integrity, encrypted communication, and revocation.
* [Privacy and Data Lifecycle](/key/privacy-lifecycle) explains dormant behavior, location-sharing boundaries, retention, and emergency data minimization.

## Management Surfaces

Enigm Key has two management surfaces with different responsibilities.

| Surface       | Responsibility                                                                                                                                        |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enigm App     | Initial linking, account association, emergency contact configuration, emergency event visibility, revocation, replacement, and device loss handling. |
| Enigm Command | Associated device visibility, lifecycle visibility, revocation, replacement state, loss handling, and emergency event visibility where authorized.    |

Enigm Command is not the initial linking surface and is not the emergency contact configuration surface. Enigm Command visibility must remain limited to authorized lifecycle and event context; it must not become routine location tracking or protected communication visibility.

## Product Boundaries

Enigm Key is a user-controlled alerting workflow, not an emergency service, public safety answering point, medical response service, law-enforcement dispatch service, rescue service, or guaranteed response system.

Emergency alert delivery and location sharing depend on device state, battery state, mobile connectivity, GNSS availability, service availability, account association, selected contacts, and user configuration.

See [Platform Limitations](/legal/limitations).