Privacy Policy

1. About this Privacy Policy

1.1 This Privacy Policy explains how Tradie View Pty Ltd (“TradieView”, “we”, “us” or “our”) collects, uses, discloses, stores and otherwise handles personal information in connection with TradieView, our website, software platform, mobile applications, support services, onboarding, communications, integrations, artificial intelligence features and related services.

1.2 We are committed to managing personal information in accordance with applicable privacy law, including the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs) where they apply.

1.3 This Privacy Policy applies to customers, account owners, administrators, users, employees, contractors, subcontractors, suppliers, clients, website visitors and people who contact us.

1.4 We take reasonable technical, organisational and administrative measures designed to protect personal information and Customer Data.

1.5 This Privacy Policy should be read together with our Terms & Conditions, Acceptable Use Policy, Product Privacy Notice (if any), Cookie & Tracking Notice, Sub-Processor List and any applicable Data Processing Addendum.

1A. Definitions

1A.1 In this Privacy Policy, unless the context requires otherwise:

• (a) “Platform” means the TradieView website, software platform, mobile applications, APIs and related services described in Section 1.1.
• (b) “Customer Data” means personal information and business information submitted, uploaded, generated or stored within a customer’s TradieView workspace (including the categories described in Section 4), but excluding information TradieView holds independently in its capacity as a business (such as its own billing, marketing and support records).
• (c) “Google User Data” means information received from a Google API in connection with a Google integration described in Section 19, including Gmail, Google Calendar, Google Search Console, Google Analytics and Google Business Profile data.
• (d) “Meta Platform Data” means information received from Meta Platforms, Inc. APIs in connection with a connected Facebook Page or Instagram Business account, as described in Section 18.
• (e) “Business customer” means an organisation or individual that holds a TradieView subscription and controls the content of its own workspace.
• (f) “Sub-processor” means a third-party provider engaged by TradieView to process personal information on TradieView’s behalf, as listed in the Sub-Processor and Third-Party Provider List referenced in Section 11.3.
• (g) “Applicable privacy law” means the Privacy Act 1988 (Cth) and the Australian Privacy Principles and, where TradieView processes personal information of an individual located in another jurisdiction, any privacy or data-protection law of that jurisdiction that applies to the processing.

2. Who We Are

2.1 TradieView is operated by Tradie View Pty Ltd, ABN 41 687 743 022, ACN 687 743 022.

2.2 Registered address: Unit 8, 33–43 Meakin Road, Meadowbrook QLD 4131, Australia.

2.3 Privacy, data protection, security incident and deletion requests: support@tradieview.com.

3. Customer Data and Our Role

3.1 TradieView is a business and construction operating platform. Customers may use TradieView to manage projects, jobs, employees, contractors, subcontractors, suppliers, customers, communications, documents, invoices, receipts, calendars, bookings, websites, accounting, safety records, compliance information, files, photographs and other operational information.

3.2 Business customers generally determine what information is entered into their TradieView workspace and act as the controller of that Customer Data.

3.3 Where TradieView processes personal information on behalf of a business customer, we act as a processor (or equivalent). The business customer remains responsible for having the appropriate authority, notices and permissions to collect and use that information under applicable privacy law (and, where the individual is located outside Australia and another privacy law applies, any required legal basis under that law).

3.4 If a person makes a privacy request relating to information controlled by one of our business customers, TradieView may refer or coordinate the request with that customer.

4. Personal Information We Collect

Depending on the services used, we may collect or process the following categories of personal information:

• Account and identity information — name, business name, email address, telephone number, address, job title, role, account identifier, username, profile information, authentication status, multi-factor authentication (MFA) settings, account permissions and connected account information.
• Business and operational information — project and job information, client details, employee and subcontractor information, supplier information, job-site addresses, quotations, purchase orders, invoices, receipts, timesheets, scheduling, bookings, calendar events, forms, reports, site diaries, safety and compliance documents, photographs, videos, drawings, plans, files, correspondence and other business records.
• Communications — emails, email metadata, email attachments, SMS, chat messages, support communications, correspondence and communications imported from authorised integrations.
• Billing information — subscription details, billing contact information, invoices, transaction references, payment status and subscription history. Full payment-card numbers are processed by third-party payment providers and are not stored by TradieView.
• Device and technical information — IP address, device identifiers, browser type, operating system, session information, login records, telemetry, crash logs, API activity, security events, performance data and other technical diagnostics.
• Location information — job-site addresses, maps, route information, workforce attendance locations, device location information and time/location data associated with work activity (where location features are enabled by the customer or user).
• Sensitive information — TradieView does not intentionally require sensitive information for ordinary Platform use. Customers must not upload sensitive information unless they have a lawful basis and appropriate consent or authority under applicable privacy law.

