FieldWise Professional
Professional Privacy Policy
Draft version 1.0 · Last updated: 27 July 2026
This policy covers the FieldWise Professional platform. Using FieldWise in a school? See the FieldWise Education Privacy Policy.
1. Purpose of this Privacy Policy
FieldWise Professional is committed to protecting the privacy, confidentiality, and security of the organisations, professionals, clients, and field teams who use the platform.
This Privacy Policy explains how FieldWise Professional collects, uses, stores, protects, manages, shares, exports, and deletes personal and organisational information across FieldWise Pro Hub and the FieldWise Professional applications.
This policy applies to:
- the FieldWise Professional website and product pages;
- FieldWise Pro Hub (accounts, organisations, clients, projects and sync);
- the FieldWise Professional applications, including Geography Pro, Ecology Pro, Agriculture Pro, Biodiversity Pro, Land & Wildlife Pro, Environmental Pro, Marine Surveyor Pro, Science Pro, and Heritage & History Pro;
- future FieldWise Professional applications and modules;
- field data capture, mapping, media and offline caching features;
- report, tabular and spatial (GIS) exports;
- any future third-party integrations, cloud storage or single sign-on connections;
- enquiry forms, pilot registrations, waitlists, and marketing communications; and
- any related exports, reports, support services, or administrative systems operated by FieldWise Professional.
FieldWise Professional is designed for professional field work. The platform helps teams plan projects, capture defensible field evidence, and turn it into reports that clients and regulators can rely on.
Where FieldWise is used by an organisation, that organisation remains responsible for determining how its client, project, and field data is used. FieldWise acts as a service provider and data processor, handling organisation data only for the purpose of delivering the FieldWise Professional service. This policy is separate from the FieldWise Education Privacy Policy, which governs the schools platform.
2. FieldWise Professional Platform Structure
FieldWise Professional is built around two connected layers: FieldWise Pro Hub and the FieldWise Professional applications.
FieldWise Pro Hub is the central platform layer that manages the secure operation of the professional ecosystem — organisation accounts, user accounts and roles, client directories, projects, sites and study areas, dynamic forms, offline sync, mapping, species and evidence records, QA and audit trails, and the secure connection between professional applications.
The FieldWise Professional applications are specialised field tools that connect to Pro Hub — including Geography Pro, Ecology Pro, Agriculture Pro, Biodiversity Pro, Land & Wildlife Pro, Environmental Pro, Marine Surveyor Pro, Science Pro, and Heritage & History Pro. Each may capture different field evidence depending on the method and profession, but all follow the same privacy and security principles set out in this policy.
FieldWise Professional is also designed to support future interoperability with commonly used cloud storage, GIS, and identity systems. These integrations will only be enabled where technically available, organisation-approved, permission-based, and consistent with privacy and security requirements.
3. Information We Collect
FieldWise Professional only collects information that is reasonably necessary to provide, operate, improve, secure, and support the platform. The type of information collected depends on how a person and organisation interacts with FieldWise.
4. Information Collected from Organisations and Users
Account and organisation information may include:
- full name;
- work email address;
- organisation or business name;
- role, job title, or user type;
- account login and authentication details;
- password or authentication information;
- team membership and access permissions;
- subscription, licensing, or access status;
- billing and account-administration contacts; and
- support or communication history.
Client and project information created in the platform may include:
- client names and contact details entered by the organisation;
- project names, references, and lifecycle status;
- sites, study areas, and boundaries;
- team assignments and responsibilities;
- documents, briefs, and deadlines;
- form templates and template versions; and
- project settings, map settings, and export settings.
Client contact details entered into FieldWise are provided and controlled by the organisation. The organisation is responsible for ensuring it has an appropriate basis to enter and use that information within the platform.
5. Field Records and Evidence
Users capture field evidence as part of their professional work. Depending on the application and method, this may include:
- written observations and field notes;
- survey and assessment responses;
- species records, counts, and condition scores;
- data tables and environmental measurements;
- checklists and method-specific forms;
- field sketches and annotated images;
- photographs and other media;
- map points, lines, polygons, routes, and transects;
- site observations and sample records;
- signatures on forms where used; and
- audio or video evidence where enabled.
Field records may include personal information only where a user chooses to record it (for example, a person appearing in a site photograph, or a landholder named in a note). Users and organisations are responsible for capturing only information relevant to the professional task.
6. Location and Field Metadata
Many FieldWise Professional activities use location features to support accurate, defensible field work. This may include:
- GPS coordinates and accuracy;
- location pins and study-site coordinates;
- datum and coordinate-system information;
- project and site boundaries;
- routes, transects, and tracks;
- map annotations;
- time and date of capture;
- observer identity attached to a record;
- record status and sync status; and
- device-generated activity metadata.
Location information is used only for professional field purposes — for example, confirming where evidence was collected, mapping observations, supporting QA and review, and producing report-ready outputs. FieldWise does not use location data for advertising, behavioural profiling, or unrelated commercial tracking.
7. Information Collected from Website Visitors and Enquiries
When a person visits the FieldWise Professional website, registers for a pilot, joins a waitlist, or contacts us, we may collect:
- name;
- work email address;
- organisation or business name;
- role or position;
- state, territory, or region;
- profession and app interests;
- message content submitted through an enquiry form; and
- communication preferences.
This information is used to respond to enquiries, provide product updates, manage pilot and early-adopter interest, and communicate with organisations and professionals who have chosen to hear from FieldWise.
8. How We Use Information
FieldWise Professional uses collected information only for legitimate operational, service, security, support, and communication purposes.
We may use information to:
- provide access to Pro Hub and the professional applications;
- allow organisations to manage clients, projects, sites, and teams;
- allow users to capture, edit, and review field records;
- sync field evidence between devices and the platform;
- generate reports, tabular exports, and spatial (GIS) packages;
- support QA, review, and audit-trail workflows;
- manage organisation accounts, roles, subscriptions, and billing;
- provide technical support;
- improve platform reliability, usability, and performance;
- monitor system performance and security;
- respond to enquiries and manage pilot or product-update communications;
- enable organisation-approved integrations where available; and
- comply with legal, regulatory, or contractual obligations.
FieldWise Professional does not sell client, project, or field data, and does not use it for advertising or unrelated commercial profiling.
9. Data Storage, Infrastructure, and Security
FieldWise Professional takes reasonable technical and organisational steps to protect information from misuse, interference, loss, unauthorised access, modification, or disclosure.
FieldWise uses Supabase as its primary backend infrastructure provider for platform data, authentication, database storage, and synced records. Persistent platform data may include organisation and user accounts, clients, projects, sites, field records, media, QA records, exports, and integration records required for the service to operate.
FieldWise aims to host organisation data in secure infrastructure located in Australia wherever technically and contractually available. Before deployment, FieldWise will confirm the hosting region and inform organisations where their data is stored. If data is stored, processed, backed up, or supported outside Australia, FieldWise will disclose this where required and take appropriate steps to protect the information.
FieldWise uses encryption and secure methods to protect data, including:
- encryption in transit using secure HTTPS/TLS connections;
- secure authentication processes;
- encryption at rest where supported by the backend provider;
- organisation tenancy and role-based access controls;
- restricted access to production systems;
- secure storage of authentication tokens where required; and
- monitoring for suspicious or unauthorised activity where technically available.
Field work often takes place in remote outdoor environments where internet access is unreliable. To support this, the app may temporarily store records and media on the device until a connection is available. When the device reconnects, this information is queued for secure synchronisation. Once syncing is complete, locally cached data may be cleared, reduced, or retained only as required for app functionality and organisation use.
10. Sensitive and Confidential Data
FieldWise Professional recognises that field work can involve sensitive or confidential information — for example, threatened or protected species locations, culturally sensitive sites, or commercially confidential client data.
The platform is designed to help organisations manage this, including:
- organisation tenancy that keeps each organisation's data separate;
- role-based access so users only see what they are authorised to;
- sensitive-species and sensitive-location controls;
- export redaction options; and
- audit trails recording who created, changed, reviewed, or exported records.
Organisations remain responsible for classifying their own sensitive data, setting appropriate access, and complying with any licence, permit, or legal conditions that apply to it.
11. Data Sharing and Third Parties
FieldWise Professional does not disclose personal or organisational information to third parties except where necessary to provide and secure the service, comply with legal obligations, or act under an organisation's instructions.
Third parties may include:
- secure cloud infrastructure providers;
- authentication providers;
- email or communication providers;
- website hosting providers;
- organisation-approved cloud storage, GIS, or identity systems;
- analytics tools used for website performance, where applicable;
- technical support services;
- legal, compliance, or security advisers; and
- government, regulatory, or law-enforcement bodies where legally required.
FieldWise will not allow third-party service providers to use organisation, client, or field data for their own advertising, marketing, behavioural profiling, or unrelated commercial purposes.
12. Marketing Communications
FieldWise Professional may send product updates, pilot information, launch announcements, or relevant content to people who have voluntarily joined a mailing list, registered for a pilot, or contacted us.
Recipients may unsubscribe from marketing communications at any time. Client and field data is not used for marketing, is not added to marketing lists, and is not shared with advertisers.
13. Data Retention
FieldWise Professional retains information only for as long as reasonably necessary to provide the service, meet organisation requirements, support records and reporting, comply with legal obligations, resolve disputes, maintain security, or meet contractual obligations.
Retention periods may vary depending on:
- organisation account and subscription settings;
- project and record requirements;
- legal or regulatory obligations;
- backup and recovery processes;
- deletion requests; and
- organisation data-retention policies.
Some data may remain temporarily in secure backups or logs for a limited period before deletion through normal backup rotation processes.
14. Data Portability, Export, and Deletion
Organisations own and control the client, project, and field data they create or manage within FieldWise.
Authorised organisation representatives may request:
- export of project and client data;
- export of field records and evidence;
- export of PDF reports, tabular workbooks, or spatial (GIS) packages;
- deletion of records, projects, or clients;
- deletion of user accounts;
- closure of the organisation account; and
- disconnection of any approved integrations.
Upon valid request, FieldWise will delete, anonymise, or return relevant data in accordance with the organisation's instructions, contractual requirements, legal obligations, and reasonable technical limits. Some data may remain temporarily in secure backups before deletion through normal backup rotation.
15. Account Termination
If an organisation ends its subscription or requests account closure, FieldWise will take reasonable steps to:
- disable access to the organisation account;
- provide an opportunity to export relevant records, where applicable;
- delete or anonymise organisation, client, and field data;
- remove user access credentials;
- disconnect approved integrations where technically possible; and
- complete data deletion in line with agreed retention and backup procedures.
FieldWise may retain limited administrative, billing, legal, or security records where required.
16. Access and Correction
Organisations and users may request access to or correction of personal information held in FieldWise. FieldWise will assist with reasonable access, correction, export, and deletion requests where technically possible and legally appropriate.
Where information relates to a client or a third party entered by an organisation, requests should usually be directed to the organisation that controls that record.
17. Data Breaches and Security Incidents
If FieldWise becomes aware of a data breach or security incident involving personal information, it will take reasonable steps to:
- contain the incident;
- assess the nature and seriousness of the incident;
- identify affected data and users;
- notify affected organisations where required;
- support organisations in meeting their own notification obligations;
- remediate the issue and review relevant access controls; and
- improve safeguards to reduce the risk of future incidents.
Where required by law, FieldWise will support notification to relevant regulators or affected individuals.
18. International Data Processing
FieldWise aims to use Australian-hosted infrastructure for organisation data wherever technically and contractually available.
However, some third-party providers, support systems, cloud storage providers, authentication systems, or technical services may process or store information outside Australia. Where this occurs, FieldWise will take reasonable steps to ensure the information is protected and that organisations are informed where required.
19. Professional Use and Limitations
FieldWise Professional records evidence and supports professional decisions. It does not make regulatory determinations and does not replace licences, permits, or qualified professional judgement.
Organisations and users remain responsible for the accuracy of the records they capture, for complying with the laws, licences, and permits that apply to their work, and for the conclusions and reports they produce using FieldWise.
20. Changes to This Privacy Policy
FieldWise Professional may update this Privacy Policy from time to time as the platform develops, new applications are released, legal requirements change, integrations are added, or security practices improve.
When significant changes are made, FieldWise will update the policy date and, where appropriate, notify account holders.
21. Contact
Questions about this Privacy Policy or FieldWise Education’s handling of personal information can be directed to:
FieldWise Education
Email: benjamen.holley@fieldwiseeducation.com.au
Website: www.fieldwiseeducation.com.au
This policy is a current draft (v1.0). We recommend a final review by legal counsel against the Australian Privacy Act / APPs before public launch.