Urbbit Platform Licence Agreement
Version 1.0 — Effective 21 August 2026
This Urbbit Platform Licence Agreement (Licence Agreement) governs access to and use of software and services supplied by Urbbit Pty Ltd (ABN 91 615 735 450) (Urbbit, we, us or our).
It applies to Urbbit's websites, cloud services, customer-hosted software, mobile or desktop applications, APIs, developer tools, documentation, updates and industry products, including TelBrix and products introduced in the future (collectively, the Platform).
1. Acceptance and authority
This Licence Agreement is a binding contract between Urbbit and the person or entity that acquires or uses the Platform (Customer, you or your).
You accept it when you:
- accept it electronically;
- sign or accept an Order that refers to it;
- install, copy or activate customer-hosted software; or
- access or use the Platform.
If you accept it for an organisation, you confirm that you are authorised to bind that organisation. If you do not have that authority, or do not agree, you must not access, install or use the Platform.
2. Contract documents and priority
This Licence Agreement supplements the Urbbit Website and Platform Terms at
https://urbbit.com/legal/terms (Urbbit Terms). The Urbbit Privacy Policy,
applicable product supplements, Orders, service descriptions, data processing
terms, security schedules and service level agreements may also apply.
If documents conflict, the following order applies unless an Order expressly states otherwise:
- a negotiated agreement signed by both parties;
- the Order;
- a data processing agreement, security schedule or service level agreement for its subject matter;
- an applicable product licence supplement;
- this Licence Agreement;
- the Urbbit Terms; and
- the Documentation.
An Order changes this Licence Agreement only if it identifies the clause being changed and states the agreed change.
3. Definitions
In this Licence Agreement:
- Authorised User means a named individual whom Customer permits to use the Platform within the scope of an Order;
- Customer Data means data, content and instructions submitted to or generated through the Platform for Customer, excluding Usage Data;
- Customer-Hosted Software means Platform software supplied for deployment in Customer's or its hosting provider's environment;
- Documentation means Urbbit's then-current user, technical and API documentation;
- Licence Credential means a licence key, activation code, certificate, token or other mechanism used to activate or measure licensed use;
- Order means an order form, statement of work, online subscription or other ordering document accepted by Urbbit;
- Subscription Term means the period stated in the Order; and
- Usage Data means technical, operational, security and usage information about operation of the Platform that does not identify the substance of Customer Data.
4. Licence grant
Subject to payment of fees and compliance with the contract documents, Urbbit grants Customer, during the Subscription Term, a limited, non-exclusive, non-transferable and non-sublicensable right to:
- allow Authorised Users to access the cloud services identified in the Order;
- install and run the authorised number of instances of Customer-Hosted Software in the approved environments;
- use the Platform for Customer's internal business purposes within the products, organisations, domains, users, capacity and usage limits stated in the Order; and
- use the Documentation in support of that licensed use.
The licence is revocable only as provided by this Licence Agreement, the Urbbit Terms or applicable law. It does not transfer ownership of the Platform or any source code.
Customer may permit its employees and individual contractors to be Authorised Users where they need access to provide services to Customer, are bound by confidentiality and security obligations, and use the Platform only for Customer's benefit. Customer remains responsible for their compliance.
Hosting, managed service, outsourcing, white-label, embedded, resale or service-bureau use is permitted only where an Order expressly grants that right.
5. Licence scope and measurement
Customer must remain within all licensed limits, including limits relating to users, environments, instances, tenants, organisations, modules, data volume, transactions, API calls, compute capacity or other metrics in an Order.
Customer must not use multiple accounts, installations, domains, proxies or technical measures to avoid a licensed limit. If use exceeds the licensed scope, the parties will promptly regularise it through an additional Order or payment of applicable fees. Deliberate concealment or circumvention is a material breach.
6. Accounts and credentials
Each human user must use their own named account. Accounts are personal to the Authorised User and must not be shared, pooled or used concurrently by another person.
Customer and its Authorised Users must:
- keep passwords, passkeys, one-time codes, recovery methods, session tokens, API keys, service credentials and Licence Credentials confidential;
- use multi-factor authentication where offered or required;
- grant only the minimum access needed and review privileged access regularly;
- promptly remove or disable access when a person no longer requires it;
- ensure service accounts are used only for their documented machine purpose; and
- notify Urbbit immediately at
info@urbbit.comof suspected loss, disclosure, compromise or unauthorised use.
Sharing a password, one-time code, session, API key or Licence Credential with another person is prohibited, including sharing between employees to avoid buying or assigning the required licences. A shared mailbox may be used for notifications, but not as a shared human login unless an Order expressly allows it.
Customer is responsible for activity performed through its accounts and credentials to the extent caused by Customer's or an Authorised User's act, omission or failure to comply with these obligations. Customer is not responsible for unauthorised activity caused solely by Urbbit's breach of its security obligations.
7. Customer responsibilities
Customer must:
- use the Platform lawfully and in accordance with the Documentation;
- maintain accurate account, organisation, billing and domain information;
- configure roles, permissions, integrations and retention settings appropriately;
- have all rights, notices and consents needed for Customer Data;
- maintain reasonable endpoint, identity, network and credential security;
- keep supported Customer-Hosted Software and dependencies updated; and
- ensure outputs are reviewed by appropriately qualified people before they are used for material business, safety, financial or operational decisions.
8. Prohibited conduct
Customer and Authorised Users must not, and must not assist or permit anyone else to:
8.1 Intrusion and security attacks
- hack, attempt to hack, compromise or gain unauthorised access to the Platform, an account, another tenant, another organisation, Customer Data, infrastructure, source code or connected system;
- probe, scan, enumerate or test vulnerabilities, ports, endpoints, networks, tenant boundaries or security controls without Urbbit's prior written authorisation;
- bypass or attempt to bypass authentication, authorisation, multi-factor authentication, rate limits, licence checks, usage controls, audit controls, access locks, tenant isolation or other safeguards;
- use credential stuffing, password spraying, stolen credentials, forged tokens, session hijacking, impersonation or privilege escalation;
- introduce malware, ransomware, malicious code, backdoors or destructive payloads, or perform denial-of-service or resource-exhaustion activity;
- exploit a suspected vulnerability beyond the minimum action needed to demonstrate it safely, access other people's data, establish persistence, move laterally or conceal activity; or
- interfere with logging, monitoring, evidence, integrity controls, service availability or another user's lawful use.
8.2 Account, credential and licence abuse
- share, sell, publish, lend or transfer an account, password, one-time code, recovery method, session, API key, signing key or Licence Credential;
- allow an unlicensed person or entity to use the Platform through an Authorised User's account;
- pool accounts, create false identities, conceal the real user or continue to use access belonging to a former employee, contractor or customer;
- resell, sublicense, rent, lease, white-label or commercially provide the Platform except as expressly permitted by an Order; or
- falsify usage, entitlement, organisation, domain or billing information, or manipulate technical controls to avoid fees.
8.3 Misuse of software, data and interfaces
- copy, modify, translate, adapt, create derivative works from, decompile, disassemble or reverse engineer the Platform, except to the limited extent that applicable law does not allow that restriction;
- seek or use source code, non-public APIs, confidential architecture, cryptographic material or internal documentation without permission;
- scrape, harvest or extract data, or use bots or automation, outside the documented APIs and agreed rate limits;
- conduct load, stress, penetration or destructive testing without written authorisation;
- remove or obscure proprietary, attribution or security notices;
- use the Platform or confidential information to build or train a competing product where that use infringes Urbbit's rights or breaches confidentiality; or
- use the Platform for unlawful, fraudulent, abusive or rights-infringing activity.
9. Authorised security testing and reporting
Urbbit welcomes responsible vulnerability reports. Testing is permitted only under Urbbit's written authorisation or a published security testing program and only within its stated scope, methods, systems and time period.
A researcher must stop if testing risks harm, service interruption, privacy or access to data not belonging to them; must not retain or disclose accessed data; and must report the issue promptly and confidentially. Urbbit's receipt of a report does not retrospectively authorise activity outside that scope.
Suspected vulnerabilities should be reported to info@urbbit.com with the
subject Security Report. Good-faith reporting does not entitle a person to
access systems or data without permission.
10. Security incidents and breach response
If Urbbit reasonably believes that an account, credential, integration or use of the Platform creates an immediate security, legal, safety or service risk, Urbbit may take proportionate containment action. This may include:
- revoking sessions, tokens, API keys or Licence Credentials;
- requiring password or key rotation and multi-factor authentication;
- blocking malicious traffic or affected functions;
- isolating an affected tenant, integration, instance or workload; or
- temporarily suspending affected access.
Where practicable, Urbbit will notify Customer and limit action to the affected access. Urbbit may act without advance notice where delay could increase harm, enable evidence destruction or affect another person or system.
Customer must reasonably cooperate with investigation and remediation, preserve relevant records, identify affected users and systems, rotate exposed credentials, apply required security updates and stop prohibited activity. Neither party must obstruct an investigation or destroy relevant evidence.
Urbbit may notify affected parties, insurers, regulators or law enforcement where required by law or reasonably necessary to address suspected unlawful conduct, subject to applicable confidentiality and privacy obligations.
11. Consequences of breach
An intentional attempt to hack the Platform, access another tenant or user, traffic in credentials, introduce malicious code, conceal an intrusion, or deliberately defeat licence or security controls is a material breach. It may be treated as incapable of remedy where the conduct or resulting loss of trust cannot reasonably be cured.
For a remediable material breach, Urbbit may require correction within a reasonable period, ordinarily 30 days. A shorter period may apply where security, privacy, service continuity, legal compliance or another customer is at risk.
Subject to applicable law, Urbbit may:
- suspend affected access under section 10;
- terminate the affected Order or this Licence Agreement for an uncured or non-remediable material breach;
- require payment for unlicensed use at the applicable contracted or then-current rate;
- recover reasonable investigation, containment and remediation costs to the extent directly caused by Customer's breach and recoverable by law;
- seek injunctive or other urgent relief to prevent continuing harm; and
- exercise any other contractual or legal remedy.
These measures are protective and compensatory, not a contractual penalty. Termination does not remove accrued payment obligations or liability arising before termination. Any refund rights remain subject to the Urbbit Terms, the Order and rights that cannot lawfully be excluded.
12. Customer-Hosted Software
For Customer-Hosted Software, Customer is responsible for the hosting environment, operating systems, database, network, backups, certificates, identity provider, endpoint protection, monitoring, disaster recovery and physical security unless an Order states otherwise.
Customer must install supported security updates within a reasonable time having regard to severity and Urbbit's instructions. Urbbit is not responsible for issues caused by unsupported modifications, unauthorised components, failure to apply supplied fixes or an environment outside Urbbit's control.
Customer must not remove telemetry or licence-verification functions where they are part of the licensed build, except where the Order or law permits. Urbbit will not use licence verification to access the substance of Customer Data except where necessary for support or security and authorised under the contract documents.
13. Updates and support
Urbbit may provide patches, security updates, maintenance releases and new versions. Updates form part of the Platform and are governed by this Licence Agreement unless accompanied by separate terms.
Support, maintenance, update rights and end-of-support periods are those stated in the Order, support policy or Documentation. Urbbit may require a supported release before providing support.
14. Third-party and open-source components
The Platform may include third-party or open-source components. Those components may be governed by their own licence notices, which take priority for the relevant component where required. No third-party licence expands Customer's rights to Urbbit's proprietary software.
Customer is responsible for licences and terms applicable to third-party systems, data or services that Customer connects to the Platform.
15. Customer Data, privacy and telemetry
Customer retains its rights in Customer Data. Customer grants Urbbit the limited rights needed to host, process, transmit, secure, support and improve the Platform and to follow Customer's lawful instructions, as described in the Urbbit Terms and applicable data processing terms.
Urbbit may process Usage Data for licensing, billing, security, support, capacity, reliability and product improvement. Urbbit's handling of personal information is governed by the Urbbit Privacy Policy and applicable law.
16. Ownership and feedback
Urbbit and its licensors own all rights in the Platform, Documentation, updates, configurations supplied by Urbbit, methods, designs and related intellectual property. All rights not expressly granted are reserved.
Customer owns Customer Data and Customer materials. If Customer provides feedback, Customer grants Urbbit a perpetual, worldwide, irrevocable, royalty-free right to use it without identifying Customer or disclosing Customer's Confidential Information.
17. Confidentiality
Each party must protect the other party's non-public business, technical, security and commercial information using at least reasonable care and use it only for the contract. Credentials, source code, non-public architecture, vulnerability information and security reports are Urbbit Confidential Information.
The confidentiality exclusions, permitted disclosures and survival rules in the Urbbit Terms apply.
18. Licence verification and records
Customer must keep records reasonably sufficient to confirm licensed users, instances and usage during the Subscription Term and for 12 months afterwards. On reasonable notice, no more than once in any 12-month period unless there is evidence of material under-licensing or security misuse, Customer must provide a written entitlement report or permit a proportionate licence review.
A review must minimise disruption, protect Customer Data and Confidential Information, and not provide Urbbit broader access than reasonably necessary. Customer must promptly purchase required entitlements for confirmed excess use. If deliberate or material under-licensing exceeds 5% of the applicable fees, Customer must also reimburse Urbbit's reasonable external review costs, to the extent permitted by law.
19. Warranties and non-excludable rights
Urbbit warrants that, during a paid Subscription Term, the Platform will materially conform to its Documentation when used as authorised. Customer's remedy is correction, replacement or re-performance and, if Urbbit cannot remedy a material failure within a reasonable period, termination of the affected Service with any refund required by the Urbbit Terms or applicable law.
Except for express warranties and rights that cannot lawfully be excluded, the Platform is provided without implied warranties, including that it will be uninterrupted, error-free or suitable for every purpose.
Nothing in this Licence Agreement excludes, restricts or modifies a guarantee, right or remedy that cannot lawfully be excluded, including any applicable rights under the Australian Consumer Law. Where lawful, Urbbit's liability for a failure of a non-excludable guarantee is limited to the remedies permitted by law.
20. Liability and indemnity
The exclusions, liability caps and indemnities in the Urbbit Terms apply to this Licence Agreement. Nothing limits liability to the extent it cannot be limited by law.
Customer indemnifies Urbbit against third-party claims, regulatory costs and direct losses to the extent caused by Customer's unlawful Customer Data, intentional security attack, credential trafficking, unauthorised sublicensing or infringement of a third party's rights, except to the extent caused by Urbbit. Urbbit must give reasonable notice and cooperation and must not settle a claim in a way that admits Customer's fault or imposes non-monetary duties on Customer without consent.
21. Term, suspension and termination
This Licence Agreement starts on acceptance and continues while Customer has an active account, Order, installation or other right to use the Platform.
Suspension and termination rights in this Licence Agreement are additional to those in the Urbbit Terms. Either party may terminate an Order for the other party's material breach if it is not remedied within the applicable cure period. Urbbit may terminate immediately for a non-remediable material breach, insolvency where lawful, or use that Urbbit is legally prohibited from providing.
On expiry or termination, Customer must stop using the affected Platform, disable access, uninstall Customer-Hosted Software and destroy Licence Credentials and copies, except for archival copies required by law. On request, Customer must confirm completion in writing. Customer Data export and deletion are governed by the Urbbit Terms, Order and applicable data processing terms.
Sections intended by their nature to survive continue, including ownership, confidentiality, accrued payment, liability, indemnity, records, effect of termination, governing law and disputes.
22. Export controls and lawful availability
Each party must comply with applicable trade, sanctions and export-control laws. Customer must not provide access where prohibited by law or use the Platform to develop or facilitate unlawful weapons, cyberattacks or other prohibited activity.
23. Changes to this Licence Agreement
Urbbit may update this Licence Agreement for future purchases and may update it for existing Services where reasonably necessary for law, security, new functionality or business operations. Urbbit will give reasonable notice of a material adverse change. A change will not reduce committed rights during a current fixed Subscription Term unless required by law or needed to address an urgent security risk.
Negotiated signed terms can be changed only in writing by authorised representatives of both parties.
24. General
The assignment, notices, force majeure, severability, waiver, independent contractor, third-party rights and entire-agreement provisions in the Urbbit Terms apply.
The words including and includes are not limiting. Headings are for convenience only. Electronic acceptance and signatures are binding to the extent permitted by law.
25. Governing law and disputes
This Licence Agreement 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 any rights that cannot lawfully be excluded.
26. Contact
Urbbit Pty Ltd
ABN 91 615 735 450
3 Turin Place
Keilor Lodge, Victoria 3038
Australia
Phone: +61 481 133 021
Email: info@urbbit.com