4A. Minors and Age of Use

4A.1 TradieView accounts may only be created by individuals aged 18 or over, acting on behalf of a business.

4A.2 Business customers may upload personal information about individuals under 18 (for example, apprentices or junior employees) as part of their own employee or contractor records. Business customers are solely responsible for ensuring they have appropriate authority to do so, including any consent required from a parent or guardian where applicable under law.

4A.3 TradieView does not knowingly collect personal information directly from individuals under 18 through the Platform’s own account-creation or marketing channels.

4B. Employee Records

4B.1 Where a business customer uploads employee records into TradieView, any employee records exemption under the Privacy Act 1988 (Cth) (where applicable) is a matter between the business customer and its own employees. That exemption does not, of itself, exempt TradieView from its own obligations as a handler of that information under applicable privacy law or under this Privacy Policy.

4B.2 Business customers remain responsible for their own compliance with the Privacy Act 1988 (Cth), the Fair Work Act 2009 (Cth), and any applicable state or territory employment and privacy laws in relation to employee records they upload to the Platform.

5. How We Collect Information

We may collect personal information:

• directly from users when an account is created, a subscription is purchased, or information is entered into TradieView;
• through file uploads, forms, surveys, support interactions and onboarding;
• from customer administrators and authorised users;
• through cookies, local storage, analytics, application logs, security systems and telemetry;
• via APIs and integrations that have been expressly enabled by an authorised customer or user; and
• from publicly available sources or third parties where permitted by law.

6. How We Use Information

We may use personal information to:

• provide, operate, maintain and improve the Platform;
• create and manage user accounts, authenticate users and maintain permissions;
• deliver customer-requested functionality (including jobs, projects, communications, documents, invoicing, booking, calendar, accounting, website and SEO features);
• enable authorised integrations;
• provide AI-assisted functionality;
• process subscriptions and payments;
• provide support, onboarding and service communications;
• protect the security and integrity of the Platform, detect and prevent misuse, fraud and security incidents;
• troubleshoot issues and improve product reliability and performance;
• comply with legal obligations, enforce our agreements and protect our rights and those of our customers; and
• for other purposes notified at the time of collection or otherwise permitted by law.

7. Artificial Intelligence Features

7.1 TradieView includes artificial-intelligence and automated-assistance functionality. Depending on the selected feature, AI may be used to extract information from documents, recognise invoices and receipts, categorise documents, detect duplicates, match documents to jobs or projects, summarise communications, draft email responses, search information, generate content, analyse business information, assist with scheduling, analyse website information, provide estimates or recommendations, and support other user-requested Platform functionality.

7.2 AI outputs may contain inaccuracies or incomplete information. Users remain solely responsible for reviewing all AI-generated outputs before making material business, contractual, employment, financial, compliance, safety or other decisions.

7.3 Unless expressly disclosed otherwise, AI functionality is intended to assist human decision-making and does not replace appropriate human judgement.

7.4 TradieView does not use identifiable Customer Data to train a shared or general-purpose TradieView AI model for the benefit of unrelated customers unless an appropriate express opt-in arrangement exists and the use is lawful.

7.5 Additional restrictions apply to Google Workspace API data (see Section 19).

8. Payments and Billing

8.1 Subscription payments are processed by approved third-party payment providers (including Stripe where enabled).

8.2 TradieView does not store full payment-card numbers. Card credentials are managed by the payment provider.

8.3 We may retain invoices, transaction references, billing contact information, subscription history, payment status and limited payment metadata for accounting, taxation, support, audit and legal purposes.

