Wireless sensors and Yggio, the open operational layer for cities, property owners and transport operators. Your data, your operations, your sovereignty.

Trust & sovereignty

Your data, your operations, your sovereignty

How we work everywhere and, rule by rule in the EU and in the United States, what Yggio and our sensors do and what stays with you.

Our strengths

European by default

Sensative AB is a Swedish company. Yggio is developed and operated entirely by our own staff in Sweden; our sensors are developed in Sweden and made in Poland. For customers in the EU/EEA, the UK and Switzerland, Yggio as a service is hosted in the EU/EEA by Cleura AB, a Swedish cloud provider. Yggio also runs entirely on your own servers or at the edge.

Open, so you can always leave

An open API, one FIWARE NGSI-LD data model, open-source payload decoders for our sensors, and Yggio as your own LoRaWAN join server, so no third party holds your device keys. You own your data, and you can take it with you.

Tested and governed

An independent penetration test of Yggio by Outpost24 Ghost Labs in January–February 2026 covered 134 risk categories and found no critical, high or medium issues. Information security is managed with reference to ISO/IEC 27001, with a risk register, an incident process and a contingency plan.

A city of homes, a hospital, transport and utilities connected to one digital domain, with services for citizens, mobility, healthcare, environment and security on top
Users and services connected to one digital domain, run by the domain owner.

Security by design, not secured afterwards

Security is treated as a property of the platform: architecture, operations and independent validation reinforce each other.

1

Secure architecture

  • Zero-trust architecture
  • Keycloak identity and least-privilege access
  • Customers isolated from each other, with no data duplicated between them
  • Hardened NGINX, RabbitMQ and Keycloak at the core
2

Secure development and operations

  • 15 required automated checks on every change, with test suites run against real services
  • Container images scanned for known vulnerabilities (CVEs)
  • Continuous monitoring and intrusion detection
  • Backups and a documented incident process
3

Validated

  • Independent penetration test by Outpost24 Ghost Labs, January–February 2026
  • 134 risk categories across 16 security domains
  • No critical, high or medium findings
  • Remediation tracked; reviewed every two weeks
0critical, high or medium findings
134risk categories tested
16security domains

How we work, everywhere

The same practices apply to every customer, wherever they are.

Security management

  • Information security managed with reference to ISO/IEC 27001, under a named management-system owner.
  • A risk register reviewed at least once a year and whenever something significant changes; security reviewed every two weeks and in an annual security and privacy review.
  • A documented incident process, and a contingency plan for Yggio as a service with backups at least every 24 hours.
  • Staff and contractors sign confidentiality agreements; access is granted and withdrawn through onboarding and offboarding routines.

Tested, and open to reports

  • An independent penetration test of Yggio by Outpost24 Ghost Labs, January–February 2026, found no critical, high or medium issues.
  • Vulnerabilities can be reported to security@sensative.com, published in security.txt.
  • Translators, the code that decodes device data, run in a sandbox with no access to the network, the file system or the host.

Identity, access and logs

  • Single sign-on through Keycloak: SAML 2.0, LDAP, Active Directory, OAuth 2.0 and OpenID.
  • Access rights per resource, roles and user groups, inherited down the organisation tree, and withdrawn at once.
  • Customers are isolated from each other and no data is duplicated between them; when access is withdrawn, the data disappears from that user’s view at once.
  • Every access-rights change is logged and kept for ten years; device history is kept per connector for as long as you set.

Devices and updates

  • Our sensors are developed in Sweden and manufactured in the EU by our production partner JME in Gliwice, Poland.
  • Every LoRaWAN sensor has its own identity (DevEUI) and a unique, randomly generated key; no keys are printed on the device, and LoRaWAN encrypts each message with AES-128.
  • Every sensor is tracked in our build system from production onwards, for complete fleet traceability; over NFC a customer reaches only its own devices.
  • Strips for LoRaWAN have fixed firmware by design: no writable bootloader, so no path to inject code. Their radio only listens briefly after its own transmissions, and they hold no IP stack and no personal data.
  • Square and Puck firmware is updated over NFC, at the device, after its ownership is checked in Yggio. Their VSM apps update over NFC or LoRaWAN, run in a sandbox, and every change is permissioned and logged in Yggio.
  • Yggio is one continuously updated platform with no customer forks, released every 8–12 weeks after staged quality assurance.

