> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/events-and-notifications/security/bracelet-or-ankle-sensor.md). # Bracelet or ankle sensor Receive immediate alerts when a GPS bracelet or ankle sensor is removed without authorization. Designed for legal monitoring applications such as house arrest. The **Bracelet sensor** (or **Ankle sensor**) rule is specifically designed for legal monitoring applications involving specialized GPS devices. It is an essential tool for security in contexts such as house arrest or parole. This rule is designed to immediately notify security personnel if a GPS device is removed without authorization. In these situations, the rule triggers an instant alert to the relevant authorities, allowing for quick action to prevent any unauthorized movement or breach of legal conditions. ## Rule settings This rule is entirely dependent on the device's capabilities and hardware configuration. There are no specific settings to configure within the rule itself. For common settings, see [Rules and alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * **Reset timer.** The **Bracelet sensor** alert has a 3-minute reset timer, meaning the alert event doesn't occur more often than once every 3 minutes. If this type of event occurs in time the rule has been waiting for the reset, this event is omitted by the Navixy platform, including the reports. * **Multiple devices:** With this rule, you have the flexibility to select multiple GPS devices for receiving notifications. The only requirement is that the selected GPS devices must support Bracelet sensor events and have this feature integrated into the platform. This allows you to monitor multiple compatible GPS devices simultaneously, ensuring you receive notifications for the relevant events across various vehicles or devices efficiently. * **GPS-independent event alert:** When the platform detects this type of hardware event from GPS device data that lacks valid coordinates, it still registers and displays the event as valid. This applies regardless of whether the event took place inside or outside of the designated geofences. In such cases, the platform disregards the Inside/Outside geofence logic to ensure the event is captured and reported. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/user/guide/events-and-notifications/security/bracelet-or-ankle-sensor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.