9. Cookies and Analytics

9.1 TradieView may use cookies, local storage, analytics services, telemetry and similar technologies to operate the Platform, authenticate sessions, maintain preferences, measure performance, improve reliability, understand feature usage, identify errors and protect security.

9.2 IP addresses, device identifiers and usage information may constitute personal information where they can reasonably identify an individual.

9.3 Further details are set out in the TradieView Cookie & Tracking Notice.

10. Location Information

10.1 TradieView may process job-site addresses, maps, route information, attendance information, device location and other location information where the customer has enabled location-related functionality.

10.2 Precise device location depends on device permissions, browser permissions, user permissions, application settings and customer configuration.

10.3 Customers remain solely responsible for providing any required workplace notices, employee notices and complying with applicable privacy, surveillance, employment and industrial-relations obligations associated with their use of location features.

11. Overseas Processing and Disclosure

11.1 TradieView uses third-party providers and sub-processors for hosting, infrastructure, security, storage, payments, communications, analytics, identity, artificial intelligence, integrations and other Platform functionality. Providers may include (depending on enabled functionality) Stripe, SendGrid, Twilio, OpenAI, Anthropic, Google, Firebase, cloud hosting and database providers, monitoring providers, security providers and other providers identified in our Sub-Processor List.

11.2 Providers and authorised sub-processors may process, store or access information outside Australia. Processing locations may include Australia, the United States, the United Kingdom, the European Union, Singapore, New Zealand and other jurisdictions used by approved providers.

11.3 The current list of material service providers is maintained at https://tradieview.com/legal/sub-processors and should be treated as the operational source of truth.

11.4 Before authorising a material new provider to process Customer Data or Google User Data, we assess (where appropriate) purpose, categories of data, processing location, privacy terms, security, confidentiality, retention, sub-processors, AI training practices and applicable Google Limited Use requirements.

11.5 Before disclosing personal information to an overseas recipient, TradieView takes reasonable steps to ensure the overseas recipient does not breach the Australian Privacy Principles in relation to that information. These steps include contractual data-protection terms with providers and sub-processors and assessment of provider privacy and security practices as described in Section 11.4. Where TradieView is not reasonably able to take such steps in relation to a particular disclosure, we will only make that disclosure where an exception under APP 8.2 applies or with the individual’s informed consent.

12. Security

12.1 We take reasonable technical and organisational measures designed to protect personal information and Customer Data against misuse, interference, loss, unauthorised access, unauthorised modification and unauthorised disclosure.

12.2 Production controls include (where applicable): TLS/HTTPS encryption in transit; encryption at rest for production data stores containing Customer Data and Google User Data; multi-factor authentication; access controls and role-based permissions; restricted administrative and personnel access; secure credential handling; logging and monitoring (including suspicious-activity monitoring); infrastructure protection; backup and recovery controls; and contractual security requirements for providers.

12.3 OAuth access tokens, refresh tokens, API credentials and integration credentials are security-sensitive. They must not be exposed in normal user interfaces, placed in browser or application logs, sent through analytics systems, visible to unrelated customers, or unnecessarily accessible to personnel.

12.4 Google User Data receives protection at least comparable to other sensitive Customer Data processed by TradieView.

12.5 Staff access to Customer Data is restricted to legitimate requirements such as support, troubleshooting, security, maintenance, incident response or legal compliance.

12.6 Security controls are periodically reviewed as infrastructure, integrations and threats evolve.

12.7 No internet-connected system can guarantee absolute security.

12.8 Security incidents should be reported promptly to support@tradieview.com.

13. General Data Retention

13.1 We retain personal information only for as long as reasonably necessary to provide the service, deliver customer-requested functionality, comply with law, maintain security, maintain accounting and taxation records, resolve disputes and enforce agreements.

13.1A Without limiting Section 13.1, indicative retention periods are set out below. These are default periods only; a business customer’s own data-handling instructions, legal holds or applicable law may require a different period in a specific case.

13.2 Following account termination, Customer Data may remain available for up to 30 days for authorised export or account closure (subject to payment of outstanding fees and technical limitations).

