Tradie View Pty Ltd
ABN 41 687 743 022 · ACN 687 743 022
Unit 8, 33–43 Meakin Road, Meadowbrook QLD 4131, Australia
Privacy contact: support@tradieview.com
Version 3.1 — August 2026
Last updated: 17 August 2026
1. About this Privacy Policy
1.1 This Privacy Policy explains how Tradie View Pty Ltd 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 Australian Privacy Principles where applicable.
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.
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 and security contact: 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; email; documents; invoices; receipts; calendars; bookings; websites; accounting; safety records; compliance information; files; photographs; business records; and other operational information.
3.2 Business customers generally determine what information is entered into their TradieView workspace.
3.3 Where TradieView processes personal information on behalf of a business customer, the business customer remains responsible for having the appropriate authority, notices, permissions and lawful basis to collect and use that information.
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:
Account and identity information — including: name; business name; email; telephone number; address; job title; role; account identifier; username; profile information; authentication status; MFA settings; account permissions; and connected account information.
Business and operational information — including: project information; job information; client details; employee information; subcontractor information; supplier information; job-site addresses; quotations; purchase orders; invoices; receipts; timesheets; scheduling; bookings; calendar events; forms; reports; site diaries; safety documents; compliance documents; photographs; videos; drawings; plans; files; correspondence; and other business records.
Communications — including: emails; email metadata; email attachments; SMS; chat communications; support communications; correspondence; and communications imported from authorised integrations.
Billing information — including: subscription information; billing details; invoices; transaction references; payment status; and subscription history. Payment-card information may be processed directly by payment providers rather than stored by TradieView.
Device and technical information — including: IP address; device identifiers; browser; operating system; session information; login records; telemetry; crash logs; API activity; security events; performance information; and other technical diagnostics.
Location information — depending on enabled functionality, TradieView may process: job-site addresses; maps; route information; workforce attendance locations; device location information; and time/location information associated with work activity.
Sensitive information — TradieView does not intentionally require sensitive information for ordinary Platform use. Customers should not upload sensitive information unless they have appropriate authority, consent or another lawful basis.
5. How We Collect Information
Information may be collected: directly from users; when an account is created; when a subscription is purchased; when information is entered into TradieView; through file uploads; during support; during onboarding; through forms; through surveys; through customer administrators; through cookies; through analytics; through application logs; through security systems; through APIs; and through integrations expressly enabled by an authorised customer or user.
6. How We Use Information
TradieView may use information to: provide the Platform; operate user accounts; authenticate users; maintain permissions; provide customer-requested functionality; manage jobs and projects; provide communications functionality; process business documents; enable integrations; provide booking and calendar functionality; provide accounting and invoicing features; provide website and SEO functionality; provide AI-assisted functionality; provide support; provide onboarding; process subscriptions; provide service communications; protect security; identify misuse; troubleshoot issues; improve product reliability; comply with law; enforce agreements; and protect TradieView and its customers.
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; provide recommendations; and support other user-requested Platform functionality.
7.2 AI outputs may contain inaccuracies or incomplete information. Users remain responsible for reviewing outputs before making material business, contractual, employment, financial, compliance, safety or other decisions.
7.3 Unless expressly disclosed otherwise, AI functionality assists human decision-making rather than replacing appropriate human judgement.
7.4 TradieView does not use identifiable Customer Data to train a shared or general-purpose TradieView AI model for 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 as described in section 19 below.
8. Payments and Billing
8.1 Subscription payments may be processed by approved third-party payment providers, including Stripe where enabled.
8.2 TradieView does not intend to store full payment-card numbers when payment credentials can instead be managed by the payment provider.
8.3 TradieView 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 Additional details may be contained 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 responsible for workplace notices, employee notices and 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 functionality enabled: 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; United States; United Kingdom; European Union; Singapore; New Zealand; and other jurisdictions used by approved providers.
11.3 Because service-provider infrastructure and sub-processors can change over time, TradieView maintains a separate Sub-Processor and Third-Party Provider List at https://tradieview.com/legal/sub-processors. This must be treated as the operational source for material service providers.
11.4 Before a material new provider is authorised to process Customer Data or Google User Data, TradieView should assess, where appropriate: purpose; categories of data; processing location; privacy terms; security; confidentiality; retention; sub-processors; AI training practices; and Google Limited Use requirements.
11.5 Where required, TradieView will take reasonable steps under applicable Australian privacy law concerning overseas disclosures.
12. Security
12.1 TradieView takes 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; role-based permissions; restricted administrative access; restricted personnel access; secure credential handling; logs; monitoring; suspicious-activity monitoring; infrastructure protection; backup and recovery controls; and security requirements for providers.
12.3 OAuth access tokens, refresh tokens, API credentials and integration credentials are security-sensitive information. They must not be: exposed in normal user interfaces; placed in browser logs; placed in application logs; sent through analytics systems; visible to unrelated customers; or unnecessarily accessible to personnel.
12.4 Google User Data must receive protection at least comparable to other sensitive Customer Data processed by TradieView.
12.5 Staff access to Customer Data must be restricted to legitimate requirements such as: support; troubleshooting; security; maintenance; incident response; or legal compliance.
12.6 Security controls should be periodically reviewed as infrastructure, integrations and threats change.
12.7 No internet-connected system can guarantee absolute security.
12.8 Security incidents should be reported to support@tradieview.com.
13. General Data Retention
13.1 TradieView retains personal information only for as long as reasonably necessary to: provide the service; provide customer-requested functionality; comply with law; maintain security; maintain accounting and taxation records; resolve disputes; and enforce agreements.
13.2 Following account termination, Customer Data may remain available for up to 30 days for authorised export or account closure.
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 and Deletion
14.1 Individuals may request access to personal information TradieView holds 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 TradieView may verify identity before processing a request.
14.5 Where information is controlled by a TradieView business customer, TradieView 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.
15. Data Breaches
15.1 TradieView will take reasonable steps to assess, contain and remediate suspected or actual data breaches.
15.2 Where required under the Australian Notifiable Data Breaches scheme or another applicable law, TradieView will notify relevant: individuals; business customers; regulators; and/or the Office of the Australian Information Commissioner.
15.3 Customers must promptly notify TradieView if they suspect unauthorised access to: their Account; credentials; integrations; devices; or Customer Data.
16. Marketing
16.1 TradieView may send marketing communications where permitted by applicable law.
16.2 Users can unsubscribe from marketing communications.
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 may process information under their own privacy policies and legal terms.
17.4 TradieView will seek only the permissions reasonably required to provide the selected integration.
18. Meta Platform — Data Deletion (App Review Disclosure)
18.1 If you have connected your Facebook Page or Instagram Business account to TradieView, you have three ways to delete the Meta Platform Data we hold about you:
- Self-service in-app: log into TradieView → Settings → Social Hub → Disconnect platform. We instantly soft-delete the connection, encrypted access token and any cached Page / Instagram metadata, and best-effort 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 at facebook.com/settings → Business Integrations, Meta automatically notifies us via the Deauthorize and Data Deletion callbacks documented in our Sub-Processor List section 5. We complete the deletion within 30 days and respond with a confirmation code you can verify at the public status URL we return.
18.2 Once deleted, your Meta Platform Data is removed from our active database and AWS S3 media buckets within 30 days. Encrypted backups are overwritten on the regular backup-retention cycle (max 30 days).
19. Google API Services and Google User Data
19.1 Limited Use Commitment
When a user connects a Google service, TradieView's use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including applicable 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 they wish to connect. Google integrations may include: Gmail; Google Calendar; Google Search Console; Google Analytics; Google Business Profile; and Google authentication. These integrations are independent where supported — a customer can connect Gmail without being forced to connect Google Calendar or Google Insights. TradieView requests permissions only when the user activates the corresponding integration.
19.3 Google Identity
When a user uses Google authentication or connects a Google account, TradieView 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
TradieView requests the Gmail modification scope https://www.googleapis.com/auth/gmail.modify to provide its two-way Unified Inbox. This permits the authorised user to: view Gmail messages and attachments; compose and send email; reply; mark messages read or unread; archive; star/unstar; apply supported mailbox state changes; and move messages to Gmail Trash. These user actions are synchronised with the connected Gmail mailbox.
TradieView does not request permission to immediately and permanently delete Gmail messages while bypassing Trash. "Delete" in TradieView moves a Gmail message to Gmail Trash, where it may remain recoverable according to Google's retention behaviour. TradieView does not request the broad https://mail.google.com/ permission. All Gmail actions are user-facing and are 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 recognition; receipt recognition; AI Drop a Doc workflows; document classification; duplicate detection; client matching; job matching; project matching; and AI-assisted draft replies requested by the user.
TradieView must not use Gmail functionality for: email warming; prohibited cold-email systems; unlawful unsolicited bulk email; bypassing Gmail restrictions; or other prohibited Gmail purposes.
19.5 Google Calendar
TradieView may access authorised Google Calendar event information for: bookings; appointments; scheduling; and calendar synchronisation. Information may include: event title; date; time; event description; location; attendees; meeting information; and other information required to provide the selected event functionality.
Where authorised, TradieView may: display Google Calendar events; create an event; modify an event; synchronise a TradieView booking with Google Calendar; and update a corresponding event following a user action.
TradieView requests only https://www.googleapis.com/auth/calendar.calendarlist.readonly (to display the calendars already available to the authorised user and identify calendars where that user has read or edit permission) and https://www.googleapis.com/auth/calendar.events (to display event information and, when the user has permission, create, reschedule, update or cancel events from TradieView). TradieView does not request access to manage calendar sharing permissions, access-control lists, or the creation/deletion of entire Google calendars — the broad calendar scope is not requested. TradieView respects the access role Google reports for each calendar: read-only calendars cannot be edited from TradieView.
19.6 Google Search Console
Where connected, TradieView may access authorised Search Console data including: clicks; impressions; search queries; pages; search positions; and related SEO metrics. This information is used only to provide website and SEO reporting to the authorised TradieView customer.
19.7 Google Analytics
Where connected, TradieView may access authorised Google Analytics data including: users; sessions; traffic; page performance; engagement metrics; and other authorised GA4 performance information. This data is used only for the user-facing Analytics and website-performance functionality inside TradieView.
19.8 Google Business Profile
Where connected, TradieView may access authorised: Google Business Profile account details; location information; business information; reviews; review responses; and other supported business-management data.
Changes to Google Business Profile only occur when initiated or specifically authorised by the user. TradieView does not automatically post review replies without a user action or specific authorised workflow.
19.9 Prohibited Use of Google User Data
TradieView does not use raw, derived, aggregated or anonymised Google Workspace API user data for: targeted advertising; personalised advertising; advertising profiling; advertising eligibility; data brokerage; information resale; lending; creditworthiness; credit decisions; lending eligibility; unrelated commercial profiling; or unrelated product monetisation.
TradieView does not sell Google User Data.
General rights elsewhere in this Privacy Policy relating to aggregated or anonymised information do not override Google's Limited Use requirements. Where Google's policy imposes a stricter rule, the stricter Google requirement applies.
19.10 Google Data + AI / Machine Learning
TradieView may use AI functionality for user-facing features such as: email triage; email summaries; draft replies; attachment processing; invoice extraction; receipt extraction; document classification; job matching; project matching; client matching; and other user-requested functionality.
However:
- TradieView does 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, TradieView uses the provider's commercial/API product (not a consumer service), and ensures provider terms/settings applicable to the service do not permit the Google Workspace content to be used for general/shared model training.
- TradieView does not voluntarily opt Google Workspace API data into: model-training programs; development-partner programs; data-sharing programs; or human-review programs unrelated to the requested user feature.
- Processing only occurs to provide the specific user-facing functionality requested by the authorised TradieView user.
- If these protections cannot be confirmed for a provider, TradieView does not send Google Workspace API user data to that provider — this restriction is enforced technically in the TradieView platform.
19.11 Human Access to Google Data
TradieView personnel do not read Google User Data except where reasonably necessary and permitted. Examples include: affirmative user consent for support; troubleshooting; security investigation; abuse investigation; operating the user-requested service; legal requirements; or another use expressly permitted by applicable Google policy. Personnel access is restricted based on role and legitimate need.
19.12 Transfer of Google User Data
Google User Data may only be transferred to service providers when: necessary to provide the user-facing feature; necessary to secure the service; permitted by Google policy; subject to appropriate confidentiality and security terms; and subject to applicable AI/ML restrictions.
TradieView does not transfer Google User Data to: advertisers; advertising networks; data brokers; information resellers; unrelated marketing companies; or unrelated organisations seeking to monetise the information.
19.13 Security of Google User Data
Google User Data is protected using: TLS/HTTPS encryption in transit; encryption at rest where stored in TradieView 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.14 Google Integration Disconnection
When the user disconnects a Google integration, TradieView immediately: marks the connection as disconnected; stops all future API requests associated with that authorisation; stops scheduled synchronisation jobs; deletes stored Google access tokens from active production storage; deletes stored Google refresh tokens from active production storage; revokes the Google OAuth grant/token where Google's API supports revocation; invalidates related cached authentication state; deletes temporary Google API cache data that is no longer required; removes active integration sessions; and logs that the integration was disconnected.
Disconnect audit logs never contain: Google access tokens; refresh tokens; passwords; full email content; or confidential Google API payloads.
19.15 Retained Customer Business Records
Disconnecting Google does not automatically destroy business records deliberately saved into TradieView by the customer. For example: a Gmail invoice enters TradieView; the AI Receipt & Invoice Collector identifies it; the customer approves it; and it is matched to a Job → Supplier Invoice → Accounts. That approved invoice has become part of the customer's TradieView business records.
If Gmail is later disconnected, TradieView: revokes Gmail access; deletes OAuth credentials; stops future Gmail sync; and deletes unnecessary Gmail cache — but does not delete the approved invoice from the Job. The saved document continues to be treated as Customer Data. This same principle applies to: receipts; invoices; attachments; documents; approved communication records; and other files intentionally saved into the TradieView workspace.
19.16 Google Data Deletion Requests
Users can request deletion of eligible Google-derived information in-app via Settings → Privacy & Data → Request Google Data Deletion, or by emailing support@tradieview.com.
Where appropriate, TradieView will: verify identity; verify authority over the connected workspace; delete eligible information; record the deletion request; and confirm completion.
Information may only be retained where legally required or reasonably necessary for limited purposes such as: taxation; accounting; security; fraud prevention; legal disputes; legal holds; or regulatory obligations. Data retained for those reasons is not used for unrelated purposes.
20. Aggregated and De-identified Information
TradieView may generally use aggregated or de-identified Platform information for: service analytics; performance; reliability; security; product development; capacity planning; internal business analysis; and industry insights, where customers and individuals are not reasonably identifiable.
However, 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 TradieView 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 may 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, TradieView will update this Privacy Policy and product disclosure where required.
22. Complaints
Privacy complaints should be sent to support@tradieview.com. TradieView will investigate complaints and respond within a reasonable period. Where applicable, an individual who is not satisfied with TradieView's response may contact the Office of the Australian Information Commissioner.
23. Changes to this Privacy Policy
23.1 TradieView may update this Privacy Policy where necessary because of: product changes; new integrations; new AI functionality; provider changes; legal changes; security requirements; or privacy requirements.
23.2 The current version will remain publicly available at https://tradieview.com/legal/privacy-policy.
23.3 Material changes should be communicated to customers where appropriate.
23.4 If the way Google User Data is used changes materially, TradieView 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 / Deletion Requests: support@tradieview.com