TelBrix Privacy Supplement
Version 0.1 — Effective 21 August 2026
1. How this supplement works
This TelBrix Privacy Supplement (TelBrix Supplement) explains additional privacy matters for:
telco.urbbit.com;- TelBrix cloud, customer-hosted and hybrid deployments;
- TelBrix APIs and gateways; and
- related telecommunications design, inventory, civil infrastructure, mapping, order and orchestration modules (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).
This supplement must be read with the Urbbit Privacy Policy at
https://urbbit.com/legal/privacy (Master Policy). The Master Policy is
the authoritative platform-wide policy. This supplement extends it for
TelBrix-specific processing and does not replace it.
The relevant Master Policy clauses include:
- section 2 for Urbbit and Customer privacy roles;
- section 3 for information categories;
- section 5 for purposes;
- section 6 for cloud, APIs, integrations and customer-hosted deployments;
- sections 7 to 11 for cookies, marketing, disclosures and overseas recipients;
- sections 12 and 13 for retention, security and breaches;
- sections 15 and 16 for automated processing and privacy rights; and
- section 17 for questions and complaints.
If an Order, Data Processing Addendum (DPA) or collection notice provides a more specific privacy commitment for a TelBrix Customer, that commitment applies to its subject matter.
2. Privacy roles in TelBrix
2.1 Customer-controlled network and workforce data
The telecommunications operator, infrastructure owner, contractor, designer or other organisation using TelBrix (Customer) normally determines why and how TelBrix processes:
- network, site, premises and infrastructure records;
- workforce, contractor and field-service information;
- work orders, tasks, approvals and audit records;
- end-customer or occupant information;
- designs, maps, routes, media and documents; and
- information received from Customer systems and integrations.
This information is Customer Data. Urbbit generally processes it on the Customer's documented instructions to provide and support TelBrix. The Customer's privacy policy and the DPA govern that processing.
Individuals should usually direct requests about Customer Data to the Customer identified in the TelBrix account, work order, communication or collection notice.
2.2 Information Urbbit controls
Urbbit controls personal information used for:
- the
telco.urbbit.compublic website; - direct TelBrix account identity, authentication and agreements;
- Urbbit sales, demonstrations, contracts and billing;
- platform security, licence administration and abuse prevention;
- Urbbit-delivered support and Professional Services; and
- Urbbit marketing and business communications.
The Master Policy governs those activities.
2.3 Customer-hosted TelBrix
For a customer-hosted deployment, Customer controls the environment and the Customer Data stored in it. Urbbit receives only the licence, update, usage, diagnostic and support information disclosed in the Order, Documentation, Master Policy section 6.4 and section 10 of this supplement.
3. TelBrix information categories
In addition to information described in Master Policy section 3, TelBrix may process the following when a Customer configures or supplies it.
3.1 Telco account and access information
- organisation, domain, module and client context;
- network or project membership;
- design, inventory, administration and field-work roles;
- invitations, delegations and approval authority;
- authentication, session and API events; and
- access and change audit history.
3.2 Workforce and project information
- employee, contractor, designer, approver and field-worker identity;
- business contact details and organisation;
- team, skill, role and work allocation;
- task status, notes, comments, attachments and completion evidence;
- approval, rejection, exception and escalation history; and
- support or project communications.
3.3 Location and premises information
- site, premises, building and access-structure addresses;
- coordinates, routes, service areas and boundaries;
- landowner, occupant, site-contact or access-contact details;
- map searches and selected locations;
- field observations, photographs and documents; and
- device location where Customer enables a location-aware function and has an appropriate lawful basis.
Network and location data does not always identify a person. It is personal information where it identifies or can reasonably be linked to an individual. It may also be confidential or security-sensitive even when it is not personal information.
3.4 Design, inventory and connectivity activity
- network and civil design authorship;
- catalogue selections and configuration;
- canvas placement and connection changes;
- inventory creation, allocation and lifecycle updates;
- rack, equipment, port, cable, fibre and splice records;
- revision, validation, lock and conflict events;
- export and report activity; and
- linked order, task and orchestration events.
3.5 API, integration and operational metadata
- request identity, client or agent identifier and tenant;
- endpoint, date, time, status and duration;
- API credential or key identifier, without intentionally logging the secret;
- source IP, device and application information;
- job, event, retry, failure and reconciliation metadata;
- integration provider and configured connection;
- error, diagnostic and performance information; and
- security, access and administrative events.
3.6 Telco end-customer information
A Customer may configure TelBrix to process information relating to its own business or residential customers, such as a name, contact method, service address, appointment, order or premises connection.
Urbbit does not independently collect this information for advertising or consumer profiling. The Customer is responsible for its collection notice, lawful basis, minimisation, access controls, retention and consumer rights.
4. How TelBrix information is collected
TelBrix information may be collected:
- from an individual using TelBrix;
- from the Customer, its administrators, personnel and contractors;
- from imported catalogue, GIS, inventory, order or workforce data;
- from Customer OSS/BSS, identity, GIS, field-service and other systems;
- from authorised APIs, webhooks and gateways;
- from maps, geocoding and location services selected by Customer or Urbbit;
- from devices used for authorised field or operational work;
- automatically through security, audit, transaction and application logs; and
- through support and implementation activity authorised by Customer.
Customer must ensure it is authorised to provide the information and that people receive required collection notices.
5. Why TelBrix processes information
| TelBrix purpose | Typical information | Master Policy reference |
|---|---|---|
| Authenticate and select the correct tenant | identity, account, organisation, domain, role and session information | sections 5 and 6.1 |
| Build and collaborate on network designs | author, project, catalogue, canvas, connectivity, revision and comment information | sections 5, 6.2 and 6.3 |
| Display maps and manage locations | address, coordinate, route, boundary, map-query and device information | sections 5, 6.3, 10 and 11 |
| Manage physical inventory and civil assets | user, change, location, equipment, connection, lifecycle and audit information | sections 5 and 6.2 |
| Allocate and evidence work | workforce identity, contact, task, status, location, note, media and approval information | sections 5 and 6.2 |
| Execute orders and orchestration | user, authority, order, job, event, integration and reconciliation information | sections 5, 6.2 and 6.3 |
| Maintain integrity and auditability | identity, revision, validation, change, lock, approval and audit information | sections 5 and 13 |
| Secure, support and improve TelBrix | account, authentication, log, diagnostic, performance and usage information | sections 5, 6.4 and 13 |
| Meet Customer and legal requirements | contract, audit, security, retention and regulatory information | sections 5, 12, 13 and 19 |
Urbbit processes Customer Data only to deliver, secure and support the TelBrix Services, follow Customer instructions and comply with law. Urbbit does not use TelBrix Customer Data for behavioural advertising.
6. Maps, geospatial data and device location
6.1 Map and geocoding services
When a map, address search, geocoder, route or imagery service is used, the provider may receive:
- the requested address, coordinate, area or route;
- IP address and device or browser information;
- map interaction and provider-specific identifiers; and
- other information described in the provider's privacy policy.
The applicable provider and processing country must be identified in the Subprocessor List, map interface or Customer configuration. Customer-selected providers process information under Customer's arrangement with them.
Where practicable, TelBrix sends only the information needed for the requested map function. Do not enter a person's name or unrelated personal information into a map search.
6.2 Device location
TelBrix will access precise device location only where:
- a location-aware feature has been enabled;
- the device or browser grants permission;
- Customer has authorised the feature and established an appropriate lawful basis; and
- the person receives any notice required by law.
Customer must not use TelBrix device location for covert or disproportionate workforce surveillance. Customer controls device permissions and may disable the feature. The collection notice must state whether location is collected in the foreground, background or only when an action is submitted.
6.3 Infrastructure sensitivity
Network routes, sites, connectivity and critical-infrastructure information may create security risks even when it is not personal information. Urbbit and Customer protect that information under the contract, Security Schedule and access controls. Privacy rights apply only to the extent the information is personal information.
7. Workforce, contractor and field information
Customer determines whether TelBrix is used to allocate work, record attendance, collect completion evidence or associate changes with a person.
Customer must:
- collect only information reasonably necessary for the work;
- notify personnel and contractors;
- comply with workplace, surveillance, tracking and employment laws;
- avoid continuous or background tracking unless specifically justified and lawful;
- restrict supervisors and administrators to appropriate access;
- define retention for notes, images and location evidence; and
- provide a process to correct inaccurate records.
Urbbit does not use Customer workforce data to score personnel for its own purposes.
8. Premises, occupant and end-customer information
Customer may associate a network design, order or inventory item with a service address or contact. Customer must minimise this information and keep operational network data separate from end-customer information where practical.
Customer is responsible for:
- notices and consent where required;
- lawful use for service delivery, access and appointments;
- protecting vulnerable-customer or sensitive information;
- limiting field-worker access;
- retention and deletion after the operational purpose ends; and
- responding to the individual's requests and complaints.
Unless expressly included in an Order and DPA, Customer must not place identity documents, payment card data, health information, government identifiers or other highly sensitive information in free-text notes, media or network design records.
9. Design, inventory and audit history
TelBrix associates changes with users to support integrity, collaboration, accountability, investigation and regulatory records. Depending on Customer configuration, audit information may include:
- who viewed, created, changed, approved, exported or deleted a record;
- before-and-after values;
- date, time, tenant, application and source information;
- reason, comment, task, order or revision; and
- security and access events.
Customer determines the business retention of Customer audit records, subject to the Order, technical safeguards and law. A correction to an operational record may preserve the original event in audit history rather than erase it. Where appropriate, access to audit history is restricted and the current record is corrected without destroying evidence required for integrity or law.
10. Customer-hosted telemetry and support
For customer-hosted TelBrix, transmitted operational information is limited to what is disclosed in the Order and Documentation and reasonably required for:
- licence activation and validation;
- purchased usage measurement;
- version and update management;
- security and abuse prevention; and
- optional diagnostics or support requested by Customer.
Product analytics must not transmit network designs, routes, inventory, connectivity, premises, work notes, media or other substantive Customer Data.
If Customer asks Urbbit to investigate an issue, Customer must minimise and redact diagnostic material where practicable. Remote access requires Customer authorisation and must use the agreed secure access method and time window.
11. APIs, gateways and third-party integrations
Customer may connect TelBrix to identity, GIS, OSS/BSS, CRM, ERP, field-service, communications, cloud, mapping and other systems.
An integration may disclose Customer Data and account or request metadata to the provider. Customer is responsible for:
- choosing and authorising the provider;
- granting appropriate scopes;
- configuring the data flow;
- reviewing the provider's privacy and security terms;
- notifying affected individuals; and
- disabling access when no longer required.
Urbbit uses API metadata for routing, authentication, audit, usage measurement, support and security as described in Master Policy sections 5 and 6.3.
12. Disclosure and overseas recipients
The disclosure categories in Master Policy section 10 apply to TelBrix. TelBrix-specific recipients may include:
- the Customer and authorised administrators, designers, field personnel and contractors;
- Customer-selected implementation and delivery partners;
- map, imagery, geocoding and routing providers;
- Customer-authorised GIS, OSS/BSS, workforce and communications systems;
- cloud, database, storage, logging and support providers; and
- regulators or authorities where disclosure is legally required.
The current Urbbit Subprocessor List must identify subprocessors that handle TelBrix Customer Data and likely overseas processing countries. Customer may select a hosting region through an Order, but Customer-authorised integrations and support arrangements may cause additional transfers.
The safeguards and Customer responsibilities in Master Policy section 11 apply.
13. Retention and deletion
Master Policy section 12 applies.
For Customer Data, Customer determines retention subject to its legal obligations, the Order, DPA and available configuration. Customer should define separate retention for:
- draft and superseded designs;
- operational inventory and connectivity;
- work orders, notes and completion media;
- premises and contact information;
- device location and field evidence;
- audit and security events;
- integration payloads and failed jobs; and
- exports and support material.
TelBrix may preserve an immutable or append-only event where deletion would damage record integrity or breach a legal requirement. Where appropriate, the personal fields in the event should be minimised, pseudonymised or access restricted.
On subscription termination, export and deletion follow the Master Policy, Order and DPA. Customer controls deletion in a customer-hosted environment.
14. Security
The safeguards and shared responsibilities in Master Policy section 13 apply. TelBrix security may additionally include:
- organisation, domain and tenant isolation;
- role-based access to catalogue, design, inventory and administration;
- revision, validation, lock and conflict controls;
- API authentication and request integrity;
- audit history for material changes;
- separation of design and operational privileges where configured;
- controlled support access; and
- backup and recovery appropriate to the deployment.
Customer is responsible for its users, endpoints, permissions, data classification, connected systems and Customer-controlled environment.
Report a suspected TelBrix privacy or security incident immediately to info@urbbit.com with the subject TelBrix Security Incident. Do not place secrets or unnecessary personal information in the initial email.
Security-incident assessment and notifications follow Master Policy section 13 and the DPA.
15. Automated workflows and decisions
TelBrix may automate validation, task routing, reminders, job execution, inventory updates and exception handling according to Customer configuration.
Urbbit does not independently use TelBrix Customer Data to make employment, credit, access-to-service or other legally significant decisions about individuals.
Customer is responsible for:
- determining whether its workflow makes or supports a significant decision;
- configuring appropriate human approval and review;
- validating rules and input data;
- explaining the Customer's decision where required; and
- providing a way to challenge and correct inaccurate information.
Master Policy section 15 applies to artificial intelligence and automated processing.
16. Privacy rights and corrections
For personal information Urbbit controls directly, use the process in Master Policy section 16.
For network, workforce, premises, end-customer, work-order or other Customer Data:
- contact the Customer that controls the TelBrix tenant;
- identify the relevant account, project, order, site or record;
- explain the access, correction, deletion or other request; and
- allow the Customer to verify identity and authority.
If you contact Urbbit, we may refer the request to the Customer and assist it under the DPA. We will not disclose Customer Data directly where doing so would bypass Customer authority, expose another person or tenant, compromise security, or breach law.
Where an inaccurate current record must be corrected but audit history must be preserved, the Customer may correct the current value and attach an appropriate statement or restricted correction record.
17. Cookies and public telco website
The cookie and website practices in Master Policy sections 3.5, 6, 7 and 18
apply to telco.urbbit.com.
The TelBrix website cookie settings tool must identify the technologies
actually used on that domain. A choice recorded on urbbit.com may not carry
to telco.urbbit.com where browser or domain controls prevent it, in which
case the TelBrix site must request or remember its own choices.
18. Questions and complaints
For a complaint about a Customer's use of TelBrix Customer Data, contact that Customer first.
For a complaint about Urbbit's handling of personal information, use the Master Policy section 17 process:
- email: info@urbbit.com, subject TelBrix Privacy Complaint;
- phone: +61 481 133 021; or
- post: Privacy Officer, Urbbit Pty Ltd, 3 Turin Place, Keilor Lodge, Victoria 3038, Australia.
Urbbit aims to respond within 30 calendar days. The OAIC escalation information in Master Policy section 17 applies.
19. Changes to this supplement
Urbbit may update this supplement when TelBrix features, integrations, providers, deployments or legal obligations change. We will update the version and effective date and provide reasonable notice of material changes.
If a new TelBrix function materially changes the collection or use of personal information, we will provide an appropriate collection notice or seek consent before the new processing where required.
20. Contact Urbbit
- 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