13.3 After the applicable retention period, Customer Data may be deleted, de-identified, archived where legally required, or otherwise processed in accordance with applicable retention requirements.

13.4 Backups may continue to contain deleted information temporarily until overwritten or deleted through normal backup-retention cycles.

14. Access, Correction, Deletion and Export

14.1 Individuals may request access to personal information we hold about them.

14.2 Individuals may request correction of inaccurate or outdated information.

14.3 Individuals may request deletion where applicable. Requests can be sent to support@tradieview.com.

14.4 We may verify identity and authority before processing a request.

14.5 Where information is controlled by a TradieView business customer, we may refer the individual to the relevant customer or coordinate the request with that customer.

14.6 Requests may be limited where permitted by law, including where disclosure would compromise another individual’s privacy, confidentiality, security, legal obligations or legitimate record-keeping requirements.

14.7 Business customers may export their own Customer Data from an active workspace at any time using the Platform’s built-in export functionality, or by contacting support@tradieview.com. This right of export is separate from, and available in addition to, the 30-day post-termination export period described in Section 13.2.

15. Data Breaches

15.1 Where TradieView becomes aware of a suspected data breach, we will carry out a reasonable and expeditious assessment of whether the breach is likely to result in serious harm, and will take reasonable steps to assess, contain and remediate suspected or actual data breaches as soon as practicable.

15.2 Where an assessment concludes that an eligible data breach has occurred under the Notifiable Data Breaches scheme, or notification is otherwise required under applicable law, we will notify affected individuals, relevant business customers and the Office of the Australian Information Commissioner as soon as practicable, and in any event within the timeframes required by applicable law.

15.3 Customers must promptly notify us if they suspect unauthorised access to their Account, credentials, integrations, devices or Customer Data.

16. Marketing

16.1 We may send marketing communications where permitted by applicable law.

16.2 Users can unsubscribe from marketing communications at any time.

16.3 Marketing opt-out does not prevent necessary security alerts, billing notices, service messages, account notices, legal notices or transactional communications.

16.4 Google Workspace API user data is not used for personalised or targeted advertising.

17. Third-Party Services

17.1 TradieView may integrate with third-party applications and services.

17.2 Third-party integrations are normally initiated or authorised by the customer or user.

17.3 Third parties process information under their own privacy policies and legal terms.

17.4 We seek only the permissions reasonably required to provide the selected integration.

18. Meta Platform — Data Deletion

18.1 If you have connected your Facebook Page or Instagram Business account to TradieView, you may delete the Meta Platform Data we hold about you in any of the following ways:

• Self-service in-app: Log into TradieView → Settings → Social Hub → Disconnect platform. We will immediately soft-delete the connection, encrypted access token and any cached Page / Instagram metadata, and use best efforts to revoke the token at Meta.
• Email request: Email support@tradieview.com with the words “Meta data deletion”. We will action the request within 30 days in accordance with the Australian Privacy Act.
• Meta-initiated: When you remove the TradieView app from your Facebook account (facebook.com/settings → Business Integrations), Meta notifies us via the Deauthorize and Data Deletion callbacks. We complete deletion within 30 days and respond with a confirmation code that can be verified at the public status URL we return.

18.2 Once deleted, Meta Platform Data is removed from our active database and associated storage within 30 days. Encrypted backups are overwritten on the regular backup-retention cycle (maximum 30 days).

19. Google API Services and Google User Data

19.1 Limited Use Commitment

TradieView’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

“TradieView’s use of information received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.”

19.2 Google Connections Are Optional

Google integrations are optional. Users choose which Google services to connect. Supported integrations may include Gmail, Google Calendar, Google Drive, Google Search Console, Google Analytics, Google Business Profile and Google authentication. Integrations are independent where supported. We request permissions only when the user activates the corresponding integration.

19.3 Google Identity

When a user uses Google authentication or connects a Google account, we may receive Google account ID, name, email address, profile information and authentication status. This information is used only for authentication, identifying the connected account and providing authorised Google functionality.

19.4 Gmail

