Legal notice,
Terms & privacy.

1. Purpose of the service

FlyFenix provides a software environment for managing virtual airlines and recording activities performed in flight simulators.

The platform may notably provide:

• management of airlines, fleets, routes and pilots;
• Virtual Dispatch and operational preparation;
• tracking via FlyFenix Interface and recording of flight paths;
• automatic or manual PIREPs;
• management of qualifications, training, and virtual compliance;
• Flight Safety Score and internal operational reviews;
• simulated economy and maintenance.

2. No real-world aviation use

FlyFenix does not guarantee the accuracy, completeness, timeliness, or availability of data from third-party services.

3. Account creation and security

The user must provide accurate information and keep credentials confidential. The user is responsible for all use of the account until unauthorized access is reported.

It is prohibited to knowingly share an account, bypass access controls, impersonate another person, attempt to access another user's account, or exploit a platform vulnerability.

4. Pilot accounts and invitations

Access to an airline as a pilot may require an invitation code. A code may be time-limited, limited in number of uses, revoked, or associated with a specific email address.

Accepting an invitation creates no employment contract, mandate, real aviation licence, or professional relationship with FlyFenix or the virtual airline concerned.

5. Dispatch, FlyFenix Interface and PIREP

Telemetry data sent by FlyFenix Interface is used to document the virtual execution of a flight. It may include position, altitude, speed, flight events, and the final technical report.

A PIREP may remain pending until validated. FlyFenix may prevent business effects from being applied until the report has been reviewed.

The user must not intentionally falsify FlyFenix Interface telemetry, PIREP, flight times, positions, fuel, or events to gain an artificial advantage.

6. Flight Safety Score

FlyFenix may automatically calculate an operational score from FlyFenix Interface telemetry or PIREP data. This score is an internal simulation mechanism.

It does not constitute a real professional assessment, medical or aeronautical fitness determination, or competency certification.

An unfavorable threshold or certain critical events may trigger a Safety Hold within FlyFenix and temporarily prevent new departures. A human review by an airline manager may be required before reactivation.

7. Service availability and evolution

FlyFenix is provided “as is” and according to available technical resources. Permanent availability, error-free operation, unlimited retention, or future compatibility is not guaranteed.

Maintenance, schema changes, API changes, network outages, or third-party service failures may temporarily interrupt some functions.

8. Services tiers

FlyFenix may depend on third-party services or software, particularly for weather data, NOTAM, charts, telemetry, or simulator connectivity.

The unavailability, modification, or removal of a third-party service cannot engage FlyFenix liability beyond what applicable law requires.

9. Prohibited conduct

The following are prohibited in particular:

• intrusion, aggressive scanning, denial-of-service attacks or exploitation of vulnerabilities;
• abusive automation or circumvention of technical limits;
• publication of illegal, hateful or fraudulent content, or content infringing third-party rights;
• intentional falsification of operational data;
• use of the service to prepare or operate a real-world flight;
• unauthorized resale or commercial exploitation of the service or its content.

10. Account suspension and closure

FlyFenix may limit, suspend, or close an account in cases of abuse, fraud, security impact, repeated breach of these Terms, or serious technical necessity.

Except in a security emergency, a proportionate and reversible measure is preferred where reasonably possible.

11. Limitation of liability

To the fullest extent permitted by applicable law, FlyFenix is not liable for indirect losses, loss of unsaved data, third-party service interruptions, simulator incompatibilities, external data errors, or consequences of use contrary to these Terms.

No provision of these Terms is intended to exclude liability that cannot legally be excluded or limited.

12. Intellectual property

FlyFenix code, interface, brand, texts, and proprietary elements remain protected by applicable rights.

Third-party trademarks, software, data, and content remain the property of their respective owners. Their presence or interoperability with FlyFenix does not imply any official affiliation.

13. Data and content provided by users

The user retains ownership of content they provide, subject to third-party rights. The user grants FlyFenix a non-exclusive authorization, limited to operating the service, to store, display, process, and back up information required for their account, virtual airline, and flights.

14. Changes to the Terms of Use

These terms may evolve to reflect new features, security requirements, or legal changes.

A significant change may be reported in the interface or at a future login.

1. Data controller

The data controller is: NUICOM PF.

Contact regarding personal data: [email protected].

2. Categories of data processed