Software you can account for

  • Sensative-owned core code, permissive open-source components and no proprietary platform runtime. The Ratatosk context broker is Apache 2.0.
  • Yggio ships as containers; a software bill of materials (SBOM) is generated in every build and its components are monitored for known vulnerabilities.
  • Security fixes are shipped separately from functional updates.
  • Every change passes 15 required automated checks (build, static analysis, licences, coverage and 13 test suites against real services) before an engineer reviews it, and the main branch only accepts changes through a merge queue.

Your data, your choice of where

  • You own the data in Yggio and can take it with you: one open API, the FIWARE NGSI-LD data model, export through the standard functions, and for 30 days after an agreement ends.
  • Yggio runs as a service, on your own servers or at the edge. Yggio can be your own LoRaWAN join server, so device keys need not sit with a third party.
  • Open-source payload decoders for our sensors are on GitHub.

AI under rules

  • Customer data and personal data are never sent to an external AI service by us, and never used to train a model.
  • AI we operate is disclosed as AI, and a named person stays accountable for what it produces.
  • The Yggio AI Assistant runs on your own Anthropic or OpenAI account, with a daily token limit you set.
Our AI policy

In the EU

For customers in the EU/EEA and, for hosting, the UK and Switzerland. One card per rule. The status line says where the rule stands today; the last line says what remains your responsibility. This page explains; it is not legal advice, and the agreements below are what bind us.

GDPR

General Data Protection Regulation (EU) 2016/679 In force since May 2018

What it asks. Personal data is processed lawfully, securely and only as far as needed, and a processor works under a written agreement with the controller.

What Yggio and Sensative do

  • Our Data Processing Addendum (Rev B): we process only on your instructions and notify a personal data breach within 24 hours.
  • New sub-processors are announced 30 days in advance, and you may object. The current list is below.
  • For customers in the EU/EEA, the UK and Switzerland, personal data is processed and stored in the EU/EEA unless agreed otherwise.
  • Access rights per resource, single sign-on, and an access log kept for ten years. History is kept per connector for as long as you set, from two days to indefinitely.
  • Occupancy sensors detect presence, not people: no cameras and no images.
  • When the agreement ends, you can export your data for 30 days; then we delete or return it.

What stays with you. You are the controller: you decide the purposes, the legal basis and the retention periods, and carry out a DPIA where one is needed.

NIS2

Directive (EU) 2022/2555 on cybersecurity Applies through national law; in Sweden, the Cybersecurity Act (cybersäkerhetslagen)

What it asks. Essential and important entities, among them many municipalities and water, energy and transport operators, manage their cyber risks, including those in their supply chain, and report significant incidents.

What Yggio and Sensative do

  • Everything under How we work, everywhere (information security management, incident process, contingency plan, penetration testing, single sign-on and audit logs) is what you can bring into your own NIS2 risk management and supplier assessment.
  • Yggio on your premises or at the edge connects outbound only, so no inbound port is opened in your network. Or it runs entirely inside it.
  • Security vetting under the Protective Security Act (2018:585), arranged with you where an assignment requires it.

What stays with you. If you are covered by NIS2, the obligations are yours: your risk management, your incident reporting, and your assessment of suppliers. Our security organisation and risk register can be presented to you on request.

Cyber Resilience Act

Regulation (EU) 2024/2847 In force since December 2024. Reporting of actively exploited vulnerabilities (24 h / 72 h / 14 days) applies from 11 September 2026, across the installed base; full application from 11 December 2027, per unit placed on the market

What it asks. Manufacturers of hardware and software that connects to a network design it securely, assess its risks, handle vulnerabilities, publish an SBOM, declare a support period with free security updates, and report to ENISA and the national CSIRT. Radio equipment already has to meet RED Article 3(3) and EN 18031, mandatory since August 2025.

