Source: https://weartags.com/ WearTags for Kids · In development # A wearable safety system for kids. **Find them. Identify them. Notify you. Help others help them.** WearTags is being designed to combine wearable technology, location services, emergency notifications, and the emergency-access technology behind WearableDocs, so a child's safety system does not stop at a dot on a map. The wearable is one part of the system. ## When a child is missing, the map is only the beginning. A tracker can help a parent find a location. Real situations tend to keep going after that. A child can leave an expected area. A caregiver can lose contact. A child can be found by someone who does not know who they are. A parent may need to reach other people quickly. Emergency information may matter to whoever is standing there. Afterward, everyone may need to understand what actually happened. > Finding a child is only part of what happens when something goes wrong. WearTags uses layered safety technology designed to help caregivers stay informed when something changes. The system is being designed so that when one safety layer fails, other layers can continue providing useful information. ## Five jobs, not one. WearTags is being designed around the whole chain of events, from the moment something is unusual to the record of what happened. 1. **Find.** GPS/GNSS, cellular, Wi-Fi, Bluetooth and compatible finding technologies can offer different ways to help locate a wearable. 2. **Identify.** A wearable can give someone who finds a child a simple, controlled way to reach the right person. 3. **Notify.** Parents and designated contacts can be alerted when events you have defined actually occur. 4. **Respond.** Emergency information can be made available through a controlled web experience, to the people who need it. 5. **Document.** Events, notifications and authorized access can form a record that holds up when someone asks what happened. ## More than a tracker. GPS tells you where a device is. WearTags is being designed around what happens next. Location → Alert → Find → Identify → Respond → Document > The system should not stop at the map. ## What happens when someone finds your child? A child can be found by a passerby, another parent, school staff, security, or emergency personnel. That person will not have your app. They may not know your child's name. They will not know who to call. We are designing the wearable to open a controlled web interaction for exactly that moment, through technologies such as NFC or QR, depending on the final hardware. 1. **Tap or scan.** The person who found your child interacts with the wearable using an ordinary phone. No app, no account. 2. **A controlled page, not a profile.** They reach a page that shows only what you have authorized for this moment. Not your address, not your child's school, not your phone number, not where your family has been. 3. **They reach you without being given your number.** The page is intended to relay the finder to you, and to let them share their own location if they choose. Helping should not require handing a stranger your family's contact details. 4. **You are notified.** You learn that the wearable was scanned, rather than waiting to be called. 5. **Emergency information, if it applies.** Where you have authorized it, information that matters in an emergency can be shown to whoever is standing there. ## When something is wrong, the system should change gears. Ordinary days and bad days are not the same problem. The system is intended to have a distinct emergency state that behaves differently from everyday use. - Increased location attention where hardware, battery and network conditions allow it. - Parent and guardian alerts, and notifications to contacts designated in advance. - Live or recent location information presented alongside what else has happened. - Emergency information made available to those who need it, on your terms rather than by default. - Events as they occur, in order, rather than reconstructed from memory afterward. - A record of who reached what, and when. Actual behavior will depend on hardware, battery, connectivity, configuration and the final product design. We will publish what it really does when the hardware is real, rather than promising update intervals we cannot yet stand behind. ## No single tracking technology solves every situation. Each of these is good at something and blind to something else. The design intent is to use them together rather than to bet on one. - **GPS / GNSS.** Outdoor positioning. The familiar layer, and the one most affected by buildings, tunnels and dense cities. - **Cellular.** Independent communication. A path that does not depend on a parent's phone being nearby. - **Wi-Fi.** Where GPS struggles. Additional positioning capability indoors and in places where satellite signal is weak. - **Bluetooth.** Low-power proximity. Short-range presence and device communication, at a fraction of the power cost. - **Finding networks.** Potential additional recovery. Compatible ecosystem technologies may add recovery capability where it is technically and commercially possible. - **NFC / QR.** In-hand identification. The layer that matters once a person is physically holding the child or the wearable. Ecosystem integrations are subject to technical, certification, licensing and partnership requirements. We are not claiming any company's finding network is integrated today. When one is, this page will say which. ## Layers, so that one failure is not the whole failure. Any single safety mechanism can fail. A battery runs down, a network drops, a device comes off. A system built on one mechanism fails completely when that one thing goes wrong. So WearTags is being designed in layers, where each layer keeps producing something useful after another has stopped. - **Separation and tamper awareness.** The system is being designed to notice when something changes, including a device that appears to have been separated from the child. - **Last known information is kept.** If reporting stops, the last confirmed location and time remain available rather than disappearing with the signal. - **State, not just position.** Battery level and connectivity state are information in their own right. "Quiet because it is off" and "quiet because there is no coverage" are different answers. - **Movement and anomaly awareness.** Patterns that do not fit the ordinary day are worth surfacing to a caregiver, not just raw coordinates. - **Geofence and SOS.** Alerts when a defined area is left, and a way for a child to ask for help directly. - **Timestamped and sealed.** Events carry a time and become part of a record, using the integrity technology already built for WearableDocs. ### What we publish, and what we do not We will publish what the system does, how your information is handled, and what we can and cannot promise. We do not publish the internal engineering of the hardware. That is deliberate, and it is the same reasoning any serious safety product applies: design details that would help someone interfere with a child's safety device are not marketing material. What we will always tell you is what the product does for you and what it does with your data. ## Built by the people behind WearableDocs. WearableDocs was built around a simple problem: important information is useless if the right person cannot find it when it matters. WearTags takes that thinking into child safety. - Location tells you where. - The wearable helps identify. - Notifications tell the right people. - The emergency record helps others respond. - The access record helps document what happened. [Explore WearableDocs](https://wearabledocs.com/) ## When something happens, the timeline matters. Afterward, the question is always the same: what happened, in what order, and who knew what. That is a record, and records are the part we have already built once. **Conceptual example.** Illustrative only. This is a design concept, not a representation of final product behavior or timing. | Time | Event | |---|---| | 2:14 PM | Child leaves expected area. | | 2:15 PM | Parent receives alert. | | 2:17 PM | Location update received. | | 2:19 PM | Parent activates emergency response. | | 2:24 PM | Wearable is scanned. | | 2:24 PM | Parent is notified. | | 2:25 PM | Authorized emergency information is accessed. | | 2:26 PM | Event is added to the record. | ## Where WearTags is meant to sit. Every category below solves something real. The gap we are designing for is that no single one of them covers the whole chain. Categories, not brands. "Designed for" means intended architecture, not a capability that ships today. | Capability | Traditional ID tag | Bluetooth tracker | GPS tracker | GPS smartwatch | WearTags | |---|---|---|---|---|---| | Location | No | Proximity | Yes | Yes | Designed for | | Wearable identification | Yes | No | Limited | Limited | Designed for | | Parent notification | No | Limited | Yes | Yes | Designed for | | Emergency information | Engraved only | No | No | Limited | Designed for | | Finder interaction | Read it aloud | No | No | Limited | Designed for | | Event timeline | No | No | Location history | Location history | Designed for | | Controlled access | No | No | No | No | Designed for | | Integrity record | No | No | No | No | Designed for | ## Built for families, not for a niche. Separation is not a rare event that happens to other people. It happens at festivals, in parking lots, on field trips, at the beach, and on the walk home. Parents of young children. Families with children who wander. Children who travel or attend camps. School-age children. Families who want an everyday safety layer. Caregivers. Schools and child-care organizations. Child-safety organizations. ## Help shape the first WearTags. We are designing WearTags now. If enough families want this, we want to build it with them, rather than disappear for two years and come back with a finished product no one asked for. Join the early list to hear about prototypes, product decisions, launch timing, and any future crowdfunding campaign. The form asks for an email address and, optionally, whether you are a parent or caregiver, a child-safety professional, a school or childcare organization, a technology or hardware professional, a potential partner, or an interested supporter. No purchase. No commitment. Just updates. ## This is early. The product is being designed now. We would rather show you what we are building than pretend every specification has already been decided. Hardware, connectivity, wearing options, integrations, pricing and launch timing will be published as they become real. --- WearTags is in development. Features, hardware, connectivity, integrations, pricing and availability are subject to change. Location and communication services depend on device, battery, network and environmental conditions. **No safety product can guarantee that an incident will be prevented, detected, or that a missing child will be recovered, and WearTags does not claim otherwise.** WearTags is not a substitute for appropriate supervision or emergency services. WearTags for Kids is a product of WearableDocs. Contact: hello@wearabledocs.com © 2026 WearableDocs. All rights reserved.