Flight Management App — Privacy Policy
Version: 1.0 - Effective 26 August 2026
Flight Management App ("FMA", "we", "us", "our") respects your privacy and is committed to protecting
personal information.
This Privacy Policy explains how FMA collects, uses, stores, discloses and protects personal
information when customers, users, passengers, staff, agents, contractors and website visitors
access or use FMA.
By accessing or using FMA, you acknowledge that your personal information may be collected, used and
disclosed in accordance with this Privacy Policy.
1. Scope
This Privacy Policy applies to:
- 1.1 FMA software and applications;
- 1.2 FMA websites;
- 1.3 customer portals;
- 1.4 booking portals;
- 1.5 support services;
- 1.6 communications with FMA; and
- 1.7 related services provided by FMA.
This Privacy Policy does not apply to third-party websites, services or applications that may be
linked from FMA.
2. Information We Collect
The information collected depends on how FMA is used. Below are examples of information we may
collect.
2.1 Customer Account Information
We may collect:
- 2.1.1 name;
- 2.1.2 business name;
- 2.1.3 email address;
- 2.1.4 telephone number;
- 2.1.5 billing details;
- 2.1.6 subscription information;
- 2.1.7 domain information;
- 2.1.8 account preferences; and
- 2.1.9 communications with us.
2.2 Passenger Information
Customers may enter passenger information into FMA, including:
- 2.2.1 name;
- 2.2.2 contact details;
- 2.2.3 booking information;
- 2.2.4 flight information;
- 2.2.5 accommodation details;
- 2.2.6 transfer details;
- 2.2.7 passenger weights;
- 2.2.8 baggage weights;
- 2.2.9 manifests;
- 2.2.10 travel records; and
- 2.2.11 operational notes.
2.3 Staff and Pilot Information
Customers may store:
- 2.3.1 employee names;
- 2.3.2 contact information;
- 2.3.3 positions and roles;
- 2.3.4 pilot licence numbers;
- 2.3.5 licence expiry dates;
- 2.3.6 medical expiry dates;
- 2.3.7 qualifications;
- 2.3.8 training records;
- 2.3.9 compliance records;
- 2.3.10 scheduling information; and
- 2.3.11 operational responsibilities.
2.4 Agent and Business Partner Information
Customers may store information relating to:
- 2.4.1 travel agents;
- 2.4.2 lodges;
- 2.4.3 charter operators;
- 2.4.4 suppliers;
- 2.4.5 contractors; and
- 2.4.6 other business partners.
2.5 Payment Information
FMA may record payment-related information including:
- 2.5.1 transaction references;
- 2.5.2 payment status;
- 2.5.3 invoice details;
- 2.5.4 billing information; and
- 2.5.5 payment provider identifiers.
FMA does not store full payment card numbers.
2.6 Technical and Usage Information
We may automatically collect:
- 2.6.1 IP addresses;
- 2.6.2 browser information;
- 2.6.3 device information;
- 2.6.4 operating system information;
- 2.6.5 login timestamps;
- 2.6.6 access logs;
- 2.6.7 audit logs;
- 2.6.8 usage metrics;
- 2.6.9 security logs;
- 2.6.10 error reports;
- 2.6.11 activity records; and
- 2.6.12 interactions with FMA.
2.7 Support Information
Where you contact support, we may collect:
- 2.7.1 support requests;
- 2.7.2 screenshots;
- 2.7.3 attachments;
- 2.7.4 communications;
- 2.7.5 diagnostic information; and
- 2.7.6 troubleshooting information.
3. How We Collect Information
We may collect information:
- 3.1 directly from users;
- 3.2 directly from customers;
- 3.3 through online forms;
- 3.4 through bookings;
- 3.5 through user accounts;
- 3.6 through support requests;
- 3.7 through system logs;
- 3.8 through integrations;
- 3.9 through APIs;
- 3.10 from third-party service providers; and
- 3.11 from authorised representatives.
4. Why We Collect Information
We collect information for purposes including:
- 4.1 providing FMA services;
- 4.2 managing subscriptions;
- 4.3 processing payments;
- 4.4 maintaining customer accounts;
- 4.5 providing support;
- 4.6 generating manifests and reports;
- 4.7 enabling scheduling functionality;
- 4.8 enabling operational workflows;
- 4.9 maintaining audit trails;
- 4.10 protecting system security;
- 4.11 detecting fraud;
- 4.12 troubleshooting issues;
- 4.13 communicating with users;
- 4.14 improving FMA;
- 4.15 complying with legal obligations; and
- 4.16 enforcing our Terms
and
Conditions.
5. Legal Basis for Processing
Where applicable privacy laws require a legal basis, FMA may process personal information because:
- 5.1 the processing is necessary to provide requested services;
- 5.2 the processing is necessary to perform contractual obligations;
- 5.3 the individual has consented;
- 5.4 the processing is required by law; or
- 5.5 FMA has a legitimate business interest in operating and improving its services.
6. Data Ownership
As between FMA and the customer:
- 6.1 customers retain ownership of Customer Data entered into FMA;
- 6.2 FMA does not claim ownership of Customer Data;
- 6.3 FMA receives limited rights to process Customer Data for the purposes described in this
Privacy
Policy and the Terms
and Conditions.
7. Disclosure of Information
We may disclose information to:
Service Providers
Including:
- 7.1 cloud hosting providers;
- 7.2 infrastructure providers;
- 7.3 email delivery providers;
- 7.4 payment providers;
- 7.5 domain service providers;
- 7.6 customer support providers;
- 7.7 security providers; and
- 7.8 backup providers.
Legal and Regulatory Authorities
Where required by law, court order, subpoena, regulatory request, law enforcement request or legal
process.
Business Transactions
If FMA undergoes:
- 7.9 merger;
- 7.10 acquisition;
- 7.11 restructuring;
- 7.12 sale of assets; or
- 7.13 corporate reorganisation.
With Customer Instructions
Where a customer directs us to provide information to a third party.
8. International Data Transfers
FMA customers may operate in multiple countries.
Personal information may be processed or stored in:
- 8.1 Australia;
- 8.2 the country in which the customer operates;
- 8.3 jurisdictions where FMA service providers operate; or
- 8.4 jurisdictions where backup and cloud services are located.
Where reasonably required, FMA will take steps intended to protect personal information during
international transfers.
9. Data Security
FMA implements reasonable technical and organisational security measures, including:
- 9.1 password protection;
- 9.2 encrypted network communications;
- 9.3 role-based permissions;
- 9.4 account access controls;
- 9.5 audit logging;
- 9.6 security monitoring;
- 9.7 database isolation between customers;
- 9.8 automated backups; and
- 9.9 access restrictions.
No internet-connected system can be guaranteed to be completely secure.
Users are responsible for:
- 9.10 maintaining secure passwords;
- 9.11 protecting account credentials;
- 9.12 controlling user access; and
- 9.13 promptly notifying FMA of suspected security incidents.
10. Data Retention
FMA retains information for as long as reasonably necessary to:
- 10.1 provide services;
- 10.2 maintain operational records;
- 10.3 satisfy legal obligations;
- 10.4 resolve disputes;
- 10.5 enforce agreements; and
- 10.6 maintain backups and security records.
Retention periods may vary depending on:
- 10.7 the nature of the information;
- 10.8 customer instructions;
- 10.9 legal requirements; and
- 10.10 operational requirements.
11. Customer Data Deletion
Customers may request deletion of Customer Data, subject to:
- 11.1 legal obligations;
- 11.2 regulatory requirements;
- 11.3 fraud prevention requirements;
- 11.4 dispute resolution requirements; and
- 11.5 backup and disaster recovery processes.
Certain information may remain in backups for a reasonable period before permanent deletion occurs.
12. Data Following Account Cancellation
Following cancellation or termination of an FMA subscription:
- 12.1 customers may request export of Customer Data;
- 12.2 FMA may retain information where required by law;
- 12.3 FMA may retain backup copies for reasonable operational purposes; and
- 12.4 FMA may permanently delete Customer Data after applicable retention periods expire.
13. Cookies and Similar Technologies
FMA websites may use:
- 13.1 cookies;
- 13.2 session identifiers;
- 13.3 authentication tokens;
- 13.4 analytics technologies; and
- 13.5 similar technologies.
These technologies may be used for:
- 13.6 authentication;
- 13.7 security;
- 13.8 performance monitoring;
- 13.9 functionality;
- 13.10 remembering preferences; and
- 13.11 improving services.
14. Marketing Communications
We may send:
- 14.1 service notifications;
- 14.2 operational updates;
- 14.3 billing notifications;
- 14.4 security notices; and
- 14.5 product announcements.
Where required by law, marketing communications will only be sent with appropriate consent or other
lawful basis.
Users may unsubscribe from marketing communications at any time.
15. Children's Privacy
FMA is designed for use by consumers, businesses and organisations.
Passenger information relating to minors may be entered into FMA by customers where required for
operational purposes.
Customers are responsible for ensuring they have appropriate legal authority to provide information
relating to minors.
16. Your Privacy Rights
Subject to applicable law, individuals may have rights to:
- 16.1 request access to their personal information;
- 16.2 request correction of inaccurate information;
- 16.3 request deletion of certain information;
- 16.4 request restriction of processing;
- 16.5 object to certain processing activities;
- 16.6 withdraw consent where consent applies; and
- 16.7 lodge a complaint with an applicable privacy regulator.
17. Privacy Complaints
If you believe FMA has mishandled your personal information, please contact us in writing. We will
investigate privacy complaints and respond within a reasonable period. If you are not satisfied with
our response, you may contact the relevant privacy regulator in your jurisdiction. For Australian
privacy matters, this may include the Office of the Australian Information Commissioner (OAIC).
18. Changes to This Privacy Policy
FMA may update this Privacy Policy from time to time.
Where reasonably practicable, material changes will be notified through:
- 18.1 the FMA platform;
- 18.2 email notifications; or
- 18.3 publication on the FMA website.
The updated version will become effective on the date specified in the revised Privacy Policy.