--- title: "Community cellular and broadband | Nexus Observatory" description: "Many rural and Indigenous communities sit beyond commercial coverage. A community can own its own cellular and Wi-Fi network: a small site on a mast…" url: https://observatory.global/industries/communities/community-networks/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Communities](https://observatory.global/industries/communities/) / [Specialized fields](https://observatory.global/industries/communities/fields/) / **Community cellular and broadband** # A network the community owns, where carriers do not build. Many rural and Indigenous communities sit beyond commercial coverage. A community can own its own cellular and Wi-Fi network: a small site on a mast, shared spectrum, solar power and backhaul by microwave or satellite. Local people run it, set its rules and decide what happens to its data. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Communities **Measurements**: 5 **Sources cited**: 7 1. Communities · Community cellular and broadband Beyond the carriers' maps Many rural and Indigenous communities sit beyond commercial coverage, so emergencies, health care, school and business all wait. Spectrum rules in several countries now let communities run their own cellular networks. A small site, shared spectrum, solar power and long-reach backhaul can bring coverage the community owns. 2. What is measured Coverage, health and power The network measures itself: signal and quality across the community, availability and traffic at the site and core, backhaul health, and the solar and battery system that powers it. Walk tests at commissioning and radio exposure checks around the site complete the picture. MeasuredCoverage · Quality · Availability · Traffic · Power · Radio exposure 3. The base node Local calls stay local The node runs a compact core at the site, so calls and messages within the community never cross the backhaul. It caches content and updates, shapes traffic fairly, watches power, radio and backhaul, and keeps the community's records where the community decided they live. 4. Radio and links Out through microwave or satellite A small cell gives phones coverage across the community and Wi-Fi carries heavy use at the school, clinic and hall. Microwave reaches the nearest fibre where a line of sight exists; satellite reaches communities beyond it, with caching to save capacity. LinksPrivate LTE · Wi-Fi · Microwave · Satellite 5. How it works From a call to the clinic A parent calls the clinic across the village; the call stays on the local core. The nurse then sends a video consultation request to the regional hospital; it leaves over the backhaul with priority. That night the battery state reaches the local operator, who adjusts the evening load. 6. From order to operation · Order Scope with the community The scope starts with the community: who will own and run the network, what it must serve first, how it will be paid for and who holds its data. Nexus Observatory Inc. returns the site design, spectrum route, backhaul, power, training and a price for building and for each year. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey with local guides Crews survey with local guides: mast positions with the best view of homes, the school and the clinic, the path to the nearest fibre or a clear sky for satellite, ground for the mast and solar array, and where people gather. Findings are recorded with photographs. 8. From order to operation · Permits Spectrum, land and consent The spectrum licence is applied for under the regulator's local or shared access rules, the mast is approved on community land, and the community's agreement sets ownership, data governance and how decisions are made. Every licence and agreement is kept with the site record. 9. From order to operation · Build Build and train together Small cells, access points, the core, node, backhaul and power are configured and tested together, enrolled with their identities and labelled. Local operators join the bench work, learning how each part is set up, tested and replaced. Test results travel with the kit to the site. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Raise the mast Crews and local operators raise the mast, mount the small cell, access points and backhaul antenna, install solar panels, batteries and the shelter, and connect everything. Every part is photographed and the site record is updated before the crew leaves. 11. From order to operation · Commission Commission and measure coverage Each node proves its identity. Walk and drive tests measure coverage and quality across the community, radio exposure is checked in public places around the site, and calls, messages and data are tested through to the backhaul. Local operators run the tests themselves. 12. From order to operation · Operate Run it locally Local operators see the network: coverage, traffic, availability, power and backhaul. They add subscribers, set tariffs and rules the community agreed, and reach remote support when they need it. Records stay where the community decided. Reports for owners and funders come from the same record. 13. From order to operation · Maintain Repair locally, update remotely Local operators replace swappable parts from spares kept on site, software updates arrive remotely in rings, batteries are tested each season, and the licence record is kept current. Training refreshers keep skills in the community. Spares and procedures travel with the crews. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For residents and operators Residents, the school, the clinic and emergency services receive phone and data coverage; local operators receive network health and power; the community and the regulator receive coverage and quality records; the governing body receives usage and finance reports, each kept under the community's own rules. [See the data products](https://observatory.global/data-products/) 15. Evidence Owned, licensed and safe Coverage and quality are measured with the definitions carriers use, availability follows the international quality of service terms, radio exposure is checked against international guidelines, spectrum is used under the regulator's licence, and data governance follows Indigenous data principles. Every record stays with the community. Drawn against3GPP TS 38.215 · ITU-T E.800 · ICNIRP Guidelines · 47 CFR Part 96 · CARE Principles for Indigenous Data Governance 16. What you get Municipal sensing and connectivity layers City-wide LPWAN or private 5G as a shared layer for public sensors and services. Delivered as managed service, for cities, regional governments. Scale: City-wide. Service levels are written as numbers you can measure on your own dashboard. Changes are versioned, tested and reversible. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan community cellular and broadband 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 community cellular and broadband. 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 contextRegulators in several countries now license spectrum for local and shared use, so communities and small operators can run their own cellular networks. Coverage and quality can be measured to the same definitions carriers use, radio exposure near antennas is assessed against international guidelines, and Indigenous data governance principles set who holds the data a network produces. Hazards - No coverage for emergencies, health and school - Satellite backhaul that is costly and easily congested - Diesel or unreliable grid power at the site - Equipment no one locally can repair - Data held far away under rules the community did not set **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 | | --- | --- | --- | --- | | Coverage and signal quality | Across the community, from drive and walk tests and from the network itself | At commissioning, then continuously | 1 | | Availability and traffic | At the cell site and core | Continuous | 2 | | Radio exposure near antennas | Publicly accessible places around the site | At commissioning and after changes | 3 | | Site power and battery state | The site's solar and battery system | Continuous | 4 | | Licence conditions | Channels, power and location registered for the site | On every change | 56 | **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 community site: a small cell and Wi-Fi access points on a mast, a compact core and a node. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A site: the mast, solar power and batteries, a shelter and microwave or satellite backhaul. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Several community sites run together, sharing one core and one operations view while each community keeps its own rules. [Managed offers →](https://observatory.global/industries/communities/solutions/) 4. **04** Network Community networks interconnect with carriers and with each other, and share coverage and quality records through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** Small cell (4G/5G) - **02** Wi-Fi access point - **03** 5G core appliance (UPF/core) - **04** Edge node (Wedge) - **05** Point-to-point microwave - **06** LEO flat-panel terminal - **07** Solar array - **08** Lattice tower Radio and links ### Private LTE A small cell on licensed shared or community spectrum gives phones coverage across the community. Radio and links ### Wi-Fi Wi-Fi at the school, clinic and community hall carries heavy use cheaply. Radio and links ### Point-to-point microwave Microwave to the nearest fibre point is the best backhaul where a line of sight exists. Radio and links ### Satellite Satellite backhaul reaches communities beyond any line of sight, with caching to save capacity. Edge computeThe node runs the compact core locally so calls and messages within the community never leave it, caches content and updates to save backhaul, shapes traffic fairly and watches power, radio and backhaul health. PowerSolar panels and batteries sized for the cloudiest weeks power the site, with the battery state reported so local operators can act before the network goes down. **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. Community cellular and broadband: data path – of 08 01 Instruments Measurement with sensor identity andcalibration 02 Radio access 03 Core network 04 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products 3GPPTR-069OGC SensorThings API 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment Subscriber phones and modems Not in the reference kit Wi-Fi client devices Not in the reference kit 01 Small cell (4G/5G) Ethernet · Fibre · GNSS antenna ·1PPS/10 MHz 02 Wi-Fi access point Ethernet 03 5G core appliance (UPF/core) Ethernet · Fibre · BMC 04 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 05 Point-to-point microwave Ethernet · Fibre 06 LEO flat-panel terminal Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Phone and data coverage Network health and power Coverage and quality records Usage and finance reports 07 Solar array RS-485 08 Lattice tower LTE/NR Wi-Fi Ethernet 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 | **Small cell (4G/5G)** Integrated base station (radio, baseband, antenna) for private LTE or NR on a local licence, shared-spectrum or leased route. A CBRS CBSD is a small cell that also registers with a spectrum access system. | EthernetFibreGNSS antenna1PPS/10 MHz | 3GPP NR air interface, 3GPP E-UTRA air interface, IEEE 1588 PTP, O-RAN E2, A1, O1 | PoE, 48 V DC, AC mains | | 02 | **Wi-Fi access point** Outdoor or indoor Wi-Fi access point, optionally with Passpoint for roaming. | Ethernet | IEEE 802.11 | PoE | | 03 | **5G core appliance (UPF/core)** Local 5G standalone core with user-plane function and local breakout, so site traffic stays on site. | EthernetFibreBMC | 3GPP 5G core service-based interfaces, DMTF Redfish | AC mains, 48 V DC | | 04 | **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 | | 05 | **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 | | 06 | **LEO flat-panel terminal** Electronically steered flat-panel user terminal for low-Earth-orbit broadband constellations. | Ethernet | — | PoE, 48 V DC, AC mains | | 07 | **Solar array** PV modules with charge controller sized to the site's load and climate. | RS-485 | Modbus | — | | 08 | **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 with the community The scope starts with the community: who will own and run the network, what it must serve first, how it will be paid for and who holds its data. Nexus Observatory Inc. returns the site design, spectrum route, backhaul, power, training and a price for building and for each year. 7 2. 02 Survey Survey with local guides Crews survey with local guides: mast positions with the best view of homes, the school and the clinic, the path to the nearest fibre or a clear sky for satellite, ground for the mast and solar array, and where people gather. Findings are recorded with photographs. 1 3. 03 Permits Spectrum, land and consent The spectrum licence is applied for under the regulator's local or shared access rules, the mast is approved on community land, and the community's agreement sets ownership, data governance and how decisions are made. Every licence and agreement is kept with the site record. 56 4. 04 Build Build and train together Small cells, access points, the core, node, backhaul and power are configured and tested together, enrolled with their identities and labelled. Local operators join the bench work, learning how each part is set up, tested and replaced. Test results travel with the kit to the site. 5. 05 Install Raise the mast Crews and local operators raise the mast, mount the small cell, access points and backhaul antenna, install solar panels, batteries and the shelter, and connect everything. Every part is photographed and the site record is updated before the crew leaves. 6. 06 Commission Commission and measure coverage Each node proves its identity. Walk and drive tests measure coverage and quality across the community, radio exposure is checked in public places around the site, and calls, messages and data are tested through to the backhaul. Local operators run the tests themselves. 31 7. 07 Operate Run it locally Local operators see the network: coverage, traffic, availability, power and backhaul. They add subscribers, set tariffs and rules the community agreed, and reach remote support when they need it. Records stay where the community decided. Reports for owners and funders come from the same record. 27 8. 08 Maintain Repair locally, update remotely Local operators replace swappable parts from spares kept on site, software updates arrive remotely in rings, batteries are tested each season, and the licence record is kept current. Training refreshers keep skills in the community. Spares and procedures travel with the crews. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Phone and data coverage** Residents, the school, the clinic and emergency services - **Network health and power** Local operators - **Coverage and quality records** The community and the regulator - **Usage and finance reports** The community's governing body Integration - **Carriers** Calls and roaming interconnect with carriers where agreements exist. - **Emergency calls** Emergency calls are routed to the public answering point through the backhaul. - **Community systems** Subscriber, tariff and finance records stay in systems the community controls. Exchanged through 3GPP, TR-069, OGC SensorThings API. **07** Questions buyers ask ## Before you scope it. Can we own the network? Yes. The design assumes community ownership and local operators. Do we need a licence? Usually, under the regulator's local or shared spectrum rules; the scope sets the route. What if backhaul is slow? Local calls stay local, and caching saves capacity for what must leave. Who holds our data? The community decides, following its data governance agreement. **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** [3GPP TS 38.215: NR physical layer measurements](https://www.3gpp.org/) 3rd Generation Partnership Project 2. **2** [ITU-T E.800: Definitions of terms related to quality of service](https://www.itu.int/) International Telecommunication Union 3. **3** [ICNIRP Guidelines for limiting exposure to electromagnetic fields (100 kHz to 300 GHz)](https://www.icnirp.org/) International Commission on Non-Ionizing Radiation Protection · 2020 4. **4** [IEC TS 62257: Renewable energy and hybrid systems for rural electrification](https://webstore.iec.ch/) International Electrotechnical Commission 5. **5** [47 CFR Part 96: Citizens Broadband Radio Service](https://www.ecfr.gov/) United States Federal Communications Commission 6. **6** [Shared Access Licence: guidance document](https://www.ofcom.org.uk/) Ofcom 7. **7** [CARE Principles for Indigenous Data Governance](https://www.gida-global.org/) Global Indigenous Data Alliance · 2019 **09** Related ## Use cases and solutions. [Use case Community cellular and sensingSmall cells with an open core, satellite backhaul and solar power, plus a sensing overlay, for a community that owns its network.The full use case →](https://observatory.global/use-cases/community-cellular/) [Solution Municipal sensing and connectivity layersCity-wide LPWAN or private 5G as a shared layer for public sensors and services.Solutions for communities →](https://observatory.global/industries/communities/solutions/#municipal-connectivity) [Solution Private Wireless as a ServiceStandalone private 5G or LTE for a site, campus, port or mine: radios, core, SIMs, spectrum route and operations.Solutions for communities →](https://observatory.global/industries/communities/solutions/#private-wireless) [Solution Operator and technician training on delivered systemsHands-on courses for customer staff on the systems they run; no public credentials are issued by the group.Solutions for communities →](https://observatory.global/industries/communities/solutions/#operator-training) **10** Communities: specialized fields ## Other fields of this industry. [Specialized field Community microgridsSolar, battery and backup generation for remote communities, monitored and run locally, with energy access measured to the international framework.The full field →](https://observatory.global/industries/communities/community-microgrids/) [Specialized field Small community water systemsWater quality, chlorine, tank levels and pumps in small community supplies, watched continuously so operators keep water safe and fix faults before taps run dry.The full field →](https://observatory.global/industries/communities/small-water-systems/) [Specialized field Community early warningRain and river gauges, local alerts and sirens that a community runs itself, linked to the national warning service so warnings reach every household in time.The full field →](https://observatory.global/industries/communities/local-early-warning/) ### 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/)**Communities** . Connectivity and observation the community owns.[Talk to us](https://observatory.global/contact/) Communities - [Overview](https://observatory.global/industries/communities/) - [Explainer](https://observatory.global/industries/communities/explainer/) - [Specialized fields](https://observatory.global/industries/communities/fields/) - [Use cases](https://observatory.global/industries/communities/use-cases/) - [Solutions](https://observatory.global/industries/communities/solutions/) - [Platforms](https://observatory.global/industries/communities/platforms/) - [Resources](https://observatory.global/industries/communities/resources/) - [Contact](https://observatory.global/industries/communities/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/)