What Yggio and Sensative do

  • We are the manufacturer of our sensors, so these obligations are ours. Each product’s risk assessment documents which protections apply and why.
  • Strips LoRaWAN are secure by design rather than by update: fixed firmware, a unique key per device and no remote attack path. An attacker must be within radio range of each sensor. Under jamming they back off to one attempt a day, so a sealed battery is not drained.
  • Square and Puck firmware updates need physical presence and a check of ownership in Yggio; VSM apps are sandboxed and their changes logged.
  • Every sensor is tracked from production in our build system, and over NFC a customer can reach only its own devices.
  • How Yggio is covered depends on delivery: as a cloud service it is regulated through NIS2 rather than the CRA; installed on your premises or delivered on edge hardware it is a product under the CRA, with CE marking, declaration of conformity and technical documentation.
  • An SBOM is generated in every Yggio build, components are monitored for known vulnerabilities, and security fixes are shipped separately from functional updates.
  • Vulnerabilities can be reported to security@sensative.com, published in security.txt.

What stays with you. Usually you are the user: install security updates, name someone who reads our security advisories, and plan the lifecycle in the contract: sensors bought in 2026 will still be in the building in 2036. You become distributor, importer or manufacturer if you pass equipment on, buy directly from outside the EU, or substantially modify a product.

Data Act

Regulation (EU) 2023/2854 Applies since 12 September 2025. Design rules for connected products placed on the market from 12 September 2026; charges for switching data processing services end in January 2027

What it asks. Users get access to the data their connected products generate, and can share it. Customers of cloud and data processing services can switch provider and take their data with them.

What Yggio and Sensative do

  • You own the data in Yggio. Our EULA states that nothing in it restricts your rights under the Data Act.
  • Open-source payload decoders for Strips and for our VSM sensors are on GitHub, so any platform can read our sensors.
  • Yggio can act as your LoRaWAN join server, so your device keys need not sit with a third party.
  • One open API and the FIWARE NGSI-LD data model. Export through the standard functions, and for 30 days after an agreement ends.
  • Share datasets with other organisations on your own terms in the Data Marketplace.

What stays with you. Decide who your data is shared with, and on what terms.

AI Act

Regulation (EU) 2024/1689 In force since August 2024; prohibitions apply since February 2025, rules for general-purpose AI since August 2025, and the remaining rules are being phased in

What it asks. AI is regulated by risk: some practices are prohibited, AI systems must be disclosed as AI, and high-risk uses carry duties for providers and deployers.

What Yggio and Sensative do

  • Our AI policy rules out the practices prohibited by Article 5, and AI we operate is disclosed as AI, as Article 50 requires. A named person stays accountable for everything AI produces.
  • Customer data and personal data are never sent to an external AI service by us, and never used to train a model.
  • The Yggio AI Assistant answers from the documentation, runs on your own Anthropic or OpenAI account, and has a daily token limit you set.
  • Anomaly-detection models are trained on your own sensor history inside Yggio, and each training run records its data, settings and results.

What stays with you. You decide where AI is used. If you use it for a high-risk purpose, for example as a safety component in critical infrastructure, the deployer duties are yours. Talk to us early.

AI at Sensative

CLOUD Act

US Clarifying Lawful Overseas Use of Data Act, 2018 US law in force since 2018

What it asks. US authorities can require providers under US jurisdiction to hand over data in their possession, custody or control, even when it is stored outside the United States. FISA Section 702 adds intelligence collection, often under non-disclosure orders.

What Yggio and Sensative do

  • Sensative AB, which develops and delivers Yggio, is a Swedish company; Yggio is developed and operated entirely by our own staff in Sweden. Our US subsidiary, Sensative Inc., is a sales company for customers in the United States only; it does not host or operate Yggio.
  • For customers in the EU/EEA, the UK and Switzerland, Yggio as a service is hosted by Cleura AB, a Swedish cloud provider, in the EU/EEA.
  • Customers established outside Europe are hosted by default on Amazon Web Services in Canada, or wherever we agree.
  • For full operational independence, Yggio runs on your own servers or at the edge, with no connection to us required.

What stays with you. Choose the hosting option that matches your requirements. On your own premises, you hold all the keys.

