AURORACREW

Airline Crew Operations

Terms of Service

These Terms govern the use of the AuroraCrew crew scheduling platform (the “Service”) provided by LEGAL: provider legal entity, registration number, registered address (“we”, “us”) to the airline operator that subscribes to it (the “Operator”), and to the individual users the Operator authorises — schedulers, operations control, department heads and crew members.

1. Who this agreement is with

The Service is licensed to the Operator, not to individual users. The Operator authorises accounts, decides who holds which role, and is responsible for the conduct of its users. Where an individual user accepts these Terms when signing in, they do so on the understanding that their employer has contracted for the Service.

2. The Service is a planning tool — the Operator remains the operator

This section is the commercially important one and must survive review intact.

• The Service assists with roster construction, duty-time checking, standby allocation, document tracking and crew notification. It supports the Operator's processes; it does not replace them.
• Automated legality checks (flight duty period limits, rest, consecutive duty days, turnaround buffers, qualification and fleet-type matching) are implemented against the rule set configured for the Operator. The Operator remains solely responsible for compliance with its Operations Manual, its Air Operator Certificate, and the requirements of its civil aviation authority.
• The Operator is responsible for verifying every roster before it is published or flown. A roster produced or checked with the Service is not a certification of legality.
• Configured rule sets, airport data, fleet data and crew qualifications are inputs supplied or approved by the Operator. We do not warrant that they reflect current regulation.
• Roster generation is rule-based, not artificial intelligence. The assignment engine applies the Operator's configured rules deterministically; it is not a machine-learning model, it is not trained on the Operator's data, and no Operator or crew data is transmitted to any generative-AI or third-party machine-learning service. Outputs are repeatable and traceable to the rules that produced them. LEGAL: revisit if an AI or ML feature is ever added — that would require re-drafting this clause and the Privacy Policy, and incrementing the acceptance version

3. Accounts, roles and security

• Accounts are personal. Credentials must not be shared, and each user is accountable for activity under their account.
• Privileged roles (crew scheduling, operations control, itinerary, department heads, platform administration) are granted by the Operator and enforced by the Service.
• The Operator must notify us promptly of any suspected compromise, and must tell us when a user leaves so their access can be withdrawn.
• Multi-factor authentication, device approval and sign-in monitoring are available and, for operational accounts, may be mandatory. LEGAL: state whether MFA is contractually required

4. Acceptable use

Users must not attempt to access data belonging to crew outside their remit, probe or circumvent the Service's access controls, extract data in bulk other than through the export features provided, or use the Service to store material unrelated to crew operations.

5. Operator data

• Rosters, flight data, crew records and documents uploaded to the Service remain the Operator's data. We claim no ownership of it.
• We process it to provide the Service, and as described in the Privacy Policy.
• Export and backup features are provided so the Operator can retain its own copies. LEGAL: retention and return/deletion obligations on termination

6. Availability, support and change

LEGAL: uptime commitment — a stated target, or explicitly none

• The Service is delivered over the public internet and depends on third-party infrastructure.
• Maintenance may require short interruptions. Where practical these are scheduled outside the Operator's peak hours.
• Features may be added, changed or withdrawn. Material reductions in functionality will be notified in advance. LEGAL: notice period

7. Fees and term

LEGAL: pricing model, billing period, currency, taxes, late payment, renewal and termination rights, notice periods

8. Warranties and liability

LEGAL: this entire section must be drafted by counsel — the disclaimer of implied warranties, the liability cap, and which losses are excluded (in particular consequential loss arising from disrupted operations, delayed or cancelled flights, or regulatory penalties). Note that the limits available depend on the governing law chosen above.

9. Confidentiality

Each party will protect the other's confidential information — for us, the Operator's rosters, crew data and commercial terms; for the Operator, the non-public workings of the Service.

10. Suspension

We may suspend access where there is a credible security threat, unlawful use, or LEGAL: non-payment terms. Where circumstances allow, we will give notice first and restore access once the cause is resolved.

11. Changes to these Terms

We may update these Terms. When a change alters what a user has agreed to, we increment the acceptance version, and users are asked to accept again when they next sign in. The current acceptance version is shown on the acceptance screen and recorded against each account.

12. Contact

Questions about these Terms: support@auroracrew.app. LEGAL: notice address for formal legal notice