{"id":20035,"date":"2026-08-26T14:40:38","date_gmt":"2026-08-26T06:40:38","guid":{"rendered":"https:\/\/www.lansitec.com\/?p=20035"},"modified":"2026-08-26T10:48:04","modified_gmt":"2026-08-26T02:48:04","slug":"connected-worker-tracking","status":"publish","type":"post","link":"https:\/\/www.lansitec.com\/ko\/blogs\/\uc5f0\uacb0\ub41c-\uc791\uc5c5\uc790-\ucd94\uc801\/","title":{"rendered":"\uc5f0\uacb0\ub41c \uc791\uc5c5\uc790 \ucd94\uc801: \uac1c\uc778\uc815\ubcf4 \uce68\ud574 \ubb38\uc81c \uc5c6\uc774 \uc791\uc5c5\uc790 \uc548\uc804\uc744 \ud5a5\uc0c1\uc2dc\ud0a4\ub294 \ubc29\ubc95"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Connected worker tracking can shorten emergency response times, warn people before they enter dangerous areas, and help rescue teams locate someone after a fall. It can also create a detailed record of where each employee went and how long they stayed there, and here is where the problems start.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We\u2019ve seen tracking projects generate genuine enthusiasm among safety and operations teams, only to slow down when HR, legal, or worker representatives become involved. Their concern is rarely the tracking technology itself. It is the possibility that a safety system could quietly become a surveillance system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Privacy should therefore be a deployment requirement from the beginning, not a compliance task added after the pilot. The objective is straightforward: collect enough information to protect people without creating an unnecessary record of their working day.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Worker Tracking vs Employee Surveillance: What Is the Difference?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A worker presses a panic button inside a chemical plant. The response team needs an accurate location immediately. That is a clear safety purpose.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A manager later opens the same system to compare how long individual employees spent in different work areas. The data has not changed, but the purpose has. What began as emergency tracking now supports performance monitoring. This is where many projects get into trouble.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Under the EU General Data Protection Regulation, organizations must define why they process personal data, collect only what that purpose requires, and avoid keeping it longer than necessary. GDPR Article 25 also requires data protection by design and by default. In contrast, Article 35 may require a Data Protection Impact Assessment when processing is likely to create a high risk to people\u2019s rights and freedoms. <sup><a href=\"#references\" data-type=\"internal\" data-id=\"#references\">(1)<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A device identifier can also count as personal data even if the database does not display a worker\u2019s name. If another table connects helmet ID A0372 to a named employee, the location record remains identifiable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Privacy by design must therefore cover the complete system:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The wearable and its configuration<\/li>\n\n\n\n<li><a href=\"https:\/\/www.lansitec.com\/ko\/\uac8c\uc774\ud2b8\uc6e8\uc774\/\">Gateways<\/a>, network servers, and positioning engines<\/li>\n\n\n\n<li>Maps, dashboards, databases, and exports<\/li>\n\n\n\n<li>The people and processes that can access the information<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Encryption matters, but it is only one layer. For example, the Lansitec <a href=\"https:\/\/www.lansitec.com\/products\/helmet-tracker-sensor\/\" data-type=\"page\" data-id=\"1237\">LoRaWAN Helmet Sensor<\/a> uses AES128 for its <a href=\"https:\/\/www.lansitec.com\/ko\/\ub85c\ub77c\uc644\/\">LoRaWAN<\/a> communication. That protects data transmission, but it does not decide whether a supervisor should see six months of movement history. The deployment owner must make that decision in the application and its operating policies.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-1024x576.png\" alt=\"Connected Worker Tracking\" class=\"wp-image-20044\" title=\"\" srcset=\"https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-1024x576.png 1024w, https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-300x169.png 300w, https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-768x432.png 768w, https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-1536x864.png 1536w, https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-18x10.png 18w, https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-360x203.png 360w, https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking-600x338.png 600w, https:\/\/www.lansitec.com\/wp-content\/uploads\/2026\/08\/Connected-Worker-Tracking.png 1920w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><figcaption><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How to Define a Clear Purpose for Worker Tracking<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cWorker tracking\u201d is too broad to guide a privacy-conscious deployment. Define the exact safety outcomes instead. A suitable purpose statement might read:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The system detects worker-initiated alarms, falls, entry into defined hazardous zones, and overstays in controlled areas. It provides location information to authorized responders during an active safety event or evacuation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That statement sets useful boundaries. It does not authorize productivity scoring, continuous attendance analysis, route optimization by individual, or disciplinary monitoring.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Purpose limitation also prevents quiet expansion after deployment. If management later wants to use location histories for another reason, the organization should conduct a separate necessity, proportionality, and legal-basis assessment. Safety data should not automatically become performance data simply because the dashboard makes it possible.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How Event-Based Worker Tracking Protects Privacy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not everyone needs a live map of every worker. A privacy-conscious system can keep routine visibility coarse while revealing more detail during defined events. Under normal conditions, the dashboard might show only:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The number of people present in each safety zone<\/li>\n\n\n\n<li>Whether assigned wearables are online<\/li>\n\n\n\n<li>Unresolved fall, panic, overstay, or zone alerts<\/li>\n\n\n\n<li>The evacuation status of a work area<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">When a worker presses the panic button, the system can expose that person\u2019s current or last known location to the authorized response team. The same rule can apply after a fall alarm, during an evacuation, or when someone overstays in a confined space.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is emergency-only visibility. It gives responders what they need without turning routine operations into continuous observation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/www.lansitec.com\/products\/helmet-tracker-sensor\/\">Lansitec Helmet Sensor<\/a> provides a practical foundation for this approach. It supports GNSS positioning outdoors, Bluetooth positioning indoors, configurable reporting intervals, wear and fall detection, panic alarms, zone alerts, and overstay alarms. However, the customer\u2019s chosen platform must enforce who can see the resulting data and under what conditions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Role-Based Access for Worker Location Data<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A common implementation mistake is to give managers the same access as emergency responders. It is easy to configure, but difficult to justify.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Assign permissions according to operational need:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Role<\/strong><\/th><th><strong>Appropriate access<\/strong><\/th><th><strong>Access to avoid by default<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Emergency responder<\/td><td>Precise location during an active alarm, evacuation, or rescue<\/td><td>Routine historical movement<\/td><\/tr><tr><td>EHS manager<\/td><td>Safety alerts, incident records, zone-risk trends<\/td><td>Unrelated off-incident tracking<\/td><\/tr><tr><td>Line supervisor<\/td><td>Headcount, device status, unresolved alerts<\/td><td>Continuous individual location history<\/td><\/tr><tr><td>HR<\/td><td>Policies, complaints, and approved incident documentation<\/td><td>Live worker maps<\/td><\/tr><tr><td>IT administrator<\/td><td>Device health, configuration, pseudonymous device IDs<\/td><td>Worker identity mapping where unnecessary<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Separate identity data from location data where practical. An IT administrator may need to troubleshoot a helmet sensor without knowing who wears it. A responder may need the identity-location connection during an emergency. Neither requirement justifies giving every administrator unrestricted access to both datasets.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Privileged access should also require individual accounts. Shared \u201ccontrol room\u201d credentials make it impossible to establish who viewed or exported a worker\u2019s history.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How Long Should Worker Location Data Be Stored?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Continuous tracking can produce an enormous volume of location data. Keeping all of it \u201cjust in case\u201d increases legal, cybersecurity, and employee-relations risk without necessarily improving safety.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create a retention schedule for each data category rather than one blanket period:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Data category<\/strong><\/th><th><strong>Practical retention approach<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Live location<\/td><td>Use for current operations; avoid retaining a continuous trail unless required<\/td><\/tr><tr><td>Routine zone presence<\/td><td>Delete or aggregate after the operational need ends<\/td><\/tr><tr><td>Panic, fall, or overstay event<\/td><td>Retain under the approved incident-investigation policy<\/td><\/tr><tr><td>Device diagnostics<\/td><td>Keep separately from worker identity where possible<\/td><\/tr><tr><td>Aggregated safety trends<\/td><td>Retain longer only after effective de-identification<\/td><\/tr><tr><td>Visitor badge assignment<\/td><td>Expire after the visit and a short reconciliation period<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">There is no universal retention period that fits every deployment. Occupational safety rules, incident-investigation requirements, insurance obligations, and national employment laws vary. GDPR Article 88 specifically allows EU member states to introduce more detailed employment-processing rules. <sup><a href=\"#references\" data-type=\"internal\" data-id=\"#references\">(1)<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The important point is to choose and document each period before collection begins. Deletion should then happen automatically. A policy that says \u201cdelete after 30 days\u201d has little value if no process actually removes the records from the main database, exports, and backups.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Use Worker Tracking Data Without Identifying Employees<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Connected worker systems can reveal useful patterns without naming individuals. Safety teams may want to know:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which hazardous zones generate the most alerts<\/li>\n\n\n\n<li>When overcrowding or overstay events occur<\/li>\n\n\n\n<li>How long evacuation headcounts take<\/li>\n\n\n\n<li>Whether particular areas have weak positioning coverage<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These questions usually require trends, not individual movement trails. Aggregation reduces privacy risk, but it does not eliminate it automatically. A report showing that \u201cone worker\u201d spent 47 minutes in a restricted room may still identify that person. Set minimum group sizes, suppress very small groups, remove unnecessary timestamps, and review whether combinations of shift, role, and location could reveal an individual.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pseudonymization and anonymization are also different. Replacing an employee\u2019s name with a device number is pseudonymization if the organization can reconnect the number to the person. The data still falls within data-protection rules.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Handle Visitor Tracking and Temporary Badges<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Visitor badges create a smaller but easily overlooked privacy issue. Guests may not attend the worker briefing, understand site terminology, or expect their movement to be recorded.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use a temporary visitor identifier and keep the identity mapping in the reception or access-control system. Explain what the badge does when issuing it, especially if it generates zone-entry alerts. Access should expire automatically at the end of the visit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not reuse the previous visitor\u2019s assignment record when handing the badge to someone new. The physical device can be reused, but the identity association and session data should be closed first.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For many sites, visitor tracking can remain strictly event-based: entrance confirmed, restricted-zone warning, <a href=\"https:\/\/www.lansitec.com\/ko\/blogs\/\ube44\uc0c1-\uc9d1\uacb0\/\">emergency mustering<\/a>, and badge return. A detailed historical route usually adds little value.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Workers Should Know About Location Tracking<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A vague statement such as \u201ctracking is used for safety and operational purposes\u201d will not build trust. It also leaves too much room for interpretation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Workers should receive plain-language answers to four questions:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>What events and location data does the device collect?<\/li>\n\n\n\n<li>Who can see live and historical information?<\/li>\n\n\n\n<li>How long is each type of record kept?<\/li>\n\n\n\n<li>Can the data be used for performance or disciplinary decisions?<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Communication should happen before the pilot, not after workers notice new <a href=\"https:\/\/www.lansitec.com\/ko\/\uc13c\uc11c\/\">sensors<\/a> on their helmets.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consultation matters too. Safety representatives, unions, works councils, HR, IT security, and the Data Protection Officer may identify problems that the technical team cannot see. For example, continuous GNSS reporting may continue during a lunch break outside the facility. The solution could instead pause identity-linked tracking outside working hours, use a docking process at shift end, or restrict reporting to the worksite.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not assume that employee consent solves the problem. EU guidance recognizes the imbalance between employers and employees, which often makes workplace consent unsuitable as the primary legal basis. (3)(4) The organization must identify an appropriate legal basis and demonstrate that the tracking remains necessary and proportionate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Audit Access to Worker Location Data<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the platform records workers, it should also record how administrators use the platform.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Audit logs should capture:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Who viewed precise location data<\/li>\n\n\n\n<li>Which worker or device record they opened<\/li>\n\n\n\n<li>When they exported, changed, or deleted information<\/li>\n\n\n\n<li>Whether access related to an alarm, investigation, or approved support task<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Review these logs. Do not collect them merely to satisfy a checklist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sensitive actions can require a reason code, ticket number, or incident ID. Some deployments may also benefit from two-person approval before exporting a long movement history.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Remember that audit logs contain personal data about administrators. Restrict and retain them according to their own documented purpose.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Test Worker Tracking Privacy Before Deployment<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A technical pilot asks whether the system can locate a worker. A privacy test asks whether it behaves properly when nobody is in danger.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before going live, test scenarios such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A supervisor attempts to view an employee with no active alarm.<\/li>\n\n\n\n<li>An administrator exports more history than their role permits.<\/li>\n\n\n\n<li>A visitor badge remains associated with its previous wearer.<\/li>\n\n\n\n<li>A worker leaves the site while still wearing the device.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A Data Protection Impact Assessment provides a structured way to examine these risks. The European Data Protection Board recommends applying data protection by design throughout the processing lifecycle, from selecting technology and default settings to deletion and retirement. <sup><a href=\"#references\" data-type=\"internal\" data-id=\"#references\">(2)<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do this work while configuration choices remain open. Privacy becomes much more expensive once dashboards, integrations, and management expectations have already formed around unrestricted data.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Can Worker Tracking Improve Safety Without Continuous Surveillance?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Connected worker tracking can protect people without documenting every movement indefinitely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Start with a narrow safety purpose. Keep routine visibility coarse. Reveal precise location during defined emergencies. Separate operational roles, limit retention, aggregate analytics, explain the system clearly, and audit access.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The technology can support both safety and surveillance. Privacy by design is what determines which system you actually deploy.<\/p>\n\n\n<div\n\tclass=\"betterdocs-faq-wrapper layout-modern icon-after betterdocs-faq-layout-1 betterdocs-faq-wc0qdxb betterdocs-shortcode\">\n\t<h2 class=\"betterdocs-faq-layout-1 betterdocs-faq-wc0qdxb betterdocs-faq-section-title\">Frequently Asked Questions<\/h2>\n\t<div class=\"betterdocs-faq-inner-wrapper\">\n\t\t<div class=\"betterdocs-faq-title\">\n\t<h3 class=\"betterdocs-faq-title-tag\">About Connected Worker Tracking<\/h3><\/div>\n<ul class=\"betterdocs-faq-list\"><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tIs employee location tracking legal?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p><span style=\"font-weight: 400\">It can be, but legality depends on the purpose, necessity, proportionality, legal basis, transparency, safeguards, and applicable national employment law. An organization should assess these factors before deployment and complete a DPIA where the processing is likely to create a high risk.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tShould workers be tracked continuously?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p><span style=\"font-weight: 400\">Not automatically. Continuous tracking should require a clear operational justification. Many safety use cases can rely on zone status, device heartbeat, or event-triggered access to precise location instead of retaining a complete movement history.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tCan an employer rely on employee consent?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p><span style=\"font-weight: 400\">Often not as the primary basis. The power imbalance in an employment relationship can prevent consent from being freely given. Employers should obtain jurisdiction-specific advice and identify the appropriate legal basis before processing begins.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tHow long should worker location data be stored?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p><span style=\"font-weight: 400\">There is no single correct period. Live location, safety incidents, device diagnostics, access events, and aggregated statistics serve different purposes and should have separate retention rules. Keep identifiable data only as long as its documented purpose requires.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tDoes encryption make a worker tracking system private?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\">\n\t<p><span style=\"font-weight: 400\">No. Encryption protects data in transit or storage, but it does not control why the data is collected, who can view it, how it is used, or when it is deleted. Privacy requires both technical and organizational controls.<\/span><\/p>\n<\/div>\n<\/div><\/li><\/ul><script type=\"application\/ld+json\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Is employee location tracking legal?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">It can be, but legality depends on the purpose, necessity, proportionality, legal basis, transparency, safeguards, and applicable national employment law. An organization should assess these factors before deployment and complete a DPIA where the processing is likely to create a high risk.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Should workers be tracked continuously?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">Not automatically. Continuous tracking should require a clear operational justification. Many safety use cases can rely on zone status, device heartbeat, or event-triggered access to precise location instead of retaining a complete movement history.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Can an employer rely on employee consent?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">Often not as the primary basis. The power imbalance in an employment relationship can prevent consent from being freely given. Employers should obtain jurisdiction-specific advice and identify the appropriate legal basis before processing begins.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"How long should worker location data be stored?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">There is no single correct period. Live location, safety incidents, device diagnostics, access events, and aggregated statistics serve different purposes and should have separate retention rules. Keep identifiable data only as long as its documented purpose requires.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Does encryption make a worker tracking system private?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">No. Encryption protects data in transit or storage, but it does not control why the data is collected, who can view it, how it is used, or when it is deleted. Privacy requires both technical and organizational controls.<\\\/span><\\\/p>\"}}]}<\/script>\t<\/div>\n<\/div>\n\n\n\n<div id=\"references\"><\/div>\n\n\n\n<h4 class=\"wp-block-heading\">References<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li><a href=\"https:\/\/eur-lex.europa.eu\/eli\/reg\/2016\/679\/oj\/eng\" target=\"_blank\" rel=\"noopener\">Regulation (EU) 2016\/679, including Articles 5, 25, 35, and 88<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.edpb.europa.eu\/documents\/guideline\/guidelines-42019-on-article-25-data-protection-by-design-and-by-default_en\" target=\"_blank\" rel=\"noopener\">European Data Protection Board: Guidelines 4\/2019 on Data Protection by Design and by Default<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/ec.europa.eu\/newsroom\/article29\/items\/610169\" target=\"_blank\" rel=\"noopener\">Article 29 Working Party: Opinion 2\/2017 on Data Processing at Work<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/commission.europa.eu\/law\/law-topic\/data-protection\/rules-business-and-organisations\/legal-grounds-processing-data\/grounds-processing\/when-consent-valid_en\" target=\"_blank\" rel=\"noopener\">European Commission: When Is Consent Valid?<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Connected worker tracking can shorten emergency response times, warn people before they enter dangerous areas, and help rescue teams locate someone after a fall. It can also create a detailed record of where each employee went and how long they stayed there, and here is where the problems start. We\u2019ve seen tracking projects generate genuine&hellip;&nbsp;<a href=\"https:\/\/www.lansitec.com\/ko\/blogs\/\uc5f0\uacb0\ub41c-\uc791\uc5c5\uc790-\ucd94\uc801\/\" rel=\"bookmark\">\ub354 \ubcf4\uae30 \u00bb<span class=\"screen-reader-text\">\uc5f0\uacb0\ub41c \uc791\uc5c5\uc790 \ucd94\uc801: \uac1c\uc778\uc815\ubcf4 \uce68\ud574 \ubb38\uc81c \uc5c6\uc774 \uc791\uc5c5\uc790 \uc548\uc804\uc744 \ud5a5\uc0c1\uc2dc\ud0a4\ub294 \ubc29\ubc95<\/span><\/a><\/p>","protected":false},"author":1,"featured_media":20043,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","footnotes":""},"categories":[19],"tags":[266,84,267,100],"class_list":["post-20035","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-iot-education","tag-helmet-sensor","tag-helmet-tracker","tag-lorawan-helmet-sensor","tag-smart-helmet-for-industrial-workers"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/posts\/20035","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/comments?post=20035"}],"version-history":[{"count":2,"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/posts\/20035\/revisions"}],"predecessor-version":[{"id":20045,"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/posts\/20035\/revisions\/20045"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/media\/20043"}],"wp:attachment":[{"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/media?parent=20035"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/categories?post=20035"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lansitec.com\/ko\/wp-json\/wp\/v2\/tags?post=20035"}],"curies":[{"name":"\uc6cc\ub4dc\ud504\ub808\uc2a4","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}