We request the Gmail modification scope https://www.googleapis.com/auth/gmail.modify to provide the two-way Unified Inbox. This permits the authorised user to view messages and attachments, compose and send email, reply, mark messages read/unread, archive, star/unstar, apply supported mailbox state changes and move messages to Gmail Trash. These actions are synchronised with the connected Gmail mailbox.

We do not request permission to permanently delete Gmail messages while bypassing Trash, nor do we request the broad https://mail.google.com/ scope. All Gmail actions are user-facing and performed at the direction of the authorised user.

Gmail information may be used for Unified Inbox display, business communications, email search, user-requested summaries, email triage, attachment handling, invoice and receipt recognition, AI document workflows, document classification, duplicate detection, client/job/project matching and AI-assisted draft replies requested by the user.

We prohibit use of Gmail functionality for email warming, prohibited cold-email systems, unlawful unsolicited bulk email, bypassing Gmail restrictions or other prohibited purposes.

19.5 Google Calendar

We may access authorised Google Calendar event information for bookings, appointments, scheduling and calendar synchronisation (event title, date, time, description, location, attendees and related information).

We request only https://www.googleapis.com/auth/calendar.calendarlist.readonly and https://www.googleapis.com/auth/calendar.events. We do not request scopes that allow management of calendar sharing permissions, access-control lists, or creation/deletion of entire calendars. We respect the access role Google reports for each calendar.

19.6 Google Search Console

Where connected, we may access authorised Search Console data (clicks, impressions, search queries, pages, positions and related SEO metrics) solely to provide website and SEO reporting to the authorised customer.

19.7 Google Analytics

Where connected, we may access authorised Google Analytics data (users, sessions, traffic, page performance, engagement metrics and other authorised GA4 information) solely for the user-facing Analytics and website-performance functionality inside TradieView.

19.8 Google Business Profile

Where connected, we may access authorised Google Business Profile account details, location information, business information, reviews, review responses and other supported business-management data. Changes occur only when initiated or specifically authorised by the user.

19.9 Google Drive

Where connected, TradieView uses the least-privilege scope https://www.googleapis.com/auth/drive.file to save documents that TradieView itself generates — such as quotes, invoices, job sheets, tender bid-packs and related PDFs — into a dedicated “TradieView” folder in the authorised user’s Google Drive. This scope only permits access to files created by TradieView; we cannot see, open, download or manage any other files in your Drive. We use this access solely to store and retrieve the business documents you choose to save to Drive.

19.10 Prohibited Use of Google User Data

We do not use raw, derived, aggregated or anonymised Google Workspace API user data for targeted or personalised advertising, advertising profiling or eligibility, data brokerage, information resale, lending, creditworthiness or credit decisions, unrelated commercial profiling, or unrelated product monetisation. We do not sell Google User Data.

General rights relating to aggregated or anonymised information elsewhere in this Privacy Policy do not override Google’s Limited Use requirements. Where Google’s policy is stricter, the stricter requirement applies.

19.11 Google Data + AI / Machine Learning

We may use AI for user-facing features such as email triage, summaries, draft replies, attachment processing, invoice/receipt extraction, document classification, job/project/client matching and other user-requested functionality. However:

• We do not use raw or derived Google Workspace API user data to train, develop or improve shared or general-purpose AI or machine-learning models.
• Google Workspace API user data is not transferred to an AI/ML provider if that provider will use the data to train or improve its shared/general-purpose models.
• Where Google Workspace API data is processed by a third-party AI provider, we use the provider’s commercial/API product and ensure applicable terms/settings do not permit the content to be used for general/shared model training.
• We do not voluntarily opt Google Workspace API data into model-training, development-partner, data-sharing or human-review programs unrelated to the requested user feature.
• Processing occurs only to provide the specific user-facing functionality requested by the authorised user.
• If these protections cannot be confirmed, we do not send Google Workspace API user data to that provider (this restriction is enforced technically).

19.12 Human Access to Google Data

Personnel do not read Google User Data except where reasonably necessary and permitted (for example, affirmative user consent for support, troubleshooting, security or abuse investigation, operating the user-requested service, legal requirements, or another use expressly permitted by applicable Google policy). Access is restricted by role and legitimate need.

19.13 Transfer of Google User Data

