TelBrix Telecommunications Licence Supplement
Version 1.0 — Effective 21 August 2026
This TelBrix Telecommunications Licence Supplement (TelBrix Licence) is between Urbbit Pty Ltd (ABN 91 615 735 450) (Urbbit, we, us or our) and the person or entity that acquires or uses TelBrix (Customer, you or your).
It applies to TelBrix cloud, on-premise and hybrid deployments and supplements
the Urbbit Platform Licence Agreement at https://urbbit.com/legal/licence
(Master Licence) and the TelBrix Telco Service Terms at
https://telco.urbbit.com/legal/terms (Telco Terms).
1. Acceptance and priority
You accept this TelBrix Licence by accepting an Order for TelBrix or by accessing, installing or using TelBrix. If you accept for an organisation, you confirm that you are authorised to bind it.
Capitalised terms not defined here have the meaning given in the Master Licence or Telco Terms.
If documents conflict, the order of priority in the Master Licence applies, with this TelBrix Licence taking priority over the Master Licence only for TelBrix-specific software-use and security matters. A negotiated agreement or Order signed by both parties remains higher priority.
2. TelBrix licence scope
Subject to the Master Licence, applicable Order and payment of fees, Customer may use the licensed TelBrix modules for authorised telecommunications planning, design, inventory, construction, fulfilment and operational-support purposes. Depending on the Order, these may include:
- resource roles, specifications, models, properties and catalogue controls;
- network design, topology, connectivity graphs and revision history;
- design canvas and map visualisation;
- physical network and equipment inventory;
- racks, cabinets, devices, ports, fibres, cables, joints, splices and paths;
- sites, routes, ducts, pits, access structures and civil infrastructure;
- orders, tasks, workflows and catalogue-driven orchestration;
- reports, imports, exports, APIs, webhooks and approved integrations; and
- related Documentation, updates and support tools.
The licence is limited to the organisations, operators, domains, environments, modules, users, instances, network areas, data volumes and integrations stated in the Order.
3. Authorised telecommunications users
TelBrix access may be granted only to named people who need it for Customer's authorised work, such as employees, network designers, engineers, planners, field personnel and approved contractors.
Customer must use roles and permissions appropriate to each person's duties. Privileged functions, bulk exports, orchestration, production integrations and security administration must be restricted to specifically authorised users.
A contractor or delivery partner must use their own named account under the correct Customer organisation. Customer must not share an employee account with a contractor, use a single field-team login for multiple people or give a third party a production API key unless the Order and Customer's security controls expressly permit that access.
4. Telecommunications data is sensitive
Network topology, asset locations, coordinates, routes, duct and pit details, equipment layouts, fibre assignments, ports, splices, capacity, customer premises, work orders, access arrangements and integration credentials may be commercially, operationally or security sensitive.
Customer must classify and protect that data according to its sensitivity, applicable law and its contractual duties. Access must be based on business need. Exports and disclosures must be authorised, traceable and limited to the minimum data required.
Customer must not assume that marking a design as draft, concept or non-operational makes the underlying network or location information public.
5. TelBrix-specific prohibited conduct
The prohibited-conduct rules in the Master Licence apply. In addition, Customer and Authorised Users must not, and must not assist or permit anyone else to, engage in the following conduct.
5.1 Unauthorised access and cross-tenant activity
- access or attempt to access another operator's, tenant's, organisation's, domain's or user's TelBrix data or functions;
- manipulate a host, domain, agent identifier, organisation identifier, token, request header, API parameter or object identifier to cross an access boundary;
- use credentials obtained for one operator, project, environment or purpose to access another;
- enumerate identifiers, endpoints, users, assets, locations or network records without a legitimate authorised purpose; or
- exploit a configuration error, broken access control or data leak instead of stopping and reporting it.
5.2 Hacking and security interference
- hack or attempt to hack TelBrix, its APIs, databases, gateways, infrastructure, integrations or a connected customer system;
- scan, probe, fuzz, penetrate, load-test or test tenant isolation without Urbbit's prior written authorisation;
- bypass authentication, multi-factor authentication, role checks, workflow approvals, edit locks, rate limits, licence controls, audit history or other safeguards;
- steal, replay, forge, publish or share passwords, one-time codes, session tokens, API keys, webhook secrets, certificates, signing keys or Licence Credentials;
- introduce malicious code, destructive data, denial-of-service activity or an unauthorised remote-control mechanism; or
- alter, suppress or destroy security logs, revision records, approvals or incident evidence.
5.3 Network design and inventory integrity
- knowingly create, import or retain false or deceptive network, asset, connectivity, capacity, location or ownership data;
- tamper with graph relationships, cable endpoints, fibres, ports, splices, routes, containment, equipment hierarchy or lifecycle state to conceal an unauthorised change;
- bypass catalogue, validation, reservation, versioning, approval or change controls in order to commit an invalid or unapproved design;
- delete or modify records to conceal asset loss, unauthorised access, unapproved work or a safety issue; or
- represent a concept, draft, proposed or unverified design as an as-built or operationally verified record without proper authority.
Good-faith correction of inaccurate data through authorised workflows is not prohibited.
5.4 Live networks, orchestration and integrations
- issue an order, job, command, configuration or orchestration instruction to a live network or connected system without Customer's authority and required approval;
- bypass a change window, segregation-of-duties control, safety gate, approval step, rollback requirement or operational policy;
- use TelBrix to disrupt, degrade, reroute, intercept, disable or obtain unauthorised control of a telecommunications service or network;
- alter API, webhook, import or integration payloads to perform an action not authorised by the documented interface and assigned role;
- connect TelBrix to a production OSS, BSS, NMS, GIS, identity service or network device using credentials or permissions Customer is not authorised to provide; or
- continue an automated job or integration after becoming aware that it is producing unsafe, corrupt, excessive or unauthorised changes.
5.5 Misuse and disclosure of network information
- export, scrape, publish, sell or disclose sensitive network or civil infrastructure data without authority;
- share screenshots, maps, topology, equipment layouts, credentials or bulk exports with an unapproved subcontractor or on a public service;
- use TelBrix information to facilitate theft, sabotage, unlawful access, surveillance, service interruption, unsafe excavation or physical harm; or
- use data belonging to another operator, customer, carrier, landowner or infrastructure provider outside the licensed and authorised purpose.
6. Account and credential breaches
Each human user must have a named account. Account sharing is prohibited even when users work for the same team, shift, contractor or operator.
The following are material breaches:
- giving another person your password, passkey, one-time code or active session;
- allowing another person to act under your identity or approval authority;
- reusing a former worker's account;
- sharing privileged, integration or Licence Credentials outside their approved machine or custodian group;
- using a shared account to avoid user licences or attribution; and
- failing to revoke known compromised or obsolete credentials after notice.
Service accounts may be used only for documented, non-human integration purposes. They must have an accountable owner, minimum permissions, secure secret storage, rotation appropriate to risk and auditable use.
7. Security testing and vulnerability reports
Customer must obtain Urbbit's prior written authorisation before conducting penetration, vulnerability, isolation, load or adversarial testing against any Urbbit-hosted TelBrix environment. Approval will define the systems, methods, time period, traffic limits and notification contacts.
For Customer-Hosted Software, Customer may test infrastructure it owns or is authorised to test, but must not target Urbbit services, licence systems, update systems or another tenant, and must comply with third-party rights and applicable law.
A person who discovers a suspected weakness must stop before accessing network
data or functions beyond their authority, preserve confidentiality and report
it promptly to info@urbbit.com with the subject TelBrix Security Report.
Discovery does not authorise continued exploitation, data extraction,
persistence or public disclosure.
8. Customer security and governance obligations
Customer must maintain controls appropriate to its TelBrix deployment and risk, including:
- identity lifecycle management, multi-factor authentication and least privilege;
- separation of development, test and production environments;
- approval and change controls for bulk changes and orchestration;
- secure management and rotation of API, webhook, database and integration secrets;
- monitoring of privileged actions, exports, failed access and integrations;
- backups, recovery testing and retention appropriate to network records;
- supported software versions and timely security patching;
- contractor onboarding, confidentiality and prompt offboarding; and
- incident response contacts and procedures.
Customer is responsible for configuring the correct organisation, domain, agent, role and environment for its users and integrations. Urbbit is responsible for the security obligations allocated to it under the applicable contract documents.
9. Operational responsibility
TelBrix is a planning, design, inventory, workflow and operational-support platform. Unless an Order expressly provides a certified control function, TelBrix is not a real-time network control, emergency response, safety, surveying or regulatory compliance system.
Customer remains the network operator and decision-maker. Customer must use qualified personnel and appropriate independent checks before construction, excavation, splicing, activation, migration, decommissioning or changes to a live network.
Customer is responsible for determining and meeting applicable carrier, telecommunications, privacy, safety, land-access, critical-infrastructure, recordkeeping and regulatory obligations. A TelBrix validation or successful workflow does not certify legal, engineering, field or operational compliance.
10. Incident containment and suspension
In addition to the Master Licence and Telco Terms, Urbbit may take immediate, proportionate action where it reasonably believes an activity threatens another tenant, a live network, sensitive infrastructure information, data integrity, physical safety, service availability or legal compliance.
Containment may include:
- revoking an affected session, credential, API key or Licence Credential;
- pausing an import, export, webhook, job, workflow or orchestration;
- disabling a high-risk role, function, integration or environment;
- making affected records temporarily read-only;
- isolating an organisation, tenant or Customer-Hosted Software connection; or
- suspending affected access.
Urbbit will, where practicable, notify Customer, preserve unaffected use and work with Customer to restore access when the risk is controlled. Advance notice is not required where delay could increase harm or compromise evidence.
11. Material and non-remediable breaches
Without limiting the Master Licence, the following will ordinarily constitute a material breach:
- intentional hacking or attempted unauthorised access;
- deliberate access to another tenant's or operator's data;
- credential theft, trafficking or knowing account sharing;
- malicious alteration of network topology, inventory, audit or approval data;
- an unauthorised command or orchestration directed at a live network;
- deliberate disclosure of sensitive network data for an unlawful or harmful purpose;
- concealment of an intrusion, unsafe change or integrity breach; or
- repeated prohibited conduct after notice.
A breach may be treated as non-remediable where it is intentional, creates a serious safety or network risk, affects another customer, involves malicious code or credential trafficking, or causes a loss of trust that cannot reasonably be restored.
Urbbit may suspend, require remediation or terminate affected rights in accordance with the Master Licence. Customer must pay for confirmed unlicensed use and may be responsible for reasonable investigation, containment and remediation costs to the extent directly caused by its breach and recoverable by law. Urbbit may seek urgent injunctive relief and may notify regulators, affected parties or law enforcement where required or permitted by law.
These remedies do not prevent fair investigation of an accidental mistake or good-faith report. Urbbit will consider intent, impact, repetition, cooperation, containment and the feasibility of remediation.
12. Incident cooperation
Customer must promptly notify Urbbit of suspected compromise, unauthorised access, harmful orchestration, material data corruption or exposure of TelBrix-related credentials.
Each party must reasonably cooperate to:
- contain the incident and prevent recurrence;
- preserve relevant logs, records and evidence;
- identify affected tenants, users, assets, data and connected systems;
- rotate credentials and revoke unauthorised access;
- validate network and inventory data before normal operations resume; and
- meet applicable notification and regulatory obligations allocated to it.
Neither party must make a misleading statement about the incident or destroy relevant evidence. Cooperation does not require a party to waive legal privilege or disclose information contrary to law.
13. Data use, export and return
Customer retains its rights in Customer Data, subject to the Master Licence, Telco Terms, Privacy Policy and applicable data processing terms.
Customer must apply appropriate authorisation and security to bulk exports, map layers, network reports, backups and API access. A user's ability to export data does not by itself establish authority to disclose or reuse it.
On expiry or termination, export and deletion follow the applicable Order and Telco Terms. Customer must remove TelBrix software and Licence Credentials as required by the Master Licence, while retaining network records where Customer is independently required to do so by law.
14. Customer-Hosted and hybrid deployments
For on-premise or hybrid deployments, Customer is responsible for its hosting environment, physical and network security, operating systems, databases, identity services, certificates, backups, monitoring, recovery and access to connected operational systems unless an Order states otherwise.
Customer must not expose administrative, database, internal API or integration interfaces to untrusted networks contrary to the Documentation. Urbbit is not responsible for a compromise caused by Customer's unsupported modification, misconfiguration, leaked secret or failure to apply a supplied security update, except to the extent Urbbit caused or contributed to it.
15. Third-party systems and data
Customer is responsible for its authority to connect and use third-party maps, GIS, OSS, BSS, NMS, identity, field, messaging, storage and network systems. Customer must comply with their licences, rate limits and security requirements.
Urbbit does not grant rights in third-party network, land, premises, customer or geospatial data. Availability of an integration does not mean Urbbit or the third party has approved every use of it.
16. Warranties and limitations
The warranties, non-excludable rights, disclaimers, indemnities and liability limits in the Master Licence and Urbbit Terms apply.
TelBrix outputs depend on catalogue configuration, Customer Data, integrations, user decisions and field verification. Urbbit does not warrant that a design, map, route, capacity result, inventory record or orchestration instruction is accurate or suitable where the underlying information or configuration is incomplete, inaccurate or outdated.
Nothing excludes, restricts or modifies a right or remedy that cannot lawfully be excluded, including any applicable rights under the Australian Consumer Law.
17. Term and effect of termination
This TelBrix Licence begins when Customer first accepts an Order or accesses, installs or uses TelBrix and continues while Customer has a right to use TelBrix.
Expiry, suspension and termination are governed by the Master Licence, Telco Terms and Order. On termination, Customer must stop affected use, remove Customer-Hosted Software and destroy Licence Credentials and copies as required by the Master Licence. Accrued rights and provisions intended to survive are not affected.
18. Governing law
This TelBrix Licence is governed by the laws of Victoria, Australia. The parties submit to the courts of Victoria and applicable Commonwealth courts, subject to the dispute-resolution process in the Urbbit Terms and rights that cannot lawfully be excluded.
19. Contact
Urbbit Pty Ltd — TelBrix
ABN 91 615 735 450
3 Turin Place
Keilor Lodge, Victoria 3038
Australia
Phone: +61 481 133 021
Email: info@urbbit.com
