Urbbit Cookie Policy
Version 1.0 — Effective 21 August 2026
This Cookie Policy explains how Urbbit Pty Ltd (ABN 91 615 735 450)
(Urbbit, we, us or our) uses cookies and similar technologies on
urbbit.com, Urbbit applications, customer portals and cloud services
(collectively, the Services).
It should be read with the Urbbit Privacy Policy at
https://urbbit.com/legal/privacy. The Privacy Policy explains how we handle
personal information, including information collected through cookies and
similar technologies.
1. What cookies are
A cookie is a small text file that a website asks a browser to store on a device. Cookies allow a website to recognise a browser during a session or on a later visit.
Cookies may be:
- session cookies, which ordinarily expire when the browser session ends;
- persistent cookies, which remain until their stated expiry time or until they are deleted;
- first-party cookies, which are set for the website being visited; or
- third-party cookies, which are set by another service whose technology is used on the website.
2. Similar technologies
This policy also covers technologies that perform a similar function, including browser local storage, session storage, software development kits, pixels and scripts. In this policy, references to cookies include these similar technologies unless the context requires otherwise.
Local storage may remain on a device until it is cleared by the user or the application. Session storage normally ends when the browser tab or session is closed. Unlike a cookie, local storage is not automatically included in every request to the server.
3. Our approach
Urbbit uses cookies primarily to:
- protect accounts and Services;
- authenticate users and maintain secure sessions;
- keep domains, organisations and user contexts separated;
- prevent fraud, misuse and unauthorised access;
- remember privacy and cookie choices; and
- remember optional preferences and personalise the user experience.
We follow these principles:
- use only the cookies reasonably needed for a stated purpose;
- use first-party technology for core authentication wherever practicable;
- do not store passwords or one-time verification codes in personalisation cookies;
- do not use cookies for cross-site behavioural advertising;
- do not sell cookie identifiers or browsing behaviour; and
- obtain consent for non-essential cookies where required by applicable law.
4. Categories of cookies we use
4.1 Strictly necessary and security cookies
These cookies are required to provide a requested Service or protect it. They may be used to:
- sign a user in and maintain an authenticated session;
- route a request to the correct domain, organisation or tenant;
- prevent a session issued for one Urbbit domain from being used for another;
- detect suspicious access, abuse or repeated authentication attempts;
- apply security, rate-limit and fraud-prevention controls;
- remember a user's privacy or cookie choice; and
- support load balancing, reliability and service recovery.
Because these cookies are necessary for security or a Service requested by the user, they cannot normally be disabled through Urbbit's cookie settings. A user can block them through browser settings, but sign-in and other protected features may no longer work.
4.2 Functional and personalisation cookies
These optional cookies or local-storage records remember choices so the Services can present a more relevant and consistent experience. Depending on the application, they may remember:
- language, time zone, theme or display preferences;
- navigation, table, panel or layout preferences;
- a recently used organisation, workspace or module;
- accessibility preferences;
- dismissed notices and guided-tour progress; and
- other choices made by the user.
Personalisation does not give a user access to an organisation or function. Server-side permission checks continue to apply even if a browser remembers a selection.
Where required by law, we use functional and personalisation cookies only after the user has made the relevant choice. Users may withdraw that choice or clear the stored preference at any time.
4.3 Performance and analytics
Urbbit may use aggregated service logs and privacy-protective measurements to understand performance, availability and general feature use. We do not activate a non-essential analytics cookie merely because this category is described in this policy.
If Urbbit introduces a non-essential analytics technology, it will be listed in the cookie settings tool with its provider, purpose and duration and will be used only with any consent required by law.
4.4 Advertising and marketing
Urbbit does not use cookies for cross-site behavioural advertising under this policy. We do not permit advertising networks to use Urbbit authentication or personalisation cookies to follow users across unrelated websites.
If this practice changes, we will update this policy and the cookie settings tool before activating the relevant technology and obtain consent where required by law.
5. Current core cookie inventory
The following table describes cookies used by the Urbbit server-side authentication service. The exact domain identifier in a cookie name varies by the Urbbit domain configuration.
| Cookie or storage | Category | Provider | Purpose | Typical duration |
|---|---|---|---|---|
__token_<domain identifier> |
Strictly necessary and security | Urbbit | Maintains an authenticated session or refresh capability and prevents token collision between configured Urbbit domains | Browser session, earlier token expiry, sign-out or revocation |
__token |
Strictly necessary and security | Urbbit | Transitional authentication cookie for compatible legacy clients; the current domain-scoped cookie replaces and removes it when applicable | 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 whether the user accepted, rejected or configured optional cookie categories so the choice can be respected | Duration displayed by the cookie settings tool or until cleared |
| Site preference record, which may use a cookie or local storage | Functional and personalisation | Urbbit | Remembers optional display, navigation, accessibility or workspace choices | Duration displayed by the cookie settings tool or until cleared |
The authentication cookie is configured as HTTP-only so browser scripts cannot
read it. It uses SameSite=Lax to reduce cross-site request risk and is marked
Secure when transmitted through HTTPS. Cookie values and session validity may
expire or be revoked before the browser removes the cookie.
The cookie settings tool is the current operational inventory for optional cookies. It identifies the actual cookie or storage name, provider, purpose and duration for the site version being used. A category appearing in this policy does not mean a particular technology is active.
6. Information associated with cookies
Depending on the cookie and Service, associated information may include:
- a session, token or pseudonymous browser identifier;
- sign-in, sign-out, token refresh and security events;
- the Urbbit domain, organisation or tenant associated with a session;
- consent and privacy choices;
- language, theme, layout and other preferences;
- browser, device, operating system and network information;
- request time, page or API path, referring page and response status; and
- security signals such as failed requests or suspected misuse.
An authentication cookie may represent access rights, but it is not intended to contain Customer Data such as document bodies, network inventory or user passwords. Personalisation storage should contain only the minimum information needed to remember the preference.
Cookie information may be personal information when it identifies, relates to or can reasonably be linked with a person. In that case, the Urbbit Privacy Policy applies.
7. Cookie security
Urbbit uses technical and organisational measures designed to protect cookie information. Depending on the context, these include:
- HTTP-only authentication cookies;
- secure transmission over HTTPS;
- same-site restrictions;
- domain-scoped cookie names;
- token expiry, rotation and revocation;
- access controls and audit records; and
- detection and containment of suspicious sessions.
No method is completely secure. Users must keep their devices and accounts protected, sign out on shared devices and never disclose passwords, one-time codes, session values or authentication cookies.
If a user believes a session or device has been compromised, they should sign
out where possible, change relevant credentials and contact
info@urbbit.com promptly.
8. First-party and third-party services
Core Urbbit authentication cookies are first-party cookies. Some Services may connect to third-party providers selected by Urbbit or a Customer, such as hosting, mapping, media, support, payment or identity providers. A third party may process device or request information and may set its own cookies where its service requires them.
Optional third-party cookies controlled by Urbbit will be identified in the cookie settings tool and used only with any consent required by law. A third-party service enabled and controlled by a Customer may be governed by that Customer's notice and the provider's privacy terms.
9. Managing cookie choices
Where the Services provide a cookie settings tool, users can use it to accept, reject or change optional cookie categories. Withdrawing consent does not make earlier processing unlawful, but it stops the relevant optional technology from future use once the choice is applied.
Users can also use browser or device settings to:
- view stored cookies and site data;
- delete cookies and local storage;
- block all or selected cookies;
- restrict third-party cookies; or
- clear site data when the browser closes.
Browser controls vary. Blocking or deleting strictly necessary cookies may sign the user out, reset privacy choices or prevent protected Services from working. Deleting personalisation storage may reset the user experience to its default settings.
10. Retention
We retain cookie information only for as long as needed for its stated purpose or as required by law. Duration depends on the technology:
- session cookies ordinarily end with the browser session, token expiry, sign-out or revocation;
- security records may be retained separately from the browser cookie for a reasonable period to investigate misuse and protect the Services;
- consent records are retained long enough to respect and demonstrate the user's choice; and
- personalisation records remain for their configured duration or until the user clears them.
Where an exact expiry is configured for an optional cookie, it will be shown in the cookie settings tool.
11. Cloud, APIs and Customer-Hosted Software
This policy applies to cookies controlled by Urbbit in its hosted Services.
API clients that use bearer headers instead of browser cookies may not receive an Urbbit authentication cookie. That does not prevent Urbbit from processing normal API security and request logs under the Privacy Policy.
For Customer-Hosted Software, private cloud or a Customer-branded domain, the Customer controls its hosting environment and may configure additional cookies, identity providers, analytics or integrations. The Customer is responsible for giving notices and obtaining choices for technology it selects or controls. Urbbit remains responsible for cookies and processing that Urbbit independently controls.
12. Children
Urbbit does not use cookies to create advertising profiles of children. Where a Customer uses an Urbbit product in an education or child-related context, the Customer must configure the Service and optional technologies consistently with applicable law, its authority and the Urbbit Privacy Policy.
13. Changes to this policy
We may update this Cookie Policy when our Services, cookie 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.
14. Contact
For questions or requests about cookies or privacy, 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
