TelBrix Cookie Policy
Version 1.0 — Effective 21 August 2026
This TelBrix Cookie Policy explains how Urbbit Pty Ltd (ABN 91 615 735 450)
(Urbbit, we, us or our) uses cookies and similar technologies on
telco.urbbit.com and in Urbbit-hosted TelBrix services (TelBrix).
It supplements the Urbbit Cookie Policy at
https://urbbit.com/legal/cookies (Master Cookie Policy) and the TelBrix
Privacy Policy at https://telco.urbbit.com/legal/privacy. The Master Cookie
Policy explains cookie types, security, management, retention and Urbbit's
general practices. This policy describes how those practices apply to TelBrix.
1. Scope and priority
The Master Cookie Policy applies to TelBrix unless this policy states a more specific TelBrix practice. If the policies conflict, this TelBrix Cookie Policy applies to TelBrix-specific cookie use.
This policy applies to cookies and similar technologies controlled by Urbbit. A telecommunications operator or other Customer may deploy TelBrix under its own domain, infrastructure and privacy framework. Section 9 explains the responsibilities for those deployments.
2. Why TelBrix uses cookies
TelBrix uses cookies primarily for security and personalisation. They may be used to:
- authenticate a user and maintain a secure session;
- resolve the correct TelBrix domain, organisation and tenant;
- prevent credentials or sessions from colliding across Urbbit domains;
- protect sensitive network, location and infrastructure information;
- detect unauthorised access, abuse and suspicious sessions;
- remember privacy and cookie choices; and
- remember optional canvas, map, navigation and display preferences.
Cookies do not replace TelBrix permission checks. Remembering an organisation, network, map view or module does not grant access to it.
3. Strictly necessary and security cookies
TelBrix uses the Urbbit authentication cookies described in the Master Cookie
Policy. The current cookie generally uses a domain-scoped name in the form
__token_<domain identifier>.
This cookie may maintain an authenticated session or refresh capability and associate it with the resolved TelBrix domain. It is:
- first-party;
- HTTP-only;
- configured with
SameSite=Lax; - marked
Secureover HTTPS; and - normally a browser-session cookie, subject to earlier token expiry, sign-out or revocation.
A transitional __token cookie may be used by compatible legacy clients and
is removed when the current domain-scoped cookie replaces it where applicable.
TelBrix may also use strictly necessary storage to remember a privacy choice, support secure routing, apply rate limits, prevent abuse and protect service availability. Blocking these technologies may prevent sign-in, organisation selection, editing, protected APIs or other TelBrix functions from working.
4. Functional and personalisation storage
Optional cookies or local-storage records may remember user preferences such as:
- the selected canvas or map view;
- theme, language, time zone or accessibility preferences;
- panel position, table configuration, zoom or display density;
- visible map layers or other visualisation choices;
- a recently selected organisation, network, order or module;
- search, filter and sorting preferences;
- dismissed guidance, notices or onboarding steps; and
- other user-interface choices.
These technologies are intended to remember the preference or relevant object identifier, not the underlying network design, inventory, map geometry, fibre records, work-order content or telecommunications customer data.
Access to all TelBrix records continues to be determined by the server-side session, organisation membership, role, policy and record permissions. If a remembered selection is no longer authorised, TelBrix must not return the record.
Where required by law, optional personalisation storage is used only after the user makes the relevant cookie choice. Clearing it resets the affected preferences but does not normally delete Customer Data held in TelBrix.
5. Analytics and advertising
TelBrix may use aggregated service logs and privacy-protective measurements for security, reliability, capacity planning and product improvement. A non-essential analytics technology will be listed in the TelBrix cookie settings tool and used only with any consent required by law.
Urbbit does not use TelBrix cookies for cross-site behavioural advertising. We do not sell TelBrix cookie identifiers or allow advertising networks to use TelBrix authentication, network activity or personalisation data to follow users across unrelated websites.
6. TelBrix cookie inventory
The core TelBrix inventory is:
| Cookie or storage | Category | Provider | Purpose | Typical duration |
|---|---|---|---|---|
__token_<domain identifier> |
Strictly necessary and security | Urbbit | Maintains an authenticated TelBrix session or refresh capability and separates configured domains | Browser session, earlier token expiry, sign-out or revocation |
__token |
Strictly necessary and security | Urbbit | Transitional authentication cookie for compatible legacy clients | Browser session, earlier token expiry, sign-out, replacement or revocation |
| Cookie-consent or privacy-choice record | Strictly necessary | Urbbit or the configured consent service | Remembers the user's optional-cookie choices | Duration displayed by the cookie settings tool or until cleared |
| TelBrix preference record, which may use a cookie or local storage | Functional and personalisation | Urbbit | Remembers optional canvas, map, navigation, accessibility and display choices | Duration displayed by the cookie settings tool or until cleared |
The TelBrix cookie settings tool is the current operational inventory for that domain. It must identify the actual cookie or storage name, provider, purpose and duration for any optional technology in use. A technology is not active merely because its category appears in this policy.
7. Maps, media and connected services
TelBrix may display maps, imagery, documents, media or information supplied by third-party providers or connect to Customer-selected identity, GIS, OSS, BSS, NMS and support services.
Loading an enabled third-party resource may disclose ordinary request information, such as an IP address, browser information and the requested resource, to that provider. A provider may also use cookies or local storage under its own privacy terms.
Where Urbbit controls an optional third-party technology, the TelBrix cookie settings tool will identify it and Urbbit will obtain any consent required by law. Where a Customer selects, configures or controls the provider, the Customer is responsible for the required privacy assessment, notice, consent and contractual authority.
Urbbit does not authorise a third-party provider to receive TelBrix passwords, authentication cookies, network designs or inventory records merely because a map, media or integration feature is enabled.
8. Sensitive telecommunications information
TelBrix cookies and personalisation storage are not intended to hold full network topology, precise infrastructure routes, equipment layouts, fibre or splice assignments, customer-premises data, access credentials or work-order content.
Users must not copy an authentication cookie, session value or sensitive network information into browser extensions, public troubleshooting tools or unapproved third-party services. Account and credential sharing is prohibited under the Urbbit Platform Licence Agreement and TelBrix Telecommunications Licence Supplement.
If a device or session may be compromised, the user should sign out where
possible, stop using the affected device, notify their organisation's security
contact and contact info@urbbit.com promptly.
9. Cloud, on-premise and Customer-controlled domains
For Urbbit-hosted TelBrix, Urbbit controls the core authentication cookies and the optional technologies it selects.
For on-premise, private-cloud, hybrid or Customer-branded deployments, the Customer may control the domain, identity provider, hosting environment, cookie configuration and additional integrations. The Customer is responsible for:
- identifying all cookies and similar technologies it adds or configures;
- giving an accurate cookie and privacy notice;
- obtaining and recording any required consent;
- configuring cookie domains, paths, security and retention appropriately;
- ensuring third-party tools do not receive unauthorised network or workforce information; and
- respecting withdrawal and browser choices.
Urbbit remains responsible for technology and processing that Urbbit independently controls. The parties' privacy roles may be further described in an Order or Data Processing Addendum.
10. Managing choices
Users can manage optional TelBrix cookies through the cookie settings tool, where available, and through their browser or device settings.
A choice made on urbbit.com may not automatically apply to
telco.urbbit.com, a Customer domain or another browser because browser and
domain-security controls keep site data separated. TelBrix may therefore ask
the user to make or confirm a separate choice.
Blocking or deleting strictly necessary cookies may sign the user out or stop protected TelBrix functions. Deleting personalisation storage may reset the canvas, map, panel, filter or display experience to its default settings.
11. Retention and security
Cookie retention and security follow the Master Cookie Policy. Authentication cookies normally last for the browser session but may become invalid earlier through token expiry, sign-out, credential rotation, organisation switching or security revocation.
Security and audit records associated with a session may be retained separately for a reasonable period to protect TelBrix, investigate misuse and meet legal or contractual requirements. Clearing the browser cookie does not necessarily delete those server-side records.
12. Changes to this policy
We may update this TelBrix Cookie Policy when TelBrix features, providers, security practices or legal obligations change. We will publish the updated version and effective date. If a change materially expands optional tracking or personalisation, we will seek a new choice where required by law.
13. Contact
For questions or requests about TelBrix cookies or privacy, 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