Depending on the features used, FlyFenix may process:

• identity and contact data: first name, last name, email, date of birth, nationality;
• authentication data: identifier, password hash, account status;
• airline and role data: airline, rank, base, qualifications, training;
• flight data: Dispatch, PIREP, route, FlyFenix Interface telemetry, events, and final reports;
• technical data: IP, user agent, login dates, security logs;
• derived data: Safety scores, operational statuses, and internal alerts;
• support exchanges.

3. “Medical” module: simulation only

Users must not enter any real diagnosis, medical record, treatment, disability, sensitive health information, or real medical document.

If FlyFenix were ever to intentionally process actual health data, an appropriate legal basis, enhanced safeguards, and specific information would be required before any collection.

4. Purposes and legal bases

Purpose	Data	Primary legal basis
Account creation and management	Identity, email, authentication	Performance of the requested service
Airline and flight management	Role, Dispatch, PIREP, FlyFenix Interface	Performance of service / legitimate interest
Security and abuse prevention	IP, logs, login attempts	Legitimate security interest
Flight Safety Score	Telemetry, events, derived scores	Performance of service / legitimate operational interest
Support	Name, email, message	User request / legitimate interest

5. Automated decisions and Safety Hold

Some scores or operational statuses may be calculated automatically from flight data.

These decisions concern only use of FlyFenix and have no effect on any real aviation licence, fitness status, or qualification.

When a Safety Hold is triggered, human intervention by a manager is provided to review or lift the restriction.

6. Recipients

Data may be accessible, within the limits of their roles, to the account holder, managers of the relevant virtual airline, and technical administrators required for service operation and security.

Technical providers may also process certain data for hosting, security, email, or technical-resource delivery.

7. Third-party services and transfers

Some pages or features may rely on third-party services. When a resource is loaded directly from a third party, that third party may receive technical information such as IP address or user agent.

Where international transfers apply, FlyFenix seeks to rely on the safeguards required by applicable law.

8. Retention periods

Category	Indicative maximum period
Account and profile	Lifetime of account then up to 12 months, unless otherwise required
Login and security logs	Up to 12 months
Support messages	Up to 24 months
Expired/revoked invitations	Up to 6 months after expiry or revocation
PIREP / Interface telemetry / operational history	As long as required for airline operation; after account deletion, anonymized or deleted when personal identification is no longer necessary
Safety scores and virtual compliance	Lifetime of account, then deletion or anonymization according to operational need

These periods may be shortened when data is no longer necessary or extended when a legal obligation, dispute, or security need justifies it.

9. Security

FlyFenix implements technical and organizational measures intended to limit unauthorized access, modification, disclosure, or destruction of data.

Passwords are intended to be stored as hashes and not in plain text. No user should send their password, FlyFenix Interface token, or private key to support.

10. Account deletion and persistent history

Deleting an account may require separating personal identity from certain PIREP or historical events rather than simply deleting all operational data, in order to preserve consistency in a persistent airline.

Where possible, historical items retained after deletion are anonymized or made not directly identifiable.

FlyFenix uses cookies or equivalent mechanisms strictly necessary for authentication, session security, and form operation.

FlyFenix may also load a Google Ads measurement tool to assess campaign effectiveness. This tracker is loaded on the public page only after explicit consent. Refusal does not disable any FlyFenix feature.

The choice regarding these trackers is stored locally in the browser so the same consent is not requested on every page. Mechanisms strictly necessary for authentication and security remain independent of this choice.

Subject to applicable law, a data subject may in particular request:

• access to their data;
• rectification of their data;
• erasure of their data where the applicable conditions are met;
• restriction of processing;
• objection to certain processing based on legitimate interests;
• data portability where applicable;
• withdrawal of consent where processing is based on consent.

Requests may be sent to: [email protected].

Reasonable proof of identity may be requested when necessary to avoid disclosing data to an unauthorized third party.

A complaint may also be submitted to the competent data-protection authority for the person concerned.

In the event of difficulty, the user is invited to contact FlyFenix to seek an amicable solution.

Mandatory rules of law applicable to the user or publisher remain applicable. These Terms are not intended to deprive a consumer or data subject of mandatory protection legally available to them.

The competent court is determined in accordance with applicable mandatory rules, and not by a clause intended to unlawfully exclude a competent court.