--- title: "Avalanches and mountain roads monitoring | Nexus Observatory" description: "An avalanche above a road gives seconds once it runs and days of warning in the snowpack before. Snow and weather stations…" url: https://observatory.global/industries/public-safety/avalanches/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Public safety](https://observatory.global/industries/public-safety/) / [Specialized fields](https://observatory.global/industries/public-safety/fields/) / **Avalanches and mountain roads** # Avalanches, detected before the road is reached. An avalanche above a road gives seconds once it runs and days of warning in the snowpack before. Snow and weather stations, avalanche radar and cameras report to one record the avalanche service and the road authority act on, closing roads in time and opening them on evidence. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Public safety **Measurements**: 5 **Sources cited**: 4 1. Public safety · Avalanches and mountain roads Seconds on the path, days in the snow Once an avalanche runs it reaches the road in seconds; the warning lives in the snowpack days before. Snow and weather on the slopes let the avalanche service rate the danger, and detection on each path closes the road the moment the snow comes down. 2. What is measured Snow, weather, detection and images Stations on representative slopes measure snow depth, new snow, wind and temperature. Radar or infrasound sensors cover known paths and detect avalanches within seconds, and cameras on the paths show what released and whether the road is clear. Every reading names its path and slope. InstrumentsSnow stations · Avalanche radar · Infrasound · Path cameras 3. The base node A node that closes the road The path node detects an avalanche from radar or infrasound, triggers road signals or barriers where agreed, captures images of the path and sends the event at once, signing everything for the record. Detections are kept even when the link is down and sent when it returns. 4. Radio and links Over the ridge, or up to the satellite Path sites link over a ridge relay to the road control room by microwave, independent of public networks. Remote paths and snow stations send events and data by satellite, and valley sites use cellular as a second path. Each path is supervised from the control room. LinksMicrowave · Satellite · Public cellular 5. How it works From a release to a red signal A slab releases above the road. The radar detects it, the node triggers the red signal through road control within seconds and sends the event with images over the ridge relay. Crews see the path, confirm the road is clear and reopen it on evidence. 6. From order to operation · Order Scope the paths and the closures The scope reads the avalanche cadastre, the paths that reach the road, the closure and control procedures and the warning service's network. Nexus Observatory Inc. returns the detection plan by path, the radio design, the integration with road control and a price per path and per service. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey in summer Crews survey in summer with the avalanche expert: radar sites that see each path, snow station sites on representative slopes, ridge relays and road sections. They check microwave paths and sky view, and plan helicopter or foot access for winter. 8. From order to operation · Permits Land, slopes and road control Landowners and protected area managers consent to sites. Automatic closures are agreed in writing with the road authority, which keeps the decision rules. Every consent is kept with the site. Detection data is shared with the avalanche warning service by agreement, and the warning service keeps its own role in setting danger levels. 9. From order to operation · Build Build for the snow Radars, cameras, snow stations, nodes and radios are built for cold, ice and snow load, tested together and enrolled with their identities. Detection zones and closure triggers come from the avalanche expert and the road authority. Configurations are tested on the bench before transport. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install before the first snow Crews install in summer and autumn: radars and cameras on masts above the deepest snow, snow stations on representative slopes, relays on ridges. Every site is surveyed and photographed for the record before the first snow. Cables and masts are protected from snow creep and falling ice. 11. From order to operation · Commission Test with a controlled release Each node proves its identity. Snow stations are checked against manual measurements, detection is tested with the first controlled release of the season where allowed, and closure triggers are tested with the road control room. Each path goes live only when all checks pass. 12. From order to operation · Operate Close and open on evidence The avalanche service sees snow and weather on the slopes and sets danger levels. When a path releases, the road closes in seconds and crews see the images. Roads reopen when the paths are confirmed, and every event is kept on the record. 13. From order to operation · Maintain Service in summer, repair in winter Sites are serviced each summer: masts checked, sensors calibrated, batteries replaced. Winter faults are repaired when safe access allows. Every change is recorded, so the event record stays complete for the avalanche cadastre. Spares are stored in the valley so a failed part is swapped on the first safe day. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For road control, forecasters and the public Road and rail control rooms receive events with images; avalanche warning services receive snow and weather from the slopes; the public and operators receive danger levels; avalanche experts and planners receive event records for the cadastre. Each product carries its source and time. [See the data products](https://observatory.global/data-products/) 15. Evidence Every release on record Every event, closure, reopening and snow reading is signed and kept. Snow and weather follow WMO practice, danger follows the European avalanche standards, warnings follow the early warning checklist and travel in the Common Alerting Protocol, so every closure can be justified. Drawn againstEuropean Avalanche Warning Services standards · WMO-No. 8 · WMO early warning checklist 16. What you get Transport and logistics corridor sensing Road weather, rail condition, port and cold-chain sensing along corridors, with connectivity where coverage ends. Delivered as managed service and data licence, for transport agencies, rail and port operators, logistics firms. Scale: Corridor to network. Service levels are written as numbers you can measure on your own dashboard. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan avalanches and mountain roads with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for avalanches and mountain roads. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace. [Plan a deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) **01** The place and its hazards ## Where it runs, and what can go wrong. Operating contextAvalanche warning services publish danger levels from snowpack and weather, and road, rail and resort operators close routes, control slopes and open them again. Detection systems on known paths tell operators when an avalanche has run, so roads close automatically and crews know whether a path has released. Hazards - Avalanches reaching roads, railways and buildings - Closures that come too late or last too long - Crews exposed during control work - Stations buried, iced or destroyed - Remote paths beyond any network **02** What must be measured ## What, where, how often, and under which rules. Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below. | Measurement | Where | Cadence | Sources | | --- | --- | --- | --- | | Snow depth and new snow | Stations on representative slopes | Continuous | 12 | | Wind, temperature and humidity | Ridge and slope stations | Continuous | 12 | | Avalanche detection | Radar or infrasound covering known paths | Continuous, events in seconds | 2 | | Path images | Cameras on paths and road sections | On schedule and on event | 2 | | Danger level | Each warning region | Daily and on change | 23 | **03** The observation stack ## From one base unit to a network. The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol. 1. **01** Base unit A path point: a detection radar and a camera with a snow station, read by an edge node that signs every event. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A road section: points on each path, a relay on a ridge and a link to the road control room. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every path of a region run as one fleet, with one record. [Managed offers →](https://observatory.global/industries/public-safety/solutions/) 4. **04** Network Avalanche services, road and rail authorities and resorts exchange snow data, events and danger through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** Surveillance radar (FMCW) - **02** Compact weather station - **03** Seismometer / strong-motion accelerometer - **04** PTZ camera - **05** Edge node (Wedge) - **06** Point-to-point microwave - **07** LEO flat-panel terminal - **08** Solar array - **09** Lattice tower Radio and links ### Point-to-point microwave Path sites link over a ridge relay to the road control room, independent of public networks. Radio and links ### Satellite Remote paths and snow stations beyond microwave reach send events and data by satellite. Radio and links ### Public cellular Valley sites with coverage use cellular as a second path. Edge computeThe path node detects an avalanche from radar or infrasound in seconds, triggers road signals or barriers where agreed, captures images of the path and sends the event at once. PowerSites run on solar with batteries sized for short winter days and snow-covered panels, mounted above the deepest recorded snow. **04** How it works ## From the instrument to the product. One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks. Avalanches and mountain roads: data path – of 06 01 Instruments Measurement with sensor identity andcalibration 02 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 03 Backhaul Commit with transactional outbox andpublish, delivered at least once 04 Site Consumer inbox deduplicates and applieseach record once into governed data 05 Data store Governed product through API, map orexport, correction-aware 06 Products Common Alerting ProtocolOGC SensorThings APIWMO WIS 2.0 07 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment 01 Surveillance radar (FMCW) Ethernet 02 Compact weather station SDI-12 · RS-485 · Ethernet 03 Seismometer / strong-motionaccelerometer SDI-12 · RS-485 · Ethernet 04 PTZ camera Ethernet 05 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 06 Point-to-point microwave Ethernet · Fibre 07 LEO flat-panel terminal Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Avalanche events with images Snow and weather on the slopes Danger levels Event records for the cadastre 08 Solar array RS-485 09 Lattice tower Ethernet RS-485 Ethernet Ethernet Ethernet Ethernet Microwave link Satellite IP From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation. | Item | Equipment | Data ports | Protocols | Power in | | --- | --- | --- | --- | --- | | 01 | **Surveillance radar (FMCW)** Short-range FMCW radar for perimeter, traffic, drone and water-surface detection. | Ethernet | MQTT 5, OGC SensorThings API | 12 V DC | | 02 | **Compact weather station** All-in-one or compact station for temperature, humidity, pressure, wind and rain at a site. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 03 | **Seismometer / strong-motion accelerometer** Short-period seismometer or strong-motion accelerometer for local earthquake and structural shaking. | SDI-12RS-485Ethernet | SEED / miniSEED streams, MQTT 5, OGC SensorThings API | 12 V DC | | 04 | **PTZ camera** Pan-tilt-zoom camera for wide-area visual monitoring (wildfire, flood, traffic). | Ethernet | RTSP with ONVIF profiles | PoE, 24 V DC | | 05 | **Edge node (Wedge)** Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains | | 06 | **Point-to-point microwave** Licensed or licence-exempt point-to-point radio link between two sites with line-of-sight. | EthernetFibre | IEEE 1588 PTP | PoE, 48 V DC | | 07 | **LEO flat-panel terminal** Electronically steered flat-panel user terminal for low-Earth-orbit broadband constellations. | Ethernet | — | PoE, 48 V DC, AC mains | | 08 | **Solar array** PV modules with charge controller sized to the site's load and climate. | RS-485 | Modbus | — | | 09 | **Lattice tower** Self-supporting or guyed lattice tower for macro radios, links and instruments. | — | — | — | How it scales 01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces. SITE Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality. CLUSTER ×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites. FLEET Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts. TRUST DOMAIN TRUST DOMAIN TRUST DOMAIN ×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding. **Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. **Telemetry**: OpenTelemetry OTLP. **Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. **Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. **Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. **Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. **Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. **05** From order to operation ## Every step, from the first call to a running site. The same crew and the same record carry the work from scope to maintenance. 1. 01 Order Scope the paths and the closures The scope reads the avalanche cadastre, the paths that reach the road, the closure and control procedures and the warning service's network. Nexus Observatory Inc. returns the detection plan by path, the radio design, the integration with road control and a price per path and per service. 2 2. 02 Survey Survey in summer Crews survey in summer with the avalanche expert: radar sites that see each path, snow station sites on representative slopes, ridge relays and road sections. They check microwave paths and sky view, and plan helicopter or foot access for winter. 3. 03 Permits Land, slopes and road control Landowners and protected area managers consent to sites. Automatic closures are agreed in writing with the road authority, which keeps the decision rules. Every consent is kept with the site. Detection data is shared with the avalanche warning service by agreement, and the warning service keeps its own role in setting danger levels. 4. 04 Build Build for the snow Radars, cameras, snow stations, nodes and radios are built for cold, ice and snow load, tested together and enrolled with their identities. Detection zones and closure triggers come from the avalanche expert and the road authority. Configurations are tested on the bench before transport. 5. 05 Install Install before the first snow Crews install in summer and autumn: radars and cameras on masts above the deepest snow, snow stations on representative slopes, relays on ridges. Every site is surveyed and photographed for the record before the first snow. Cables and masts are protected from snow creep and falling ice. 6. 06 Commission Test with a controlled release Each node proves its identity. Snow stations are checked against manual measurements, detection is tested with the first controlled release of the season where allowed, and closure triggers are tested with the road control room. Each path goes live only when all checks pass. 7. 07 Operate Close and open on evidence The avalanche service sees snow and weather on the slopes and sets danger levels. When a path releases, the road closes in seconds and crews see the images. Roads reopen when the paths are confirmed, and every event is kept on the record. 24 8. 08 Maintain Service in summer, repair in winter Sites are serviced each summer: masts checked, sensors calibrated, batteries replaced. Winter faults are repaired when safe access allows. Every change is recorded, so the event record stays complete for the avalanche cadastre. Spares are stored in the valley so a failed part is swapped on the first safe day. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Avalanche events with images** Road and rail control rooms - **Snow and weather on the slopes** Avalanche warning services - **Danger levels** The public and operators - **Event records for the cadastre** Avalanche experts and planners Integration - **Road control** Events trigger signals or barriers through the road control system, under its rules. - **Avalanche warning service** Snow and weather data are delivered through OGC SensorThings. - **Public warnings** Danger levels are published by the service in its own formats and the Common Alerting Protocol. Exchanged through Common Alerting Protocol, OGC SensorThings API, WMO WIS 2.0. **07** Questions buyers ask ## Before you scope it. Does it close the road automatically? Where the road authority agrees, through its control system and rules. Who sets the danger level? The avalanche warning service. Will stations be buried? They are mounted above the deepest recorded snow. Can control work be monitored? Yes. Controlled releases are detected and recorded like natural ones. **08** Resources ## The sources behind this page. Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does. 1. **1** [Guide to Instruments and Methods of Observation (WMO-No. 8)](https://library.wmo.int/) World Meteorological Organization 2. **2** [European Avalanche Danger Scale and standards](https://www.avalanches.org/) European Avalanche Warning Services 3. **3** [Multi-hazard Early Warning Systems: A Checklist](https://library.wmo.int/) World Meteorological Organization · 2018 4. **4** [Common Alerting Protocol Version 1.2](https://www.oasis-open.org/) OASIS **09** Related ## Use cases and solutions. [Use case Avalanche detection siteDoppler radar, infrasound and geophones with a snow and wind station, feeding a road or resort control room.The full use case →](https://observatory.global/use-cases/avalanche-detection/) [Solution Transport and logistics corridor sensingRoad weather, rail condition, port and cold-chain sensing along corridors, with connectivity where coverage ends.Solutions for public safety →](https://observatory.global/industries/public-safety/solutions/#corridor-sensing) [Solution Structural and ground-movement monitoringGNSS, InSAR, tilt, strain and fibre sensing on bridges, dams, slopes, tailings and pipelines, with alert thresholds set by the owner.Solutions for public safety →](https://observatory.global/industries/public-safety/solutions/#infrastructure-monitoring) **10** Public safety: specialized fields ## Other fields of this industry. [Specialized field Wildfire detection and responseSmoke detection from towers, fire weather and danger, thermal confirmation and satellite hotspots, on microwave and satellite to the fire agency's dispatch, so a start is seen in minutes.The full field →](https://observatory.global/industries/public-safety/wildfire/) [Specialized field Flash and urban floodsRain and water depth in streets, culverts and small streams, with cameras at known flood points, on LoRaWAN and cellular, so warnings reach people in the minutes a flash flood allows.The full field →](https://observatory.global/industries/public-safety/flash-floods/) [Specialized field Landslides and debris flowsGround movement by GNSS, pore pressure and rainfall thresholds, ground vibration for debris flows, on LoRaWAN and satellite from unstable slopes to the agency that warns and closes roads.The full field →](https://observatory.global/industries/public-safety/landslides/) [Specialized field Earthquakes and early warningStrong-motion and broadband seismometers, GNSS for large events, structural response in key buildings, on fibre and cellular with timing that lets a warning outrun the shaking.The full field →](https://observatory.global/industries/public-safety/earthquakes/) [Specialized field Incident response and deployable networksA network that arrives with the crews: cell on wheels, satellite, mesh, drones, gas and thermal sensing at the scene, so incident command sees and talks when local networks are down.The full field →](https://observatory.global/industries/public-safety/incident-response/) ### Bring us the site. Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details. [Plan a deployment](https://observatory.global/contact/deployment/) [Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) [Request a quote](https://observatory.global/contact/hardware-quote/) [Nexus Observatory](https://observatory.global/)**Public safety** . Warning time, gained at the sensor.[Talk to us](https://observatory.global/contact/) Public safety - [Overview](https://observatory.global/industries/public-safety/) - [Explainer](https://observatory.global/industries/public-safety/explainer/) - [Specialized fields](https://observatory.global/industries/public-safety/fields/) - [Use cases](https://observatory.global/industries/public-safety/use-cases/) - [Solutions](https://observatory.global/industries/public-safety/solutions/) - [Platforms](https://observatory.global/industries/public-safety/platforms/) - [Resources](https://observatory.global/industries/public-safety/resources/) - [Contact](https://observatory.global/industries/public-safety/contact/) Platforms - [Observatory Protocol](https://observatory.global/protocol/) - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Open governance](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/)