GENERAL TERMS OF USE
FLIGHTINITY.COM
Current version: September 2026
These General Terms of Use, hereinafter the “GTU”, define the conditions for access to and use of the FLIGHTINITY.COM service, accessible in particular at the following address:
https://flightinity.com
They apply in particular to travelers using FLIGHTINITY as well as to recipient relatives when they access the secure portal made available to them.
Use of the service implies that the user has read and, where requested, accepted these GTU.
ARTICLE 1 — IDENTITY AND MARKETING OF THE SERVICE
The FLIGHTINITY.COM service is marketed by:
FLIGHTINITY by company ECO EVENT SARL
SIREN : 799 853 148
Registered office: 78 avenue des Champs-Élysées, 75008 Paris, France
Official website: https://flightinity.com
ECO EVENT SARL provides the marketing and commercial operation of the FLIGHTINITY.COM service.
Information relating to hosting, technical providers, and data storage is specified in the Legal Notice of FLIGHTINITY.COM.
ARTICLE 2 — TRADEMARK AND OWNERSHIP
The FLIGHTINITY trademark, as well as the ownership and intellectual property rights attached to it, belong to one or more natural persons.
The identity of the owners is not intended to appear in these GTU.
The marketing and operation of the service by ECO EVENT SARL do not imply any automatic transfer of ownership of the trademark or of the rights attached to it.
ARTICLE 3 — PURPOSE OF FLIGHTINITY
FLIGHTINITY is a digital service enabling, in particular, a traveler to prepare, before a trip, personal messages intended for one or more relatives.
These messages may in particular include: text; photographs; videos; audio files; PDF documents; other attachments compatible with the service.
The messages are stored in a secure space.
If necessary, and where the traveler is unable to carry out the transmission themself, the messages may be made accessible to the relatives concerned under the strict conditions laid down by FLIGHTINITY.
FLIGHTINITY may also offer: trip creation; flight tracking; flight tracking sharing; mapping; relatives management; message management; credits management; history; secure relatives portal; notifications; CHAT ENVOL FLIGHTINITY.
ARTICLE 4 — FUNDAMENTAL PRINCIPLE: NO AUTOMATIC TRANSMISSION
FLIGHTINITY DOES NOT CARRY OUT ANY AUTOMATIC TRANSMISSION OF MESSAGES.
The absence of confirmation from the traveler, the expiry of a time period, the flight’s scheduled arrival time, or any other technical condition are never, by themselves alone, sufficient to automatically trigger the transmission of a message.
Any making available of messages requires human and manual intervention by an authorized administrator following a rigorous verification procedure.
This procedure may in particular include: flight verification; arrival time verification; analysis of available data; analysis of follow-ups; consultation of history; attempt to make contact; administrative review; enhanced authentication; secure code; multi-factor authentication or MFA; final manual validation.
The design of the service is intended to prevent a simple counter or lack of response from automatically causing the dissemination of personal messages.
ARTICLE 5 — THE PARTIES INVOLVED IN THE SERVICE
5.1 The traveler
The traveler is the registered user. They may in particular: create their account; purchase credits; create trips; register relatives; prepare messages; add attachments; designate recipients; manage their authorizations; view their balance; view their history.
5.2 The relative
The relative is the person designated as the potential recipient of one or more messages. The relative does not need to create a standard FLIGHTINITY account. Their access to authorized messages takes place through a secure portal, in particular by means of a one-time code or OTP.
5.3 The administrator
The administrator or super-administrator is a person authorized by the operator to intervene in the operation of the service. Sensitive operations are subject to enhanced security measures and are logged.
ARTICLE 6 — CREATION OF THE TRAVELER ACCOUNT
The user may create a FLIGHTINITY account in particular: by email address and password; with Google where this functionality is available; with Apple where this functionality is available.
The requested information may in particular include: email address; surname; first name where requested; telephone number, optional unless there is a specific need.
The user undertakes to provide accurate and up-to-date information.
ARTICLE 7 — VERIFICATION OF THE EMAIL ADDRESS
FLIGHTINITY may require verification of the email address before full access to the service is granted.
The email address is recorded in a standardized form.
The user must retain access to the address used for their account.
ARTICLE 8 — PASSWORD AND SECURITY
Where the account uses a password, it is not stored in plain text. It is subject to the technical protection measures implemented by FLIGHTINITY.
The user must preserve the confidentiality of their authentication means.
Any suspicion of fraudulent use must be reported to FLIGHTINITY.
ARTICLE 9 — PERSONAL SPACE
The traveler’s personal space makes it possible in particular to find: their trips; their relatives; their messages; their attachments; their credits; their purchases; their authorizations; their confirmations; their notifications; their history.
The organization and presentation of the service may evolve.
ARTICLE 10 — FREE MESSAGE UPON REGISTRATION
Upon registration, the new user currently benefits from: 1 FREE FLIGHTINITY MESSAGE.
This free message constitutes a promotional benefit. It cannot be exchanged for its cash value.
Promotional offers proposed to new users may evolve.
ARTICLE 11 — FLIGHTINITY CREDITS
Certain FLIGHTINITY features operate by means of credits.
Unless otherwise stated: a message used within the service consumes one FLIGHTINITY credit.
Credits may in particular come from: a purchase; a free credit; a bonus; a promotion; a partnership; a referral; a commercial benefit.
ARTICLE 12 — PURCHASE OF CREDITS
The user may purchase credits directly from FLIGHTINITY.
Credits are offered at the: CURRENT PRICE DISPLAYED ON FLIGHTINITY.COM AT THE TIME OF PURCHASE.
Before validation, the user must be able to review the number of credits concerned and the total amount of the transaction.
The detailed commercial terms are specified in the applicable General Terms and Conditions of Sale.
ARTICLE 13 — SECURE PAYMENT BY BANK CARD
Payments by bank card are processed by a: SECURE BANK CARD PAYMENT CENTER.
FLIGHTINITY does not directly store the user’s full bank card number.
The entry and processing of the banking data necessary for payment are carried out in the secure environment of the payment center.
Credits are credited to the user’s account after effective confirmation of payment.
Such confirmation may in particular result from: the secure payment return; server confirmation; a secure notification sent by the payment center.
A receipt or supporting document may be sent by email.
ARTICLE 14 — UNCONFIRMED PAYMENT
Where payment is not confirmed by the secure payment center, the corresponding credits are not definitively allocated.
In the event of: failure; cancellation; anomaly; incomplete payment; suspicion of fraud; FLIGHTINITY may suspend the allocation of credits until the situation has been resolved.
ARTICLE 15 — REFUND AND WITHDRAWAL
The credit refund policy is: [TO BE COMPLETED]
The consumer’s legal rights remain applicable.
The conditions relating to the right of withdrawal and, where permitted by regulations, the immediate commencement of performance of the digital service are specified in the General Terms and Conditions of Sale.
ARTICLE 16 — CREATION OF A TRIP
The traveler may create a trip by entering in particular: flight number; departure date; arrival date; departure airport; arrival airport; other information necessary for the operation of the service.
ARTICLE 17 — FLIGHT TRACKING
FLIGHTINITY may use FlightAware to obtain or enrich certain information relating to the trip.
This information may in particular include: airline; flight number; scheduled departure; actual departure; scheduled arrival; actual arrival; delay; flight status; route.
ARTICLE 18 — LIMITS OF AIR TRAVEL INFORMATION
Flight-related data come, in whole or in part, from third-party services.
FLIGHTINITY does not guarantee their constant accuracy or their instant updating.
The information presented is for informational purposes.
For any decision concerning their travel, the traveler must refer as a priority to the information communicated by: the airline; the airport; the competent authorities.
ARTICLE 19 — MAPPING
FLIGHTINITY may in particular use: OpenStreetMap and Leaflet in order to provide certain mapping information.
A map or flight representation does not constitute certified personal geolocation of the traveler.
ARTICLE 20 — ADDING RELATIVES
The traveler may register one or more relatives.
The information may in particular include: surname; first name; email address; telephone number; possible relationship with the traveler.
The email address plays in particular an important role in the operation of the secure portal and OTP authentication.
ARTICLE 21 — ACCURACY OF RELATIVES’ INFORMATION
The traveler is responsible for the contact details they provide.
An error in an email address or telephone number may prevent the normal operation of the service.
The user must therefore verify the information before activating their trip.
ARTICLE 22 — INFORMATION OF THE RELATIVE
Certain data concerning a relative are initially communicated by the traveler.
The relative is therefore not necessarily the source of their collection.
FLIGHTINITY provides the necessary information concerning the processing of these data in accordance with the applicable regulations.
ARTICLE 23 — CREATION OF MESSAGES
The traveler may prepare one or more messages.
A message may in particular include: text; photograph; video; audio file; PDF document; other compatible file.
Each message is intended for the relative or relatives selected by the traveler.
ARTICLE 24 — CONSUMPTION OF A CREDIT
The creation or use of a message may result in the consumption of a credit according to the rules displayed in the service.
Before any operation resulting in credit consumption, the operation of the application must allow the user to understand the transaction being carried out.
ARTICLE 25 — ATTACHMENTS
Attachments are stored in the technical environment provided by FLIGHTINITY.
Possible formats, maximum sizes, or restrictions are: [TO BE COMPLETED if necessary]
FLIGHTINITY may block any file that is: incompatible; corrupted; dangerous; containing malware; likely to compromise security.
ARTICLE 26 — PERSONAL AND SENSITIVE CONTENT
The traveler acknowledges that their messages may contain personal or potentially sensitive information concerning them or third parties.
It is their responsibility to ensure that they have the right to retain and transmit this information.
FLIGHTINITY acquires no ownership rights over the traveler’s personal content.
ARTICLE 27 — PROHIBITED CONTENT
It is prohibited to use FLIGHTINITY to store or transmit in particular: unlawful content; fraudulent content; content obtained unlawfully; content unlawfully infringing privacy; content intended for harassment; content infringing the rights of a third party; malware; any content whose possession or transmission would be prohibited.
ARTICLE 28 — OWNERSHIP OF THE TRAVELER’S CONTENT
The traveler remains the owner of their texts, files, and content.
They authorize FLIGHTINITY to perform only the technical operations necessary for: storage; security; display; processing; PDF generation; downloading; transfer; making available to authorized recipients.
ARTICLE 29 — ACTIVATION OF THE TRIP
Before departure, the traveler may activate the FLIGHTINITY mechanism corresponding to their trip.
This activation allows the application of the tracking, security, and control rules provided for.
The action is recorded in the history.
ARTICLE 30 — “I HAVE ARRIVED SAFELY”
After their trip, the user is invited to confirm their arrival by means of: “I HAVE ARRIVED SAFELY”
This action makes it possible in particular to: record their arrival; normally close the trip review; stop the corresponding follow-ups; update the history; avoid the unnecessary opening of a verification procedure.
ARTICLE 31 — ABSENCE OF CONFIRMATION
The absence of the confirmation “I have arrived safely” does not constitute proof that a serious event has occurred.
It may in particular be due to: an oversight; a delay; lack of network coverage; a phone being switched off; a discharged battery; a change to the trip; a technical problem; an error in the information entered.
No automatic transmission results from this.
ARTICLE 32 — FOLLOW-UPS
In the absence of confirmation, FLIGHTINITY may carry out several follow-ups.
The service may in particular provide for follow-ups at set intervals in accordance with the current settings.
Follow-ups do not constitute a transmission decision.
ARTICLE 33 — REVIEW PROCEDURE
Where the situation so requires, FLIGHTINITY may open a review procedure.
It may in particular include: flight verification; review of schedules; review of available information; verification of history; further follow-ups; attempt to make contact; in-depth administrative review; human intervention.
ARTICLE 34 — STRICTLY MANUAL DECISION
Even after the opening of a review procedure: NO MESSAGE IS TRANSMITTED AUTOMATICALLY.
The final decision requires the voluntary intervention of an authorized administrator.
The system is designed so as to require explicit manual action.
ARTICLE 35 — ENHANCED AUTHENTICATION OF THE ADMINISTRATOR
Sensitive administrative actions may be protected in particular by: personal identifier; password; secure code; multi-factor authentication or MFA; renewed validation before execution.
The objective is to prevent ordinary administrative access alone from being sufficient to make protected messages accessible.
ARTICLE 36 — AUDIT LOG
Sensitive actions carried out in FLIGHTINITY are logged.
The log may in particular record: date; time; action; status change; administrator concerned; validation; authorization; refusal; transmission; security events.
The audit log is designed to be: NON-MODIFIABLE AND NON-DELETABLE FROM THE NORMAL USER AND ADMINISTRATION INTERFACES.
The objective is to preserve the integrity and traceability of operations.
The retention period for identifying data contained in this log is: [TO BE COMPLETED]
ARTICLE 37 — EXPLICIT AUTHORIZATION OF THE TRAVELER
FLIGHTINITY may ask the traveler to expressly validate the following authorization: “I authorize all relatives to consult, save, and transfer all messages.”
This authorization must be subject to explicit validation by the traveler. The validation is logged.
ARTICLE 38 — AUTHORIZATION AND TRANSMISSION: TWO DISTINCT CONDITIONS
The authorization given beforehand by the traveler does not trigger any transmission.
Two separate conditions are therefore necessary: 1. the traveler must have previously given the authorization provided for; 2. FLIGHTINITY must then manually authorize the making available after the review procedure.
Neither of these steps can, by itself alone, replace the other.
ARTICLE 39 — SCOPE OF THE RELATIVE’S RIGHTS
The relative may access only the messages actually authorized and concerning them.
They do not have access to: the traveler’s complete account; messages not intended for them; personal data of other relatives except where such data legitimately appear in the transmitted content.
ARTICLE 40 — ABSENCE OF AN AUTHORIZED MESSAGE
If no message is available for the relative, the portal may deliberately display: “NO MESSAGE AVAILABLE”
This message may in particular appear where: no transmission has been authorized; no message is intended for this relative; the review procedure has not been completed.
ARTICLE 41 — SECURE PORTAL FOR RELATIVES
The relative does not need to create a standard user account.
Their access may in particular follow the following path: receipt of an invitation; opening of the secure portal; entry of their email address; receipt of an OTP code; entry of the OTP code; confirmation of their identity; access to any authorized messages.
ARTICLE 42 — OTP CODE
The OTP code is a one-time authentication code. It has a limited validity period.
FLIGHTINITY may implement mechanisms intended to prevent abuse, in particular: maximum number of attempts; delay between two requests; limitation of resends; temporary blocking; anomaly detection.
ARTICLE 43 — ACCESS TOKEN
After successful authentication, FLIGHTINITY may create a secure token allowing the relative to temporarily maintain their access.
The contemplated duration is approximately: 30 days and must be definitively determined before production deployment: [TO BE COMPLETED / CONFIRMED]
FLIGHTINITY may revoke the token at any time in the event of: a security risk; modification of the authorization; suspicion of fraudulent use.
ARTICLE 44 — CONSULTATION OF MESSAGES
Where access is authorized, the relative may in particular: read the text; view the photos; watch the videos; listen to the audio files; consult the PDFs; view the thumbnails; download the authorized content; confirm reading; transfer the items where this functionality is authorized.
ARTICLE 45 — PDF DOWNLOAD
FLIGHTINITY may allow the relative to download the message in the form of a FLIGHTINITY PDF.
This document may in particular include: the FLIGHTINITY logo; the content of the message; useful information related to the message.
Other files may be downloaded separately where their nature does not allow their full integration into the PDF.
ARTICLE 46 — MULTIPLE DOWNLOADS
Where a message is available in the secure portal, the relative may, depending on the features offered, consult or download it several times during the period in which their authorization remains active.
These operations may be logged.
ARTICLE 47 — FORWARDING BY EMAIL
Where the traveler’s authorization allows it, the relative may forward a message or certain items by email.
After download or transfer to a system external to FLIGHTINITY, FLIGHTINITY can no longer control all copies subsequently made by their recipients.
ARTICLE 48 — READ CONFIRMATION
FLIGHTINITY may allow the relative to confirm that a message has been read.
Consultation, confirmation, and certain access events may be recorded with their date and time.
ARTICLE 49 — OFFICIAL FLIGHTINITY EMAILS
FLIGHTINITY may send in particular the following emails: welcome; account verification; password reset; invitation of a relative; access authorization; OTP code; payment receipt; administrative alert; sharing of flight tracking; security notification.
Official FLIGHTINITY emails may display the official FLIGHTINITY logo.
ARTICLE 50 — EMAIL DELIVERY
Emails may in particular be routed by: SMTP AMEN
Final receipt also depends on the recipient’s email provider.
FLIGHTINITY cannot guarantee that an email message will never be: delayed; classified as junk mail; rejected; blocked; made inaccessible due to an external cause.
ARTICLE 51 — FLIGHT SHARING
FLIGHTINITY may allow the traveler to send certain relatives a link enabling them to track the available information relating to their flight.
The link may in particular display: the flight number; schedules; available status; route; mapping information.
ARTICLE 52 — NATURE OF FLIGHT TRACKING
The tracking displayed corresponds to the available air travel information concerning the aircraft or the flight.
It does not constitute individual and certified geolocation of the traveler.
ARTICLE 53 — CHAT ENVOL FLIGHTINITY
FLIGHTINITY offers or may offer a feature called: CHAT ENVOL FLIGHTINITY
CHAT ENVOL is intended to assist the traveler during the period associated with their flight.
It may in particular be accessible when the trip is activated and until the validation: “I have arrived safely”
ARTICLE 54 — PURPOSE OF CHAT ENVOL
CHAT ENVOL may in particular allow: asking a free-form question; obtaining assistance on how FLIGHTINITY works; receiving support during the trip; receiving certain reminders; reporting a difficulty; sending a question to the FLIGHTINITY team.
ARTICLE 55 — ARTIFICIAL INTELLIGENCE AND CHAT ENVOL
CHAT ENVOL may use an automated system or artificial intelligence in particular in order to: understand questions; propose answers; translate certain requests; recognize certain topics; detect certain priority terms; direct a request to the FLIGHTINITY team.
ARTICLE 56 — NO LIVE HUMAN CHAT
CHAT ENVOL does not constitute a permanent human instant messaging service.
Where intervention by the team is necessary, FLIGHTINITY may indicate: “The Flightinity team will contact you in order to provide you with an appropriate response. The Flightinity team remains at your service.”
ARTICLE 57 — UNRECOGNIZED QUESTIONS
Where the assistance does not have a sufficiently reliable answer, it may indicate: “I prefer to forward your question to the Flightinity team in order to provide you with an appropriate response. The Flightinity team remains at your service.”
The automated service is not intended to invent an answer where it does not have sufficient information.
ARTICLE 58 — ULTIMATE EMERGENCY
CHAT ENVOL may be designed to detect certain wording that may require priority attention.
An alert may then be generated in the administration with the wording: “ULTIMATE EMERGENCY”
A notification and/or an email may be sent to authorized persons.
ARTICLE 59 — LIMITS OF THE ULTIMATE EMERGENCY MECHANISM
The foregoing mechanism is only an additional measure.
It does not guarantee: the detection of all emergencies; the absence of false positives; immediate handling; intervention by public emergency services.
ARTICLE 60 — FLIGHTINITY IS NOT AN EMERGENCY SERVICE
FLIGHTINITY is not: a medical service; a rescue service; an airline; a police service; a gendarmerie service; an air traffic control service; an official geolocation device; an official aviation safety service.
In the event of an emergency, the persons concerned must contact the competent services directly.
ARTICLE 61 — PERSONAL DATA OF THE TRAVELER
FLIGHTINITY may in particular process: surname; first name; email address; telephone number; authentication provider; travel information; purchase history; credit history; message history; connection data; security logs.
ARTICLE 62 — PERSONAL DATA OF RELATIVES
FLIGHTINITY may in particular process: surname; first name; email address; telephone number; possible relationship with the traveler; OTP requests; OTP validations; identity confirmations; consultations; downloads; transfers; read confirmations; access logs.
ARTICLE 63 — PAYMENT DATA
Payment is processed by a: SECURE BANK CARD PAYMENT CENTER.
FLIGHTINITY does not directly store full bank card numbers.
FLIGHTINITY may nevertheless retain the non-sensitive information necessary for: payment confirmation; allocation of credits; receipt; invoicing; accounting follow-up; handling a dispute; compliance with its legal obligations.
ARTICLE 64 — PURPOSES OF PROCESSING
Personal data may in particular be processed in order to: provide the service; manage the account; manage trips; manage relatives; secure messages; authenticate users; organize reviews; enable manual transmission; manage the relatives portal; track flights; manage credits; manage payments; ensure security; prevent fraud; maintain histories; comply with legal obligations.
ARTICLE 65 — LEGAL BASES
Depending on the processing concerned, it may in particular be based on: performance of the contract; consent where required; legitimate interest; compliance with a legal obligation.
The legal bases applicable to the different processing operations are detailed in the Privacy Policy of FLIGHTINITY.COM.
ARTICLE 66 — RETENTION PERIODS
The retention periods must be defined before the final publication of the Privacy Policy.
Traveler account: [TO BE COMPLETED]
Relatives’ data: [TO BE COMPLETED]
Messages: [TO BE COMPLETED]
Attachments: [TO BE COMPLETED]
Travel information: [TO BE COMPLETED]
OTP and authentication data: [TO BE COMPLETED]
History and audit log: [TO BE COMPLETED]
Security logs: [TO BE COMPLETED]
Personal data are not intended to be retained indefinitely.
ARTICLE 67 — RGPD/GDPR RIGHTS
Depending on the processing concerned and its legal basis, persons may in particular have: a right of access; a right to rectification; a right to erasure; a right to restriction; a right to object; a right to portability; the right to withdraw their consent where the processing is based on it.
Persons may also lodge a complaint with the CNIL.
ARTICLE 68 — RGPD/GDPR CONTACT
Requests concerning personal data may be sent to: [TO BE COMPLETED: dedicated email address]
DPO or contact person responsible for data protection: [TO BE COMPLETED]
If no DPO is legally required or appointed, this last reference must be adapted.
ARTICLE 69 — DATA SECURITY
FLIGHTINITY implements technical and organizational measures intended to protect data.
They may in particular include: access control; secure authentication; OTP; MFA; encryption where appropriate; logging; limitation of rights; monitoring of sensitive operations; backups; measures to prevent unauthorized access.
ARTICLE 70 — THIRD-PARTY SERVICES AND PROVIDERS
FLIGHTINITY may in particular use: AMEN — email routing; FlightAware — flight information; OpenStreetMap / Leaflet — mapping; Secure bank card payment center — secure payment processing.
Other technical providers necessary for the operation of the service may be used.
Detailed information relating to their role and the corresponding data processing is set out in the Privacy Policy where necessary.
ARTICLE 71 — SERVICE AVAILABILITY
FLIGHTINITY uses reasonable means to ensure service availability.
However, an interruption may occur in particular in the event of: maintenance; update; incident; network failure; unavailability of a provider; cyberattack; force majeure.
ARTICLE 72 — LIABILITY OF THE TRAVELER
The traveler is in particular responsible for: the information provided; the contact details of relatives; the designation of recipients; the content of messages; attachments; travel information; authorizations granted; the protection of their identifiers.
ARTICLE 73 — LIABILITY OF THE RELATIVE
The relative must protect the means of access to their portal.
In particular, they must not: voluntarily transmit their OTP to an unauthorized person; attempt to access the traveler’s account; attempt to consult messages not intended for them; use the portal fraudulently.
ARTICLE 74 — LIABILITY OF FLIGHTINITY
FLIGHTINITY uses the reasonable means necessary for the operation of the service.
FLIGHTINITY cannot be held liable for an air event itself, in particular: accident; incident; delay; cancellation; diversion; closure of an airport; decision by an airline.
FLIGHTINITY cannot guarantee the continuous operation of an independent external provider.
No provision of these GTU limits liability where such limitation would be prohibited by law.
ARTICLE 75 — FORCE MAJEURE
The parties’ liability may not be incurred where a failure results from an event meeting the conditions of force majeure as defined by French law.
ARTICLE 76 — FLIGHTINITY INTELLECTUAL PROPERTY
The FLIGHTINITY trademark, the domain name flightinity.com, the logo, interfaces, graphic elements, databases, software, texts, and elements specific to the service are protected.
The trademark and the ownership rights attached to it belong to one or more natural persons.
The service is marketed under the presentation: FLIGHTINITY by company ECO EVENT SARL
Use of the service does not confer any ownership right over these elements.
ARTICLE 77 — SUSPENSION OF ACCESS
FLIGHTINITY may suspend an account or access in particular where such a measure is necessary in order to: protect the user; protect a relative; preserve security; handle a suspicion of fraud; stop prohibited use; comply with a legal obligation.
ARTICLE 78 — DELETION OF THE ACCOUNT
The user may request the closure of their account.
Certain data may nevertheless be retained for an additional period where such retention is necessary in particular: to comply with a legal obligation; to establish proof; to process an ongoing operation; to ensure security; to exercise or defend a right.
ARTICLE 79 — EVOLUTION OF THE SERVICE
FLIGHTINITY is an evolving service.
Certain features may be: added; improved; adapted; modified; replaced.
Significant changes likely to substantially affect users’ rights will be the subject of the necessary information.
ARTICLE 80 — MODIFICATION OF THE GTU
These GTU may evolve in particular due to: a new feature; a technical development; a regulatory development; a change of provider; a security improvement.
A new acceptance may be requested where necessary.
ARTICLE 81 — SUPPLEMENTARY DOCUMENTS
These GTU must be read together with: the General Terms and Conditions of Sale; the Privacy Policy; the Legal Notice; the Cookie Policy where applicable; any special terms and conditions.
ARTICLE 82 — APPLICABLE LAW
These GTU are governed by French law, without prejudice to any mandatory provisions that may apply to the consumer by reason of their place of residence.
An amicable resolution of the dispute will be sought where appropriate.
ARTICLE 83 — PARTIAL NULLITY
If one of the provisions of these GTU is declared null and void or unenforceable, the other provisions remain applicable.
ARTICLE 84 — CONTACT
For any question relating to FLIGHTINITY:
FLIGHTINITY.COM
FLIGHTINITY by company ECO EVENT SARL
78 avenue des Champs-Élysées
75008 Paris — France
Official website: https://flightinity.com
General email: [TO BE COMPLETED]
Contact relating to personal data: [TO BE COMPLETED]
ARTICLE 85 — ACCEPTANCE OF THE GTU
Where acceptance of these GTU is required, the traveler must be able to confirm that they: have read these General Terms of Use; understand how FLIGHTINITY works; understand that FLIGHTINITY is not an emergency service; understand that no message transmission is automatic; understand that any transmission requires rigorous verification and manual intervention by FLIGHTINITY; accept these GTU.
Electronic validation formalizes this acceptance.
ARTICLE 86 — VERSION IN FORCE
Version: September 2026
These General Terms of Use enter into force upon their publication on: https://flightinity.com