Google User Data may only be transferred to service providers when necessary to provide or secure the user-facing feature, permitted by Google policy, and subject to appropriate confidentiality, security and AI/ML restrictions. We do not transfer Google User Data to advertisers, advertising networks, data brokers, information resellers or unrelated organisations seeking to monetise the information.

19.14 Security of Google User Data

Google User Data is protected using TLS/HTTPS encryption in transit, encryption at rest (where stored in production data stores), authentication controls, role-based access, restricted personnel access, logging, monitoring, secure OAuth token storage and other reasonable production security controls. OAuth tokens and refresh tokens must never appear in general application logs.

19.15 Google Integration Disconnection

When a user disconnects a Google integration we immediately: mark the connection as disconnected; stop all future API requests and scheduled synchronisation jobs associated with that authorisation; delete stored Google access and refresh tokens from active production storage; revoke the Google OAuth grant/token where supported; invalidate related cached authentication state; delete temporary Google API cache data that is no longer required; remove active integration sessions; and log the disconnection.

Disconnect audit logs never contain Google access tokens, refresh tokens, passwords, full email content or confidential Google API payloads.

19.16 Retained Customer Business Records

Disconnecting Google does not automatically destroy business records deliberately saved into TradieView by the customer. For example, an approved invoice that has been matched to a Job and saved into Accounts remains Customer Data. The same principle applies to receipts, attachments, documents, approved communication records and other files intentionally saved into the TradieView workspace. On disconnection we revoke access, delete OAuth credentials, stop future sync and delete unnecessary cache, but do not delete the saved business records.

19.17 Google Data Deletion Requests

Users can request deletion of eligible Google-derived information in-app (Settings → Privacy & Data → Request Google Data Deletion) or by emailing support@tradieview.com.

Where appropriate we will verify identity and authority, delete eligible information, record the request and confirm completion. Information may be retained only where legally required or reasonably necessary for limited purposes such as taxation, accounting, security, fraud prevention, legal disputes, legal holds or regulatory obligations, and will not be used for unrelated purposes.

20. Aggregated and De-identified Information

We may use aggregated or de-identified Platform information for service analytics, performance, reliability, security, product development, capacity planning, internal business analysis and industry insights, provided customers and individuals are not reasonably identifiable.

This section does not override Google’s Limited Use requirements. Google Workspace API user data (including derived, aggregated or anonymised data) remains subject to applicable Google restrictions.

21. Automated and AI-Assisted Decision-Making

21.1 We may use AI or rules-based systems to produce recommendations, alerts, classifications, summaries, risk indicators, workflow suggestions, document categorisation, scheduling suggestions and other assistance.

21.2 Unless specifically disclosed otherwise, these tools assist users rather than independently making decisions that have legal or similarly significant effects on individuals.

21.3 Examples include invoice classification, receipt recognition, duplicate detection, job matching, workflow priority, AI-generated replies, business-health indicators and suggested schedules.

21.4 Where new automated systems are introduced that may significantly affect an individual’s rights or interests, we will update this Privacy Policy and product disclosure where required.

22. Complaints

Privacy complaints should be sent to support@tradieview.com. We will investigate and respond within a reasonable period. If you are not satisfied with our response you may contact the Office of the Australian Information Commissioner (OAIC).

23. Changes to this Privacy Policy

23.1 We may update this Privacy Policy from time to time to reflect product changes, new integrations, new AI functionality, provider changes, legal or security requirements, or other necessary updates.

23.2 The current version will remain publicly available at https://tradieview.com/legal/privacy-policy.

23.3 Material changes will be communicated to customers where appropriate.

23.4 If the way Google User Data is used changes materially, we will determine whether additional disclosure, updated OAuth consent, new Google verification or further user permission is required before deploying the change.

24. Contact

Tradie View Pty Ltd
ABN 41 687 743 022 · ACN 687 743 022
Unit 8, 33–43 Meakin Road, Meadowbrook QLD 4131, Australia
Privacy / Data / Google API / Meta / Deletion Requests: support@tradieview.com

© 2026 Tradie View Pty Ltd. All rights reserved.

These documents are governed by the laws of Queensland, Australia.