Cloud and AI Development Act

Proposal COM(2026) 502 Proposal from the European Commission, 3 June 2026. Not yet law; the certification scheme it rests on is not yet adopted

What it asks. Sovereignty becomes a condition in public cloud procurement, through four assurance levels: level 1 as the floor for all public cloud procurement, higher levels where an activity touches public order, with level 3 requiring EU ownership, EU staff and EU jurisdiction.

What Yggio and Sensative do

  • Sensative AB is owned and controlled within the EU: a few small shareholders outside the EU hold minority stakes without controlling influence. Yggio is developed and operated entirely by Sensative’s own staff in Sweden, and for customers in the EU it runs in the EU.
  • Yggio as a service in Europe runs on Cleura, a Swedish provider, by default; other placement only at your request. Cleura describes its own sovereignty position at cleura.com.
  • On your premises or at the edge, the cloud-provider role sits entirely with you.
  • Measured against the criteria in the proposal (ownership and control, jurisdiction, and the infrastructure beneath), Yggio in Europe is structurally well placed for the higher assurance levels today. The certification scheme does not exist yet, so no provider can be certified; we will document Yggio against the levels as the implementing acts set them.

What stays with you. Public bodies will carry out a sovereignty risk assessment per use case. Until the levels exist, ask suppliers to describe their sovereignty position rather than writing level requirements into contracts that no one can yet meet.

In the United States

For customers in the United States, served by our sales company Sensative Inc. Federal and state requirements differ from the EU’s; here is where we stand.

Hosting and data location

Where Yggio runs for US customers Set in each agreement

What it asks. US customers, and public bodies in particular, often require data to stay in North America and to be operated by a provider they can assess.

What Yggio and Sensative do

  • Yggio as a service can be hosted in the United States, on Amazon Web Services or another provider, as agreed in the order.
  • Without such an agreement, customers outside Europe are hosted on Amazon Web Services in Canada.
  • Yggio also runs entirely on your own servers or at the edge.
  • Sensative Inc. is our US sales company; Yggio is developed and operated by Sensative AB’s own staff in Sweden.

What stays with you. Choose the hosting option that matches your requirements.

Radio certification

FCC Part 15 (United States) and ISED (Canada) Required before radio equipment is marketed

What it asks. Every radio device sold in the United States needs FCC equipment authorisation, and in Canada ISED certification.

What Yggio and Sensative do

  • Our sensors for North America are certified by the FCC and ISED.
  • The FCC and IC certification numbers will be listed on each product page.

What stays with you. Use the North American frequency plan (US915) and a network that supports it.

NIST IoT cybersecurity baseline

NISTIR 8259A and NIST SP 800-213 Guidance; required for IoT bought by US federal agencies under the IoT Cybersecurity Improvement Act of 2020

What it asks. Connected devices should be identifiable, securely configurable, protect their data and interfaces, take software updates and report their cybersecurity state.

What Yggio and Sensative do

  • Device identification: each LoRaWAN sensor has its own DevEUI, and each Z-Wave sensor its own DSK.
  • Data protection: LoRaWAN encrypts every message with AES-128, with keys set up at join.
  • Configuration: over the air through Yggio, or locally by NFC for Square, Square Xtreme, Puck and Prism.
  • Software update: VSM apps, almanacs and firmware over the air.
  • State awareness: SIDD in-device diagnostics, and Yggio flags a device that misses an expected report.

What stays with you. If you are a federal agency, your security controls under NIST SP 800-213 remain yours; this mapping is input to them, not a certification.

Supply chain

NDAA Section 889 and the FCC Covered List Applies to federal procurement, and increasingly to state and local buyers

What it asks. Federal agencies may not buy equipment that contains components from certain vendors, listed in Section 889 of the 2019 National Defense Authorization Act and on the FCC Covered List.

What Yggio and Sensative do

  • Our sensors are developed in Sweden and manufactured in the EU, by our production partner JME in Poland.
  • We can attest that our sensors contain no components from vendors restricted under Section 889 or on the FCC Covered List.
  • The attestation is provided with a quotation or on request.

What stays with you. Request the attestation as part of your procurement.