TelBrix Telco Service Terms
Version 0.1 — Effective 21 August 2026
1. About these Telco Terms
These TelBrix Telco Service Terms (Telco Terms) apply when a person or
organisation accesses telco.urbbit.com or uses TelBrix and related
telecommunications modules and services (TelBrix Services).
The TelBrix Services are provided by Urbbit Pty Ltd, ABN 91 615 735 450, of 3 Turin Place, Keilor Lodge, Victoria 3038, Australia (Urbbit).
These Telco Terms supplement the Urbbit Website and Platform Terms at
https://urbbit.com/legal/terms (Urbbit Terms). The Urbbit Terms are
incorporated into these Telco Terms.
If documents conflict, the following order applies:
- a signed Master Enterprise Agreement or Order;
- an applicable DPA, Security Schedule or SLA for its subject matter;
- these Telco Terms; and
- the Urbbit Terms.
Capitalised terms not defined here have the meaning given in the Urbbit Terms.
2. What TelBrix provides
Depending on the purchased modules and configuration, TelBrix may support:
- telecommunications resource roles, specifications, models, properties and catalogues;
- logical and physical network planning and design;
- drag-and-drop design canvases and graph-based connectivity;
- map-based network and civil-infrastructure visualisation;
- sites, service areas and geographic hierarchies;
- physical network inventory and lifecycle records;
- cabinets, racks, equipment, ports, cables, fibres, joints, splitters, splices and connectivity;
- ducts, access structures, routes and other civil infrastructure;
- manufacturer models, stock-keeping units and material planning;
- design-to-inventory transformation;
- orders, work, tasks, orchestration, dependencies and audit history;
- APIs and integrations with Customer and third-party systems; and
- reporting, collaboration and operational documentation.
The exact functions, environments, capacity, support and deployment model are stated in the applicable Order.
3. Nature of the TelBrix Services
3.1 Decision support and system of record
Unless a signed Order expressly states otherwise, TelBrix is a planning, design, inventory, orchestration and record-management platform. It assists qualified people and Customer-controlled systems but does not replace their judgement, approvals or responsibilities.
TelBrix is not:
- a licensed engineering, surveying, architectural, construction or safety service;
- a utility-locating or underground-service detection service;
- a certification that a network or civil design is compliant, safe, constructible or fit for a particular location;
- a telecommunications carrier, carriage service provider, network operator or emergency service;
- a substitute for field inspection, site survey, professional review, regulatory approval or as-built verification; or
- by default, a real-time network management, supervisory control, safety-instrumented or emergency-response system.
3.2 Customer remains the operator
Customer controls its telecommunications business, network, designs, inventory, workforce, contractors, systems, approvals and regulatory decisions. Providing TelBrix does not transfer Customer's operator, designer, constructor, asset owner, employer or regulated-entity obligations to Urbbit.
4. Resource catalogue
TelBrix may use catalogues containing resource roles, specifications, models, properties, templates, compatibility rules and manufacturer information.
Customer must ensure that:
- selected catalogue information is suitable for its architecture, geography, technology, supplier and intended use;
- measurements, capacities, port structures, containment rules and compatibility constraints are verified;
- manufacturer and supplier data is current; and
- catalogue changes follow Customer's governance and approval process.
Catalog-driven validation improves consistency but cannot identify every engineering, construction, environmental, commercial or regulatory constraint. A successful validation means only that the data satisfied the configured rules at that time.
Urbbit-owned reference roles and shared catalogues remain Urbbit intellectual property. Customer owns Customer-created catalogue data, subject to any third-party rights in manufacturer or supplier material.
5. Network design canvas and graph
5.1 Design interaction
The design canvas may allow authorised users to place, move, group and connect network elements using the applicable catalogue and design rules.
Visual position on the canvas is generally a presentation aid. It does not by itself establish geographic position, physical distance, route length, legal boundary, construction sequence or field placement.
5.2 Connectivity and integrity
TelBrix may represent elements and connections as a graph and apply configured rules to preserve identities, endpoints, containment, compatibility, cardinality and lifecycle relationships.
Customer acknowledges that graph integrity depends on:
- accurate Customer Data and catalogue definitions;
- correct user selection of elements, ports, cables and connection types;
- complete integrations and migration mappings;
- current validation rules; and
- authorised handling of conflicts, exceptions and manual overrides.
Customer must investigate validation warnings and must not bypass or override a control without appropriate authority and a documented reason.
5.3 Concurrent editing and versions
Where revision, locking, order-controlled editing or conflict detection is available, Customer must configure and use it appropriately. Customer is responsible for deciding which design or revision is approved for build, inventory creation or operation.
6. Maps and geospatial information
Maps, imagery, geocoding, routing, boundaries, coordinates and location information may come from Customer, public data or third-party providers.
They may be approximate, incomplete, delayed, differently projected or subject to third-party usage restrictions. Screen placement, route rendering and geocoded results must not be used as the sole source for:
- excavation or construction;
- cadastral or property boundaries;
- underground-service location;
- emergency response;
- safety exclusion zones;
- legal access rights; or
- final engineering measurements.
Customer must obtain required surveys, permits, utility searches and field verification. Customer is responsible for the lawful use and licensing of geospatial data it supplies.
7. Physical network inventory
TelBrix may create or manage planned, installed and operational inventory, including containment, equipment, ports, cables, fibres, joints, splices, connectivity and lifecycle records.
Customer must:
- reconcile planned records with delivered material and field work;
- verify serial numbers, locations, capacities, connections and as-built conditions;
- control who may change operational records;
- preserve records required for safety, regulation, warranty and maintenance; and
- resolve discrepancies before relying on inventory for operational decisions.
A record marked valid, complete, installed or operational reflects data and workflow state in TelBrix. It is not an independent physical inspection or certification by Urbbit.
8. Equipment assembly, ports and connectivity
Rack elevations, equipment placement, port views, power budgets, patching, fibre schedules and splice records are planning and record-management aids.
Customer must independently verify:
- rack dimensions, mounting, clearance, weight and environmental requirements;
- electrical supply, earthing, load and heat;
- optical and electrical budgets;
- port type, polarity, connector and media compatibility;
- fibre allocation, splice method and continuity;
- vendor instructions and warranties; and
- site and workplace safety requirements.
Only appropriately qualified and authorised personnel may approve or perform installation, energisation, splicing, testing or activation.
9. Civil infrastructure
TelBrix may model ducts, sub-ducts, conduits, access structures, pits, manholes, routes, occupancy and relationships between network and civil assets.
Customer is responsible for:
- landowner and authority permissions;
- utility-location searches and conflict checks;
- survey, soil, structural, drainage and environmental assessment;
- heritage, planning, road-opening and construction approvals;
- capacity, separation, bend-radius and pulling calculations;
- traffic, confined-space, excavation and workplace safety controls; and
- recording verified as-built position and condition.
TelBrix does not warrant that a displayed route is available, legally accessible, unobstructed or safe to construct.
10. Orders, workflow and orchestration
TelBrix may create or execute orders, tasks, dependencies, timers, notifications, inventory changes and integrations based on configured catalogues, workflows and rules.
Customer represents that it has authority for every command, order and change submitted through its accounts or integrations. Customer must:
- configure role-based access and segregation of duties;
- use approval gates proportionate to impact;
- test workflows and integrations before production use;
- maintain rollback, compensation and incident procedures;
- review automated output and exceptions;
- protect API credentials and signing keys; and
- monitor completion, failure, retry, fallout and jeopardy states.
Unless expressly agreed in an Order, Customer must not configure TelBrix as the sole control for:
- emergency communications or emergency-service availability;
- public-safety or life-critical functions;
- automatic activation or shutdown capable of causing injury or physical damage;
- lawful-interception, emergency-call routing or regulatory reporting; or
- irreversible changes to a live network without human approval.
An accepted job or successful API response does not necessarily mean that an external system, field activity or physical change completed successfully. Customer must use appropriate acknowledgements and reconciliation.
11. Data quality and migration
Customer is responsible for the source, legality, completeness and accuracy of network, asset, customer, location and operational data supplied to TelBrix.
For data migration or import:
- Customer must approve mappings, transformations and reconciliation rules;
- samples and totals must be validated before cutover;
- source systems should be retained for an agreed verification period;
- exceptions must be reviewed by qualified personnel; and
- go-live approval remains Customer's decision.
Urbbit is responsible for performing migration services with due care and skill where included in a statement of work, but is not responsible for defects already present in source data or Customer-approved mappings.
12. Industry and regulatory compliance
Customer is responsible for determining and meeting laws, licence conditions, industry codes, standards, permits and reporting obligations applicable to its activities and locations.
This may include obligations concerning telecommunications providers, critical infrastructure, privacy, data retention, network security, emergency services, interception capability, consumer protection, environmental protection, workplace safety, construction, accessibility and record keeping.
Where a requirement affects TelBrix configuration or Urbbit's performance, it must be identified in the Order, DPA, Security Schedule or statement of work. Urbbit does not warrant compliance with a Customer-specific regulatory regime unless the applicable requirement and Urbbit responsibility are expressly documented.
Customer must not describe TelBrix or Urbbit as certified, accredited or approved by a regulator or standards body unless Urbbit has provided written evidence supporting the exact statement.
13. Critical infrastructure and high-impact use
Before using TelBrix for a critical-infrastructure or high-impact environment, Customer must perform its own risk assessment and agree with Urbbit on:
- deployment and data location;
- security classification and control ownership;
- identity and privileged access;
- logging, monitoring and audit evidence;
- backup, recovery and continuity objectives;
- incident response and notification;
- vulnerability and patch management;
- subcontractors and remote support;
- change control and release management; and
- exit and transition arrangements.
These responsibilities must be recorded in an Order and Security Schedule. Urbbit is responsible only for controls assigned to it.
14. Cloud, on-premise and hybrid deployments
For Urbbit-hosted TelBrix, Urbbit is responsible for the cloud and application controls allocated to it in the Security Schedule. Customer remains responsible for its users, endpoints, data, configurations and connected systems.
For customer-hosted TelBrix, Customer is responsible for its infrastructure, network, operating systems, databases, identity, certificates, security, monitoring, patch deployment, backup and recovery unless an Order assigns a specific responsibility to Urbbit.
For hybrid deployments, the Order must identify system boundaries, interfaces, data flows and control ownership. Each party is responsible for its side of an interface and for protecting credentials it controls.
15. Third-party data and systems
TelBrix may integrate with mapping providers, equipment suppliers, identity providers, communications platforms, OSS/BSS systems, GIS, field-service tools, cloud services and other third-party systems.
Customer chooses and authorises integrations and is responsible for third-party contracts, credentials, permissions and data flows. Urbbit does not control or warrant third-party availability, accuracy, security, compatibility or continued API support.
Manufacturer specifications and other third-party data remain subject to their owners' terms and must be independently verified before procurement, installation or operation.
16. Customer Data and derived output
Customer owns its network designs, inventory, civil records, workflow instances, uploaded media and other Customer Data.
Urbbit owns the TelBrix software, generic catalog structures, validation engine, graph methods, reusable templates, APIs, interface components and underlying technology.
Outputs created from Customer Data remain Customer Data. This does not transfer ownership of Urbbit technology embedded in, required to generate or used to display the output.
Customer may export data using purchased standard functionality. Custom export, transformation and migration assistance may require a statement of work.
17. Security and access
Customer must apply least privilege, multi-factor authentication where available, user lifecycle controls, appropriate separation between design and operational permissions, and secure API credential management.
Customer must promptly notify Urbbit if it suspects:
- unauthorised tenant or network-data access;
- compromised credentials or API keys;
- unapproved orchestration or inventory changes;
- malicious content or integrations; or
- a security weakness affecting TelBrix.
Security testing requires prior written agreement on scope, timing and safety.
18. Availability and support
Availability, maintenance, support hours, incident priorities, response targets, recovery objectives and service credits apply only as stated in an Order or SLA.
An SLA for the TelBrix application does not guarantee availability of Customer-controlled networks, devices, databases, internet access, field systems or third-party integrations.
Planned maintenance and urgent security maintenance are governed by the Urbbit Terms and applicable SLA.
19. Warranties and disclaimers
For paid TelBrix Services, Urbbit warrants that they will materially conform to the applicable Documentation and that Professional Services will be performed with due care and skill.
Subject to rights that cannot be excluded, Urbbit does not warrant that:
- every design, validation or rule will identify every defect or constraint;
- map, catalogue, manufacturer or Customer-supplied data is accurate;
- a design is constructible, compliant or suitable for a particular purpose;
- logical records exactly match physical conditions without field reconciliation;
- a third-party integration will remain available; or
- TelBrix alone satisfies Customer's engineering, safety or regulatory obligations.
The remedies and other warranty terms in the Urbbit Terms or signed Enterprise Agreement apply.
20. Responsibility for physical work and operational decisions
To the maximum extent permitted by law, Urbbit is not responsible for injury, property damage, network outage, excavation damage, construction rework, equipment incompatibility, regulatory action or service interruption to the extent caused by:
- failure to obtain professional or field verification;
- inaccurate or incomplete Customer or third-party data;
- use outside Documentation or configured controls;
- an unauthorised override or orchestration command;
- Customer's equipment, personnel, contractor or environment; or
- Customer's failure to meet its obligations under these Telco Terms.
This section does not exclude responsibility to the extent directly caused by Urbbit's breach, negligence, fraud or wilful misconduct, and remains subject to non-excludable law and the agreed liability provisions.
21. Suspension of high-risk activity
In addition to suspension rights under the Urbbit Terms, Urbbit may suspend an affected integration, credential, job type or function where we reasonably believe its continued operation presents an immediate and material risk to security, another tenant, a live network, physical safety or legal compliance.
Where practicable, Urbbit will notify Customer, limit the suspension and work with Customer to restore safe operation.
22. Governing law
These Telco Terms are governed by the laws of Victoria, Australia. The dispute process and jurisdiction provisions in the Urbbit Terms apply.
23. Contact
Questions about these Telco Terms or TelBrix may be sent to:
- Urbbit Pty Ltd
- ABN 91 615 735 450
- 3 Turin Place, Keilor Lodge, Victoria 3038, Australia
- Email: info@urbbit.com
- Phone: +61 481 133 021
