Urbbit Privacy Policy
Version 0.1 — Effective 21 August 2026
1. Who we are
Urbbit Pty Ltd, ABN 91 615 735 450, of 3 Turin Place, Keilor Lodge, Victoria 3038, Australia (Urbbit, we, us or our) provides websites, software, cloud services, customer-hosted software, APIs, content and industry platforms.
This Privacy Policy explains how we collect, hold, use and disclose personal information when you:
- visit
urbbit.comor another Urbbit website that links to this policy; - create or use an Urbbit account;
- use Urbbit cloud, API, customer-hosted or hybrid services;
- interact with our blogs, comments, replies, likes, media or community features;
- request support, a demonstration, a quote or professional services;
- subscribe to communications or attend an event;
- act as a supplier, partner, contractor or business contact;
- apply for work with Urbbit; or
- otherwise communicate with us.
Product-specific privacy notices may provide additional information. The
TelBrix Privacy Supplement at https://telco.urbbit.com/legal/privacy
applies to TelBrix and telco.urbbit.com.
2. Scope and privacy roles
2.1 Information Urbbit controls
Urbbit determines why and how personal information is handled for its own business activities, including:
- public website operation;
- direct account and identity administration;
- enquiries, demonstrations and sales;
- contracts, billing and supplier management;
- security, fraud prevention and licence administration;
- direct support relationships;
- marketing preferences and events;
- public blog and community administration;
- recruitment; and
- legal and corporate administration.
For these activities, this policy describes Urbbit's handling of your personal information.
2.2 Customer-controlled data
An organisation using the Services (Customer) may upload or generate personal information about its employees, contractors, students, learners, customers, suppliers, landowners, site contacts or other people (Customer Data).
The Customer normally decides:
- what Customer Data enters the Services;
- why it is processed;
- who may access it;
- how workflows use it; and
- how long it is retained.
For Customer Data, Urbbit generally acts on the Customer's documented instructions as a service provider or processor. The Customer's privacy notice and our contract with that Customer govern that processing. If your request concerns Customer Data, contact the relevant Customer first. We will assist the Customer as required by our Data Processing Addendum (DPA) and applicable law.
2.3 Customer-hosted deployments
Where software runs entirely in a Customer-controlled environment, Urbbit may not receive the personal information stored in that environment. The Customer is responsible for privacy and security within its environment.
Urbbit may receive limited licence, update, diagnostic or support information as described in section 6.4 and the applicable Order. We receive Customer Data for support only when the Customer chooses to provide it or authorises access.
3. Personal information we collect
Depending on your relationship with us, we may collect the following.
3.1 Identity and contact information
- name, display name and username;
- business and, where necessary, personal contact details;
- organisation, position, team and professional details;
- postal or billing address;
- profile image or avatar; and
- communication and marketing preferences.
3.2 Account, authentication and organisation information
- account and party identifiers;
- organisation, tenant, domain and module membership;
- roles, permissions and administrative relationships;
- password hashes, authentication method and multi-factor status;
- session, token, sign-in, sign-out and account recovery events;
- agreement acceptance and policy version;
- invitations and account lifecycle information; and
- security alerts and suspected misuse.
We do not store a readable copy of your password.
3.3 Contract, billing and commercial information
- plan, products, modules, usage entitlement and subscription status;
- quote, Order, contract and statement-of-work information;
- billing contact, invoice and payment status;
- tax and business registration information;
- transaction identifiers and limited payment metadata;
- supplier, partner and procurement information; and
- commercial communications.
Payment card or bank information may be collected directly by a payment provider rather than Urbbit. We receive only information needed to confirm and reconcile payment unless otherwise disclosed.
3.4 Communications and support information
- emails, contact forms, calls, meetings and messages;
- support tickets, troubleshooting steps and attachments;
- product feedback, survey responses and feature requests;
- demonstrations, training and implementation records; and
- recordings or transcripts where participants have been notified.
Please do not provide sensitive or unrelated personal information in a support request. When diagnostic material contains Customer Data, share only what is necessary and use the secure method we specify.
3.5 Website, device and usage information
- IP address and approximate location derived from it;
- browser, operating system, device type and language;
- date, time, requested URL, referrer and response information;
- cookie or similar identifiers;
- website interactions and consent choices;
- application feature interactions and usage counts;
- application, API and gateway logs;
- crash, performance and diagnostic information; and
- licence, instance and environment identifiers.
3.6 Public content and community information
- author name, profile and avatar;
- blog comments, replies, likes and moderation history;
- uploaded images or media;
- content reports; and
- other information you choose to publish.
Public content can be seen, copied or indexed by others. Do not publish personal or confidential information unless you are authorised and intend it to be public.
3.7 Recruitment and workforce information
If you apply for work or provide services to Urbbit, we may collect:
- application, resume, qualifications and work history;
- professional profiles and references;
- interview notes and assessment information;
- work eligibility and identity information;
- compensation expectations; and
- background-check information where lawful, necessary and notified.
A separate recruitment notice may apply.
3.8 Customer Data
The Services are configurable and Customer Data varies by Customer and module. It may include names, business contact details, user-generated content, educational records, work assignments, location or premises information, communications, orders and other information selected by the Customer.
We do not require Customers to enter sensitive information unless the applicable Service, Order and DPA expressly support that use.
4. How we collect personal information
We collect information:
- directly from you when you register, communicate, submit content, purchase or use the Services;
- from the Customer or organisation that creates or administers your account;
- automatically from your browser, device, application, API or customer-hosted instance;
- from service providers such as identity, payment, security, support, communications and analytics providers;
- from integrations that you or the Customer authorises;
- from business partners, event organisers and referral sources;
- from public professional sources where lawful and reasonably expected; and
- from another party to a corporate transaction or legal process.
If we receive personal information we did not request, we assess whether we could lawfully have collected it. If not, we destroy or de-identify it where lawful and reasonable.
You may interact with public website content without identifying yourself where practicable. Some Services require identity because it is impracticable to secure accounts, contracts, support or tenant data anonymously.
5. Why we use personal information
We collect, hold, use and disclose personal information only where reasonably necessary for our functions, to perform a contract, with consent, to comply with law, or for a legitimate business purpose that is not overridden by applicable privacy rights.
| Purpose | Typical information | Why it is necessary |
|---|---|---|
| Provide websites and content | device, log, cookie and preference information | deliver pages, remember choices, measure performance and protect the website |
| Create and administer accounts | identity, contact, authentication, organisation and role information | verify users, provide access, manage permissions and agreements |
| Deliver and support Services | account, usage, communication and Customer-provided diagnostic information | perform contracts, respond to requests, troubleshoot and maintain Services |
| Process Orders and payments | contact, organisation, contract, invoice and payment metadata | quote, contract, bill, reconcile, prevent fraud and meet tax obligations |
| Secure the Services | account, authentication, device, log and usage information | detect, investigate and prevent abuse, incidents and unauthorised access |
| Operate and improve products | usage, performance, diagnostic and feedback information | fix defects, understand use, plan capacity and improve usability |
| Communicate service information | contact, account, plan and incident information | send operational, security, policy, billing and support notices |
| Marketing and events | contact, professional, preference and engagement information | send requested information, administer events and develop business relationships |
| Public and community features | profile, content, reaction and moderation information | publish content, enable participation and enforce community rules |
| Professional Services | contact, project, communication and Customer-provided information | implement, configure, migrate, integrate and train |
| Legal and corporate purposes | contract, communication, account, security and transaction information | keep records, enforce rights, respond to lawful requests and manage transactions |
| Recruitment | application, professional, assessment and eligibility information | evaluate applications and administer recruitment |
Where consent is the basis for an activity, you may withdraw it for the future. Withdrawal does not make earlier lawful processing unlawful.
6. Product and service situations
6.1 When you register or sign in
We use identity, contact, authentication, organisation and agreement-acceptance information to create the account, secure access, select the correct domain and tenant, issue sessions and provide the Services.
An organisation administrator may invite you, allocate roles, see account status and manage your access. Contact that organisation about its account administration decisions.
6.2 When you use cloud Services
We process account and technical information to operate, secure, support and measure the cloud Service. We process Customer Data only to provide the Service, follow Customer instructions, address support or security issues, and comply with law.
We do not sell Customer Data. We do not use Customer Data for behavioural advertising.
6.3 When you use APIs and integrations
API requests may record credentials or credential identifiers, tenant, endpoint, time, status, IP address, device or client information and request metadata. We use this information for authentication, routing, usage measurement, troubleshooting, audit and security.
An integration may send information to or receive information from a third party chosen by you or the Customer. That third party's privacy policy applies to its processing.
6.4 When software is customer-hosted
Unless the Order states otherwise, customer-hosted software may send limited information reasonably required to:
- activate and validate licences;
- measure purchased usage;
- check for or receive updates;
- protect against abuse; and
- provide optional diagnostics or support authorised by the Customer.
Customer-hosted telemetry must not include the substantive content of Customer Data for product analytics. The Order and Documentation must disclose the fields transmitted and whether optional diagnostics can be disabled.
6.5 When you contact us
We use the information you provide to respond, authenticate the requester where needed, resolve the matter, maintain an appropriate record and improve support. We may route the request internally or to an approved provider that helps us deliver support.
6.6 When you participate publicly
Your chosen name, profile, content and reactions may be public. We use moderation information to investigate reports, enforce terms, prevent abuse and maintain community integrity.
You may ask us to delete your public account or content, subject to legal exceptions and the need to preserve the coherence of discussions or records. We may anonymise a contribution instead of deleting an entire discussion.
7. Cookies and similar technology
Our websites may use cookies, local storage, pixels, scripts and similar technologies.
They may be:
- essential, to deliver pages, authenticate users, route sessions, remember security and consent choices, and prevent abuse;
- functional, to remember optional preferences;
- performance and analytics, to understand aggregate use and improve performance; or
- marketing, to measure campaigns or provide relevant communications where permitted.
Non-essential technologies will be used only with the consent required by applicable law. You can change your choices through the cookie settings tool. Blocking essential technology may prevent account or security functions from working.
The cookie settings tool and Cookie Notice must identify the actual providers, purposes, information and durations. We do not activate a technology merely because it is described as a possible category in this policy.
8. Marketing, events and social media
We may send product news, educational content, invitations and offers where you requested them or where otherwise permitted by law. You can unsubscribe using the link in the message or by contacting info@urbbit.com.
We may retain a minimal suppression record so we do not send communications you have declined. Operational, security, billing and legal notices are not marketing and may still be sent where necessary.
If an event is recorded or photographed, we will provide notice and any practicable choice required by law.
Social networks process information under their own privacy policies when you interact with Urbbit pages or social plug-ins.
9. Payments
Payment and invoicing providers may collect identity, contact, billing, payment, IP address, transaction and fraud-prevention information. Some act for Urbbit and others act independently to provide regulated payment, merchant-of-record, tax or fraud services.
We do not store complete payment card details unless expressly disclosed and appropriate controls are in place. The payment interface will identify the provider and link to its privacy information.
10. Who we disclose personal information to
We may disclose personal information to:
- the Customer and its authorised administrators where your account belongs to that Customer;
- Urbbit personnel and contractors who need access and are subject to confidentiality;
- hosting, content delivery, database, storage and backup providers;
- identity, authentication and cybersecurity providers;
- email, communications, support and customer-relationship providers;
- payment, invoicing, accounting and fraud-prevention providers;
- analytics and consent-management providers enabled under section 7;
- professional advisers, auditors and insurers;
- implementation partners and subcontractors supporting the relevant Service;
- third-party integrations authorised by you or the Customer;
- regulators, courts, law enforcement and government bodies where legally required or reasonably necessary to protect rights and safety; and
- a prospective buyer, investor or successor in a genuine corporate transaction, subject to appropriate confidentiality and privacy controls.
We require providers acting for Urbbit to protect information and process it only for authorised purposes. The public Subprocessor List must identify providers that process Customer Data.
We do not sell personal information. We do not share personal information for cross-context behavioural advertising. If our practices change, we will update this policy and provide choices required by law before the change takes effect.
11. Overseas disclosure and data location
Urbbit is based in Australia. Some providers, support personnel, Customers or integrations may process personal information outside Australia.
The countries in which overseas recipients are likely to be located must be identified in Urbbit's current Subprocessor List and relevant collection notice where practicable. Hosting in a selected region does not necessarily mean that support, security, subprocessors or Customer-selected integrations are limited to that region unless an Order or DPA expressly says so.
Before disclosing personal information overseas, we take reasonable steps required by applicable law. Depending on the law and transfer, safeguards may include:
- due diligence and contractual privacy and security obligations;
- data-processing agreements;
- access controls, encryption and data minimisation;
- approved standard contractual clauses or another valid transfer mechanism; and
- Customer instructions and data-residency commitments.
Customers are responsible for overseas disclosures they direct through users, configuration and integrations.
12. How long we retain information
We retain personal information only as long as reasonably necessary for the purpose collected, a related lawful purpose, contractual commitments, dispute resolution or legal requirements.
We consider:
- the nature, amount and sensitivity of the information;
- the risk of harm from unauthorised use or disclosure;
- the reason for processing and whether it can be achieved another way;
- account, subscription and support lifecycles;
- security, fraud and audit requirements;
- tax, corporate, employment and limitation periods;
- Customer instructions and the DPA; and
- legal holds and regulator directions.
Typical treatment includes:
- account information for the account or contract lifecycle and a reasonable period afterwards;
- invoice and transaction records for legally required financial periods;
- security logs for the period needed to detect, investigate and evidence incidents;
- marketing information until you unsubscribe or it is no longer useful, with a suppression record retained where necessary;
- support information while the matter and related contractual or legal needs remain current;
- unsuccessful recruitment information for the notified recruitment period;
- public content until removed, anonymised or the relevant service closes; and
- Customer Data according to Customer instructions, the Order and DPA.
When no longer required, information is deleted or de-identified. Copies may remain temporarily in protected backups until overwritten through normal cycles. De-identified information that can no longer reasonably identify an individual may be retained and used.
13. Security and data breaches
We use technical, organisational and physical safeguards appropriate to the nature of the information and Services. These may include:
- identity and access controls;
- encryption in transit and, where appropriate, at rest;
- tenant and environment separation;
- logging, monitoring and vulnerability management;
- secure development and change controls;
- backups and recovery processes;
- personnel confidentiality and access governance;
- provider risk management; and
- incident response procedures.
No system is completely secure. You must protect credentials, devices, permissions and integrations and promptly report suspected unauthorised access.
We assess suspected breaches and take reasonable containment, remediation and notification steps. Where the Australian Notifiable Data Breaches scheme applies, Urbbit will notify affected individuals and the Office of the Australian Information Commissioner (OAIC) when required. For Customer Data, we notify and assist the Customer under the DPA, and the Customer generally handles notifications for its affected individuals unless law requires otherwise.
14. Children, students and education data
The general Urbbit website and direct self-service business accounts are not directed to children under 16. We do not knowingly invite a child under 16 to create an independent business account. A parent or guardian who believes a child has done so may contact us.
An education institution or other Customer may use a supported Service to process student or child-related Customer Data. In that case:
- the Customer decides the educational purpose and lawful basis;
- the Customer must provide notices and obtain consent where required;
- Urbbit processes the data only to provide and support the Service, follow Customer instructions and comply with law;
- Urbbit does not sell the data or use it for behavioural advertising; and
- rights requests should normally be directed to the Customer.
The Order and DPA must identify any additional safeguards required for children, education records or sensitive information.
15. Artificial intelligence and automated decisions
Unless a Customer expressly opts in under disclosed terms, Urbbit does not use Customer Data or personal information collected under this policy to train a general-purpose or shared artificial-intelligence or machine-learning model.
We may use automated tools for security, spam prevention, routing, support and product functions. We do not make a decision about you based solely on automated processing that produces legal or similarly significant effects unless:
- the activity is lawful and clearly disclosed;
- an applicable contract permits it;
- appropriate safeguards and human review are available; and
- any required consent has been obtained.
Customer-configured workflows and decisions are controlled by the Customer. Contact the Customer about how it uses Customer Data and automated features.
16. Access, correction and other privacy rights
You may ask Urbbit to:
- confirm whether we hold personal information about you;
- provide access to personal information we control;
- correct information that is inaccurate, out of date, incomplete, irrelevant or misleading;
- delete or de-identify information where applicable;
- withdraw consent for future processing;
- stop direct marketing;
- provide information about relevant overseas disclosures; or
- exercise another right available under applicable law, such as objection, restriction or portability.
Email info@urbbit.com with the subject Privacy Request and explain the request. We may ask for information reasonably necessary to verify identity and authority. Do not send unnecessary identity documents by ordinary email.
We will respond within a reasonable period, generally no more than 30 calendar days for Australian access and correction requests. If we cannot fulfil a request, we will explain why where required and describe available complaint options. We do not charge for making a request. A permitted reasonable charge may apply to providing access, but not to correcting information.
If the information is Customer Data, identify the Customer. We may refer the request to that Customer because it controls the data.
17. Privacy questions and complaints
Send privacy questions or complaints to:
- email: info@urbbit.com, subject Privacy Complaint;
- phone: +61 481 133 021; or
- post: Privacy Officer, Urbbit Pty Ltd, 3 Turin Place, Keilor Lodge, Victoria 3038, Australia.
Please describe:
- your name and contact details;
- the account, organisation or reference involved;
- what happened and when;
- why you believe your privacy was affected; and
- the outcome you seek.
We will acknowledge the complaint, investigate it fairly and aim to provide a written response within 30 calendar days. If more time is reasonably required, we will explain why and provide an expected timeframe.
If you are not satisfied with our response, or we do not respond within a reasonable period, you may complain to the OAIC:
- website:
https://www.oaic.gov.au/privacy/privacy-complaints; - phone: 1300 363 992; or
- post: GPO Box 5288, Sydney NSW 2001, Australia.
Another regulator or approved external dispute-resolution scheme may apply depending on the organisation and subject matter.
18. Third-party links
Our websites and Services may link to or integrate with third-party websites, social networks, applications and APIs. Their privacy practices are controlled by them. Review their privacy information before providing data or authorising an integration.
19. Business transfers and legal requirements
We may use or disclose personal information as reasonably necessary for a merger, financing, restructure, acquisition or sale. We will apply appropriate confidentiality and privacy protections and notify affected people where required.
We may preserve or disclose information to comply with a lawful request, investigate suspected wrongdoing, enforce agreements, establish or defend legal claims, or protect the rights, security and safety of Urbbit, Customers, users or the public.
Where legally permitted and appropriate, we will notify the affected Customer or individual before disclosing information to a government authority and limit disclosure to what is required.
20. Changes to this policy
We may update this policy when our products, providers, practices or legal obligations change. The version and effective date appear at the top.
For a material change, we will provide reasonable notice through the website, account or email where appropriate. If consent is required for a new use, we will seek it before that use begins.
Archived versions will be available from Urbbit on request and may also be published in the legal section of the Urbbit website.
21. 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
