⚠ Document not finalised — do not publish as is
field(s) still to be filled in legal.html,
flagged in amber below. This banner disappears by itself once every
bracket has been filled.
This English text is a courtesy translation. The French version is the authoritative one: in case of discrepancy, the French text prevails.
⚠ Decision support only
Preflight Lens is a pre-flight decision-support tool. It is not an aeronautical information service and does not replace the official pre-flight briefing required by your regulations or your operator. Data coverage and automatic classification are not guaranteed. The minima it displays are reference values, not approved operating minima, and part of them comes from user entries no authority has checked. The pilot-in-command remains solely responsible for flight preparation.
Pursuant to Article 6-III of French Law No. 2004-575 of 21 June 2004 on confidence in the digital economy (LCEN).
Feyndev — trade name of Laurent LANGLA, sole trader (micro-entrepreneur)
SIREN: 882 056 906 — SIRET: 882 056 906 00010
Address: 13 bis allée des Couralins, 64600 Anglet, France
Phone: +33 7 68 20 56 66
Contact: contact@preflightlens.com
Publication director: Laurent LANGLA
VAT: not applicable, Article 293 B of the French General Tax Code (CGI)
Frontend (website and PWA): GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, United States (GitHub Pages) — github.com.
Backend (intermediate server): Railway Corp., 548 Market St, San Francisco, CA 94104, United States — railway.com.
Mobile distribution: Google Commerce Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google Play), and Apple Distribution International Ltd. (App Store), acting as merchants of record for in-app purchases.
All elements making up the Service (source code, classification engine, interface, texts, logo, icons, the “Preflight Lens” brand) are the exclusive property of the Publisher, unless stated otherwise. Any reproduction, representation, adaptation or exploitation, in whole or in part, without prior written authorisation is prohibited (Article L.122-4 of the French Intellectual Property Code). The NOTAM data distributed by the Service comes from third-party official aeronautical sources (Article 5 of the Terms of Use) and remains the property of its respective issuers.
These Terms of Use govern access to and use of the Preflight Lens Service, available through a web browser (PWA) and through mobile apps. Using the Service implies full and unreserved acceptance of these Terms of Use. Users who do not accept them must refrain from using the Service.
Consumer status. A user who subscribes to or uses the Service for purposes falling within the scope of their professional activity acts as a professional. A user acting for purposes outside their professional activity is a consumer and benefits from the protective provisions of the French Consumer Code reflected in these Terms, in particular in Articles 9, 11.6, 12 and 13. In practice the Publisher applies Articles 11.6 and 12 to every subscriber who is a natural person, without this amounting to an acknowledgement of consumer status.
Changes to these Terms. The Publisher may amend these Terms of Use to reflect changes in the Service, in its data sources, in regulations or in its legal obligations. Amendments are not retroactive. For subscribers, any material amendment is announced in the app and on this page at least thirty days before it takes effect, earlier versions remaining available in the Service's public repository; if it is unfavourable to them, they may cancel free of charge up to thirty days after it takes effect, under the conditions of Article 14. The version applicable to a subscriber is the one in force on the day they subscribed, then each version that has come into force under these rules. For users of the free plan, the applicable version is the one in force at the time of use.
Preflight Lens is a pre-flight decision-support tool for pilots. It retrieves the NOTAMs published for a given aerodrome, automatically classifies them by severity and by flight phase on the basis of ICAO Q-codes and text analysis, and lets the user filter them by category, severity and time window. The Service neither modifies nor deletes any NOTAM: it offers a visual prioritisation of them. All retrieved NOTAMs remain available to the user.
The Service also presents, as a complement and under the same conditions: aerodrome weather observations and forecasts (METAR, TAF) and a daily forecast strip from a weather model; a schematic layout of some aerodromes, intended to locate “ground” NOTAMs; a route planning map and a display of flight information region (FIR) NOTAMs; on that map, an estimate of turbulence and a composite of radar-observed precipitation, supplemented by published SIGMETs; an estimate of flight times, wind and fuel burn by flight level; an estimate of the runway in use, derived from the wind and from traffic observations; and a search for departure and arrival aerodromes by flight number. These elements are subject to the same warning as the NOTAMs (Article 3): none of them is a certified meteorological or aeronautical product, the aerodrome layout does not conform to the AIP and must not be used for navigation, and an estimate is never published information.
Lastly, the Service includes a Minima module, which compares an aerodrome's METAR and TAF with the operating minima of each flight phase and displays, phase by phase, the result of that comparison as a three-level indicator labelled “go / marginal / no go”. The values used come from an internal reference dataset, built from public regulatory texts and approach chart readings, and supplemented by user entries (Article 8.10). The module gives no operational assessment and no overall assessment of the flight and does not replace the decision of the pilot-in-command; Article 3.7 sets out its limits.
⚠ This article prevails over any other provision
3.1. Preflight Lens is not an aeronautical information service within the meaning of ICAO Annex 15 and Commission Implementing Regulation (EU) 2017/373. The Publisher is neither an aeronautical information service provider (AISP) designated by a State nor a certified data services provider (DAT), and claims neither status.
3.2. The Service in no way replaces the official pre-flight briefing provided by authorised sources (State AIS, pre-flight information bulletin — PIB, operator briefing, company documentation). The user remains solely responsible for obtaining a complete, official briefing before any flight, in accordance with the regulations applicable to them (in particular SERA, Regulation (EU) No 965/2012, or equivalent national regulations).
3.3. Completeness not guaranteed. The data comes from third-party sources whose coverage may be incomplete. In particular, some NOTAMs with strictly national distribution (notably in Europe) may not be relayed by the Service's data source. The absence of a NOTAM in the Service never means that no NOTAM is in force.
3.4. Automatic classification. The prioritisation (severity, category, flight phase) is produced by an algorithm and may contain classification errors. It is a reading aid, never an operational assessment. The user must read the full text of every NOTAM relevant to their flight.
3.5. Data freshness. Data is cached (on the server, and on the device for offline use). It may be out of date, particularly in offline mode, which the interface indicates as such. New NOTAMs may have been published since the last synchronisation.
3.6. Professional use and EFB. For use in commercial air transport or in operations subject to Regulation (EU) No 965/2012, integrating the Service as an EFB application (type B application) is the sole responsibility of the operator, within its EFB policy and operational evaluation (AMC 20-25A and related provisions). The Publisher gives no guarantee of compliance with any given EFB policy.
3.7. Minima module. The minima displayed are reference values, produced by an automatic calculation from public regulatory texts and approach chart readings. They are not approved operating minima: the minima that apply are those in the operator's operations manual (OM-B, OM-C) and on the approach charts in force. Some of the readings come from user entries that no authority has checked. The comparison with the METAR and TAF is a reading aid: it knows neither the actual status of the equipment, nor the crew's qualifications, nor any low-visibility procedures in force, nor the MEL or CDL, nor operator-specific restrictions, and descent below the DA/MDA depends solely on the visual references acquired by the pilot. The indicator displayed is never an operational assessment, nor a clearance to depart or to fly an approach.
NOTAMs are obtained from an official international NOTAM distribution service, which aggregates the internationally distributed NOTAMs issued by national aviation authorities. The Publisher is neither the issuer nor the producer of this data: it controls neither its content, nor its accuracy, nor its availability, for which the issuing authorities remain solely responsible.
Other sources whose licence requires attribution:
Details of the licences of the redistributed third-party components (libraries, fonts, datasets) are given in the LICENSE file of the Service's public repository.
The Service is provided “as available”. The Publisher guarantees neither its continuity nor the absence of interruptions, errors or anomalies. The Service may be suspended at any time, in particular for maintenance or updates, or if the data sources or hosting providers are unavailable, without the Publisher incurring any liability as a result towards users of the free plan, to whom the Service is moreover provided “as is”. For subscribing consumers, this article applies without prejudice to the statutory guarantee of conformity (Article 13) and to the rights attached to the subscription (Part III): unavailability beyond what Article 13 allows gives rise to the remedies it sets out.
7.1. The Publisher provides the Service as described in Articles 2, 5 and 10, subject to the statutory guarantee of conformity owed to consumers (Article 13). It is not liable: (a) for the content, accuracy, completeness or availability of data issued by third parties (Article 5), which it relays without producing or controlling it and for which it gives no warranty; (b) for the consequences of an operational decision taken in disregard of Article 3 or of a use contrary to Article 4, which are the sole responsibility of the user or of their operator (7.2); (c) for damage that was not foreseeable when the subscription was taken out, in accordance with Article 1231-3 of the French Civil Code, save for gross negligence or wilful misconduct. Towards users who do not act as consumers, the Publisher's liability is further limited to direct damage and capped at the sums paid for the subscription during the twelve months preceding the event giving rise to it.
7.2. The user acknowledges that the preparation and conduct of the flight are the sole responsibility of the user as pilot-in-command, or of their operator, in accordance with the applicable regulations.
7.3. Nothing in these Terms of Use excludes or limits the Publisher's liability for fraud, gross negligence, personal injury caused by its proven negligence, or in any other case where the law prohibits such a limitation. With regard to consumers, these Terms of Use do not deprive the user of the mandatory statutory guarantees.
In short. Preflight Lens works without any user account. It does not collect personal data for commercial purposes, contains no advertising, analytics or third-party tracker, and never accesses your device location. Favourites, theme, planned route and NOTAMs saved for offline use stay on your device and can be erased at any time by clearing the app's data. When you look up an aerodrome, technical data (IP address, timestamp, requested ICAO code) transits to our intermediate server and may appear briefly in the hosting providers' technical logs; the same applies to your IP address towards the map tile server and, when you search a flight by its number, towards the community route database. Those logs are never profiled or sold. If you type a minimum into the Minima module, that value and a random device identifier are sent to our server and kept in an encrypted journal, so that the same value counts once per device rather than once per click; the identifier is tied neither to your name nor to an account and serves that purpose only; it is shown in the app and can be redrawn or erased at any time (art. 8.10). Each entry is also stamped by the server with a keyed hash of the network address it came from — never the address itself — so that one network cannot pass for several devices (art. 8.10). While access to the Service is restricted to admitted devices, the name you give your device and the dates of its admission and last access are kept in an access register (art. 8.11). In the Android and iOS apps, the device can also be admitted without a code, through a Google Play or Apple attestation: the server then keeps a hash of an identifier specific to the app on that device, and entries made from it carry its registration number, so as to count one vote per certified device and, in case of abuse, to set them aside (art. 8.10 to 8.12). Each aerodrome record lets you report a shared value; the report does not carry your identity (art. 8.12). If you subscribe, the server keeps a hash of the Google Play purchase token or of the App Store transaction identifier, the plan, the expiry date and the devices using it — no payment data (art. 8.4). Fonts are self-hosted, so no font service is contacted. Contact for any privacy request: contact@preflightlens.com.
8.1. Data minimisation. The Service is designed to work without a user account and without collecting personal data for commercial purposes.
8.2. Data stored locally. Favourites, display theme, the flight route being prepared, operating settings, NOTAMs saved for offline use, minima entered in the Minima module together with the device identifier that signs them (8.10), the local queues of pending submissions (8.8 and 8.10) and, where access is restricted, the device's access certificate (8.11), as well as the device's subscription status as verified by the server (8.4) are stored exclusively on the user's device (local storage). They are never sent to the Publisher — except for the submissions described in 8.8, 8.9 and 8.10, all triggered by a user action, and for the access certificate, which accompanies the requests made to the intermediate server — and the user may erase them at any time (by clearing the site's or the app's data). The same applies to the flight legs of the day and the next day that the Service extracts from a roster file the user provides (a calendar, or a schedule report exported from their crew portal), from a schedule the user pastes or, in the mobile application and only after the user has granted the operating system's calendar permission, from the device calendar: only those legs (aerodromes, times, and flight number where present) are kept, on the device alone; nothing else from the calendar is read, stored or transmitted, and the user may withdraw the permission at any time in the device settings. Where the user pastes the address of a roster calendar link (iCal/webcal) published by their crew portal or by a roster application, that address — which may contain a personal token — is stored on the device alone, and the calendar is downloaded by the app directly from the server that publishes it, without passing through the intermediate server; the user may delete the address at any time (Forget the roster).
8.3. Technical connection data. When requests are made to the intermediate server, technical data (IP address, timestamp, requested aerodrome code) may transit and appear temporarily in the hosting providers' technical logs (Railway, GitHub), on the basis of the Publisher's legitimate interest (operation, security, abuse prevention). The same applies to the IP address with respect to the third-party servers that the app queries directly: the OpenFreeMap map tile server, when the route planning base map loads; the ADSB.lol community route database, when the user searches for a flight's aerodromes by its number; and, only where the user has pasted a roster calendar link (8.2), the server of the crew portal or roster application that publishes that calendar, each time the app downloads it. These logs are never subject to profiling or commercial use. So that no single device can exhaust for everyone the functions that have a cost (language-model classification of NOTAMs, flight search, minima entries), the intermediate server also keeps, for the current day only, a count of these requests per admitted device (8.11) — failing that, per network origin fingerprint (8.10) —, reset every day at midnight UTC, with no history, on the same basis.
8.4. Subscription. Where a subscription is taken out through Google Play or the App Store, the transaction is processed by Google or Apple as controllers of their own processing; the Publisher neither receives nor stores any payment data — no card, no name, no billing address.
To open Premium, the app sends the intermediate server the purchase token that Google Play gives it — in the iOS app, the signed transaction that the App Store gives it. The server has Google verify the token, or itself verifies Apple's signature, and keeps only a hash of it — for the App Store, of the original transaction identifier —, together with the plan subscribed, the status and expiry date of the subscription, whether it is a free trial or a test purchase, the date of the last verification, and the registration numbers (8.11) of the devices — three at most — that use it, with the dates they were linked and last used. For a subscription taken out on the App Store, the server also receives from Apple the notifications relating to that subscription (renewal, expiry, refund), which carry the same information. These data are used solely to open Premium on the subscriber's devices and to apply the limit of Article 11.4, on the basis of the performance of the contract. They are kept for the duration of the subscription and then twelve months after it ends, to handle a complaint or a withdrawal request, and erased afterwards. Erasing a device in its settings removes it from the subscription.
8.5. Cookies and trackers. The Service uses no advertising cookies and no third-party trackers. Fonts are embedded in the app: no resource is loaded from a third-party font service. The local storage mentioned in 8.2 is strictly necessary for the Service to work and is exempt from consent under Article 82 of the French Data Protection Act (loi Informatique et Libertés).
8.6. Rights. In accordance with the GDPR and amended French Law No. 78-17 of 6 January 1978, the user has rights of access, rectification, erasure, restriction and objection, which can be exercised by writing to contact@preflightlens.com. A complaint may be lodged with the CNIL (cnil.fr), the French data protection authority.
8.7. Transfers outside the EU. As the hosting providers are established in the United States, the technical data mentioned in 8.3 may be processed outside the European Union, under the applicable transfer mechanisms (EU–US adequacy decision / the hosting providers' standard contractual clauses).
8.8. Layout gap reports. When the user reports a gap in an aerodrome layout with one click, the app sends the intermediate server the aerodrome's ICAO code, the references concerned and the text of the NOTAMs that mention them — no position, no user or device identifier, no loaded route. These reports, counted per aerodrome, are used solely to prioritise map corrections; the IP address transits under the conditions of 8.3. A report made offline is kept locally (8.2) and sent when the network returns.
8.9. Classification improvement. When a NOTAM being viewed is not recognised by any built-in classification rule, the app sends the intermediate server its raw text and the ICAO code concerned, so that a classification rule can be proposed and then reviewed by the Publisher. This transmission carries no user or device identifier and concerns only NOTAM texts, which are public data; the IP address transits under the conditions of 8.3.
8.10. Minima entered by the user. When the user reads a minimum on an approach chart and enters it in the Minima module, the app sends the intermediate server that value (decision height, RVR or visibility), the aerodrome's ICAO code, the runway end and approach type concerned, the date of entry and a device identifier. Corrections made to an aerodrome's record (magnetic variation, opening hours, runways and lengths, approaches, lighting, preferential runways) are sent in the same way, field by field. Unlike minima, they are served immediately to all users, the most recent prevailing, unless a value has been set by the Publisher.
This device identifier is a number drawn at random on the device at the first entry and kept in local storage. It is linked to no account, no name, no position and no other data of the Service, and serves one purpose only: counting consensus per device rather than per click, since the same minimum must be entered from several distinct devices before it becomes the value proposed by default. It is shown in the entry panel, and the user can draw a new one at any time or erase it with the site data (8.2); entries already sent keep the previous one.
The server also stamps each entry it receives with an imprint of its network origin: a keyed hash (HMAC-SHA-256, with a secret key held by the Publisher) of the IP address the entry came from — the whole address in IPv4, its /64 prefix in IPv6. The IP address itself is not kept, and the imprint cannot be turned back into an address without the key. As the Publisher holds that key, the imprint is pseudonymised data: it remains personal data within the meaning of the GDPR and is treated as such (encrypted journal, single purpose, retention period below). It serves one purpose only: counting distinct network origins alongside distinct devices, so that a single network cannot pass for several devices and push a false value to every pilot; two users behind the same network therefore count as one. The imprint is kept with the entry, in the same journal and for the same duration.
The Publisher keeps these entries in a journal encrypted at rest and uses them solely to establish and correct the values served within the Service. Each entry is kept for as long as it is needed to establish the value served for the runway end and approach type concerned; it ceases to be needed, and is erased at the latest during the annual review of the journal, once it has been superseded by a more recent entry from the same device, once the approach chart or regulatory text it was read from has been replaced, or once the aerodrome is no longer served by the Service. The processing is based on the Publisher's legitimate interest (building a reliable database and protecting it against forged entries) and takes place only following a voluntary action: users who do not wish it simply refrain from entering a minimum, the rest of the module working without it. An entry made offline is kept locally (8.2) and sent when the network returns; the IP address transits under the conditions of 8.3, and nothing of it is kept beyond the imprint described above.
When the entry comes from an Android or iOS app admitted by attestation (8.11), the server also stamps it with the registration number of that installation in the register of attested installations. This number, drawn at random by the server, identifies neither the user nor their device outside the Service. It serves to count consensus once per certified device. Entries stamped this way are not capped by network origin — several pilots behind the same network each count as one — and if the registration is removed from the register, they stop counting. It also allows the entries of a blocked installation to be set aside (8.12). The number is kept with the entry, in the same journal and for the same duration.
8.11. Restricted access. While the Service is in its testing phase, the intermediate server answers only devices that have been admitted. To be admitted, the user enters an access code given by the Publisher and a name for the device, of their own choosing (for example “iPhone”); the app sends both to the server. The server issues an access certificate — a random number — which the app keeps in local storage (8.2) and attaches to each request it makes to the intermediate server.
For each admitted device, the server keeps in an access register: the device name as typed, a random identifier, the dates of admission, of any re-admission and of the last access (to within five minutes), and a hash of the certificate — never the certificate itself, nor the access code. The register records nothing of what the user does in the Service: neither the aerodromes looked up, nor the routes, nor the submissions described in 8.8 to 8.10. It is used solely to restrict access during testing and to cap the number of admitted devices, on the basis of the Publisher's legitimate interest (securing the Service before its publication). An entry is kept until the device is removed from the register or restricted access ends, and at the latest twenty-four months after the device's last access, inactive entries being erased during the annual review of the register. The user can ask for its removal at any time by writing to contact@preflightlens.com, and is free to choose a device name that does not identify them.
Admission by attestation (Android app). In the Android app distributed by Google Play, the device can be admitted without a code. The app asks Google Play, through Google's Play Integrity service, for an attestation stating whether it is the genuine app distributed by Google Play, whether it runs on a certified Android device and whether it was obtained from Google Play. Google issues this attestation by processing information about the device and the app, as the controller of its own processing and under its own privacy policy (policies.google.com/privacy). The attestation, encrypted by Google, is passed to the intermediate server, which has Google decrypt it and keeps only the summary of its verdicts. To tie the attestation to this installation, the app attaches a hash (SHA-256) of the identifier the Android system assigns to the app on this device — an identifier specific to the app, which other apps cannot see, and which changes only when the device is reset.
Admission by attestation (iOS app). In the iOS app distributed by the App Store, the device can also be admitted without a code. The app creates a cryptographic key in the device's security chip and has Apple certify it through the App Attest service: the attestation Apple issues establishes that the key was created on a genuine Apple device, for the app published by the Publisher. Apple issues this attestation by processing information about the device and the app, as the controller of its own processing and under its own privacy policy (apple.com/legal/privacy). The attestation is passed to the intermediate server, which verifies it itself, without passing it on to anyone, and keeps only the platform and the environment (production or development). To tie the attestation to this installation, the app attaches an identifier drawn at random at the first attestation and kept in the device's keychain: it is neither synced with iCloud nor restored to another device, survives the app being deleted and reinstalled, and disappears when the device is reset.
For each installation admitted this way, the server keeps, in a register of attested installations separate from the access register: a hash of that identifier hash or of that identifier — never the hash or the identifier itself —, a random registration number, the dates of admission, of any new attestation and of the last access (to within five minutes), the summary of the verdicts with the app's version number (Android) or the platform and environment (iOS), and a hash of the certificate — never the certificate itself. This register holds no name. It is used to restrict the Service to the genuine app and, through the registration number attached to the entries (8.10), to count one vote per certified device and to apply any block (8.12), on the basis of the Publisher's legitimate interest (protecting the Service and the reliability of its minima database), whose balancing against the users' rights and interests is documented by the Publisher and kept available to the CNIL. An entry is kept until it is removed from the register, and at the latest twenty-four months after the installation's last access, inactive entries being erased during the annual review of the register. The user can remove it from the app, by erasing the device in the settings — the app will then request a new attestation the next time it starts —, or by writing to contact@preflightlens.com.
8.12. Reports and blocking in the aerodrome database. Values entered by users in the aerodrome database (8.10) are served to other users. Each aerodrome record therefore lets the user report a value they consider wrong or abusive. The app then sends the intermediate server the aerodrome's ICAO code, the section concerned, the reason chosen (wrong value or abusive entry) and, if the user writes one, a free note of at most 300 characters — no user, device or installation identifier. The server adds the date and the network-origin fingerprint described in 8.10 (never the IP address itself), used only to spot a series of reports coming from the same network. A notice repeating the report (aerodrome, section, reason and note) may be sent to the Publisher through the Telegram messaging service. The Publisher reviews each report and uses it only to correct the database; reports are kept up to the thousand most recent. Users are asked not to put any personal data in the note.
On the basis of a report or of any other finding, the Publisher may block an installation admitted by attestation (8.11) whose entries are wrong or abusive. The server then keeps, in a blocking register separate from the other registers, the hash of the installation identifier described in 8.11 — never the identifier itself —, the registration numbers attached to that installation, the date of the block and, where relevant, a short reason. A blocked installation keeps the use of the Service; its new entries in the aerodrome database are refused, and those it has already made stop being served to other users, without being erased from the journal. The block remains if the installation is removed from the register (erasing the device) and then admitted again: that is its purpose. The decision to block is always taken by a person, never by automated processing. The block is lifted by the Publisher, on its own initiative or at the request of the user who contests it by writing to contact@preflightlens.com. It is in any case lifted automatically twenty-four months after the last entry it refused — or after it was placed, if no entry has been attempted since —, and re-examined during the annual review of the registers. Once the block is lifted, the register no longer keeps the hash of the installation identifier or the reason, but only the registration numbers and the date of the lifting, so that the entries set aside before that date are not served again; these numbers are erased together with the entries they relate to (8.10). This processing is based on the Publisher's legitimate interest: ensuring the reliability of shared aeronautical data and protecting it against abusive entries.
These Terms of Use are governed by French law. Where the user acts as a consumer and is habitually resident in another State, this choice does not deprive them of the protection afforded by the mandatory provisions of the law of that State (Article 6 of Regulation (EC) No 593/2008, “Rome I”). In the event of a dispute, the user is invited to first contact the Publisher at contact@preflightlens.com with a view to an amicable settlement.
Consumers: in accordance with the provisions of the French Consumer Code on “the consumer dispute mediation process”, after contacting us and failing an answer that satisfies you, you may refer the dispute free of charge to a consumer mediation procedure with: CM2C, 49 rue de Ponthieu, 75008 Paris, France — Tel.: +33 1 89 47 00 14 — Website: https://www.cm2c.net/declarer-un-litige.php — Email: litiges@cm2c.net.
Requests to the mediator are filed online or by post. The mediator can only be approached after a written complaint to the Publisher that has not been satisfactorily resolved, and no later than one year after that complaint. For a cross-border dispute within the European Union, the European Consumer Centre France may be contacted. Failing an amicable settlement, the French courts shall have jurisdiction under the ordinary rules, without prejudice to the protective jurisdiction rules available to consumers, in particular those of Regulation (EU) No 1215/2012.
Language: these Terms of Use are drawn up in French. This English translation is provided for the users' convenience; only the French version, published on legal-fr.html, binds the Publisher.
In force since 5 October 2026.
The Service offers a free plan, usable without a subscription or an account, and a Premium plan, by subscription. Access through a web browser remains reserved to admitted devices (Article 8.11); the mobile apps admit genuine devices by themselves.
The free plan gives access to all retrieved NOTAMs, for an unlimited number of aerodromes and with no restriction on their content, to their classification by severity and by flight phase, to aerodrome layouts, to the full text of METAR and TAF and to observed wind, to the Minima module, to the map and to route planning — and, more generally, to every feature of the Service that is not reserved below.
The following are reserved for subscribers (subject to Article 11.1 for the iOS app):
None of these limits restricts the content of the NOTAMs, of the METAR and TAF or of the minima displayed, nor their classification, which remain fully accessible without a subscription.
These limits are announced in the app, and the subscription lifts them entirely. The allocation that binds the Publisher towards a subscriber is the one set out in this article on the day the subscription is taken out.
The plans and their prices are set out in Article 11.2. They are shown all taxes included in the app, at the time of subscribing, as Google Play or the App Store calculates them for the user's country.
11.1. Sale. In the Android app, the subscription is taken out through the Google Play in-app purchase system. Google Commerce Limited acts as merchant of record: it collects the payment, issues the receipt and handles billing. The Publisher remains responsible towards the user for the obligations incumbent on it as provider of the Service: pre-contractual information, provision and conformity of the Service, statutory guarantees, mediation and the handling of complaints; the right of withdrawal is exercised with Google Commerce Limited or with the Publisher (Article 12). In the iOS app, from version 1.1.0, the subscription is taken out through the App Store in-app purchase system: Apple Distribution International Ltd. then acts as merchant of record, on the same terms, and the right of withdrawal is exercised with Apple or with the Publisher (Article 12). Use of the iOS app itself is governed by Apple's standard licence agreement (Licensed Application End User License Agreement); these Terms govern the Service and the subscription. In earlier versions of the iOS app, which do not allow subscribing, the Premium features remain available without a subscription.
11.2. Plans and prices. The prices below include all taxes in the countries of the euro area. In other countries, the price and applicable taxes are those shown by Google Play or the App Store at the time of subscribing.
In the iOS app, as the App Store does not offer payment in instalments, only the Monthly and Six months prepaid plans are offered, in all countries; the plan with commitment and Article 11.6 concern the Android app only.
Each payment is taken at the start of its period, through the user's Google account or Apple Account.
11.3. Free trial. A seven-day free trial is offered once per Google account or Apple Account, on the plans for which Google Play or the App Store shows it. During the trial, all subscription features are available. Unless cancelled before the trial ends, the first payment is taken when it ends.
11.4. Devices. A subscription opens Premium on three devices at most, used with the same Google account or the same Apple Account. A fourth device takes the place of a device unused for thirty days; failing that, it stays on the free plan. Erasing a device in its settings frees its place.
11.5. Cancellation. The user may cancel at any time in Google Play (Payments & subscriptions › Subscriptions) or, for a subscription taken out on the App Store, in the iPhone or iPad settings (Settings › [user's name] › Subscriptions), or from the app (Settings › Premium). On the App Store, cancellation must take place at least twenty-four hours before the end of the current period to prevent its renewal. For plans without commitment, cancellation takes effect at the end of the period paid, access remaining open until then. For the plan with commitment, it takes effect at the end of the current commitment period: the monthly payments still due until then are taken, and access remains open until then. Save for the right of withdrawal (Article 12) and any statutory provision to the contrary, no pro rata refund is due for a period already started.
11.6. Renewal (Article L.215-1 of the French Consumer Code). For the plan with commitment, the app informs the subscriber, no earlier than three months and no later than one month before the end of each commitment period, of the date of that end and of their right not to renew the subscription, the deadline being shown in a box. As the Service works without an account, the Publisher holds no address for the subscriber and cannot send this information by dedicated letter or email. Accordingly, in line with Article L.215-1, a subscriber whose subscription has been renewed may end it free of charge and at any time from the renewal date, simply by writing to contact@preflightlens.com with their Google Play order number. The Publisher then cancels the subscription and refunds, within thirty days of cancellation, the sums paid since the last renewal, less those corresponding to the performance of the subscription up to cancellation. Plans without commitment can be cancelled at any time (11.5).
11.7. Payment failure. If a payment fails, access remains open for a grace period of seven days, to allow the payment method to be updated in Google Play. Beyond that, access to Premium is suspended until payment is made, and the subscription ends if it does not go through. For a subscription taken out on the App Store, Apple retries the payment for several days; access to Premium is suspended from the expiry date and restored as soon as the payment goes through.
12.1. In accordance with Article L.221-18 of the French Consumer Code, consumers have fourteen days from subscribing to withdraw, without giving any reason.
12.2. Immediate performance. Before subscribing, the consumer expressly requests, by ticking the box provided in the app, that the subscription start immediately, without waiting for the end of the withdrawal period (Article L.221-25). They keep their right of withdrawal; if they exercise it, the sums paid are refunded in full, the Publisher waiving the amount proportionate to the service supplied that Article L.221-25 would allow it to retain. As the free trial is not charged, withdrawing during the trial costs nothing.
12.3. How to withdraw. For a subscription taken out in the Android app, before the period expires, the consumer withdraws either from Google Commerce Limited, the merchant of record, through Google Play's online withdrawal function — “Report a problem” on the order, under Payments & subscriptions › Budget & history, or the Google Play withdrawal form —, which the “Withdraw from the contract here” link of the app's Settings › Premium screen leads to; or from the Publisher, by any unequivocal statement — for example using the form in the annex — sent to contact@preflightlens.com or by post, quoting the Google Play order number (starting with “GPA.”). Google Play confirms the request and its decision by email; the Publisher, when contacted directly, acknowledges receipt without delay and triggers the refund from its Google Play console. In both cases the refund is made in full, no later than fourteen days after the decision is received, using the payment method used when subscribing, through Google Play, and ends the subscription.
For a subscription taken out in the iOS app, before the period expires, the consumer withdraws either from Apple Distribution International Ltd., the merchant of record, through Apple's “Report a Problem” function (reportaproblem.apple.com), which the “Withdraw from the contract here” link of the app's Settings › Premium screen leads to; or from the Publisher, as above, quoting the Apple order ID shown on Apple's receipt. As App Store payments are collected and refunded by Apple, not by the Publisher, the refund is handled by Apple, which confirms the request and its decision by email. The Publisher, when contacted directly, acknowledges receipt without delay and tells the subscriber how to make the request to Apple. If Apple refuses to refund a withdrawal made within the period, the Publisher refunds the subscriber itself, in full, by bank transfer, to the bank details the subscriber gives it for that sole purpose, which are erased once the refund is made. The refund is made no later than fourteen days after the decision to withdraw is received. As an App Store subscription can only be cancelled by its holder, the subscriber turns off its renewal in Settings › [user's name] › Subscriptions; the Publisher, for its part, closes access to Premium.
12.4. This right applies without prejudice to the refunds Google Play or Apple grant under their own rules.
13.1. Principle. When acting as a consumer, the subscriber benefits from the statutory guarantee of conformity applicable to digital content and digital services, provided for in Articles L.224-25-1 to L.224-25-31 of the French Consumer Code. As the Service is supplied continuously, the Publisher is liable for any lack of conformity that appears during the term of the subscription. This guarantee is a matter of public policy: nothing in these Terms of Use, including Articles 6 and 7, limits or excludes it.
13.2. Conformity. The Service conforms when it matches the description in Articles 2, 5 and 10 and the limits set out in Article 3, which form part of its contractual characteristics: uncertified decision support, third-party data relayed without warranty as to its content, automatic classification, reference minima. The Publisher supplies the updates necessary to maintain that conformity throughout the subscription and informs the subscriber of available updates.
13.3. Exercise. A subscriber who notices a lack of conformity reports it to contact@preflightlens.com, quoting their Google Play order number or Apple order ID. The Publisher brings the Service into conformity without undue delay, free of charge and without major inconvenience to the subscriber; failing that, the subscriber may obtain a price reduction or the termination of the contract, the sums due being refunded through Google Play or, for a subscription taken out on the App Store, by Apple at the subscriber's request and, failing that, directly by the Publisher (12.3). The conditions of these remedies are restated in the box below.
Information box on the statutory guarantee of conformity (annex to Article D.211-4 of the French Consumer Code — courtesy translation)
The consumer is entitled to the implementation of the statutory guarantee of conformity in the event of a lack of conformity appearing within a period of the total term of the subscription, renewed periods included (continuous supply: one renewable month for the monthly plan, six renewable months for the six-month plans) from the supply of the digital content or digital service. During that period, the consumer only has to establish the existence of the lack of conformity, not the date on which it appeared.
The statutory guarantee of conformity entails an obligation to supply all updates necessary to maintain the conformity of the digital content or digital service during the whole term of the subscription.
The statutory guarantee of conformity entitles the consumer to have the digital content or digital service brought into conformity without undue delay following their request, free of charge and without major inconvenience to them.
The consumer may obtain a price reduction while keeping the digital content or digital service, or may terminate the contract and obtain a full refund in return for giving up the digital content or digital service, if:
1° The trader refuses to bring the digital content or digital service into conformity;
2° Bringing the digital content or digital service into conformity is unduly delayed;
3° Bringing the digital content or digital service into conformity cannot take place without costs being imposed on the consumer;
4° Bringing the digital content or digital service into conformity causes major inconvenience to the consumer;
5° The lack of conformity of the digital content or digital service persists despite the trader's unsuccessful attempt to bring it into conformity.
The consumer is also entitled to a price reduction or to the termination of the contract where the lack of conformity is so serious that it justifies an immediate price reduction or termination. In that case the consumer is not required to first request that the digital content or digital service be brought into conformity.
Where the lack of conformity is minor, the consumer is only entitled to have the contract terminated if the contract does not provide for the payment of a price.
Any period during which the digital content or digital service is unavailable in order to be brought back into conformity suspends the remaining guarantee period until the digital content or digital service is supplied in conformity again.
These rights result from the application of Articles L. 224-25-1 to L. 224-25-31 of the French Consumer Code.
A trader who obstructs in bad faith the implementation of the statutory guarantee of conformity is liable to a civil fine of up to €300,000, which may be raised to 10% of average annual turnover (Article L. 242-18-1 of the French Consumer Code).
The consumer also benefits from the statutory guarantee against hidden defects under Articles 1641 to 1649 of the French Civil Code, for two years from the discovery of the defect. This guarantee entitles the consumer to a price reduction if the digital content or digital service is kept, or to a full refund in return for giving up the digital content or digital service.
The Publisher may change the features of the Service, beyond what is necessary to maintain its conformity, to reflect technical or regulatory developments or changes in its data sources, at no additional cost to the subscriber. A change that has a more than minor negative impact on access to or use of the Service is announced in the app and on this page at least thirty days before it takes effect; the subscriber may then cancel free of charge up to thirty days after it takes effect, and the amounts corresponding to the period paid for and not provided are refunded through Google Play or, for a subscription taken out on the App Store, by Apple at the subscriber's request and, failing that, directly by the Publisher (Article L.224-25-25 of the French Consumer Code). If the paid offer is discontinued, subscribers are informed with reasonable notice and refunded in the same way.
(Complete and return this form only if you wish to withdraw from the contract.)
To Feyndev — Laurent LANGLA, 13 bis allée des Couralins, 64600 Anglet, France — contact@preflightlens.com:
I hereby give notice that I withdraw from my contract for the provision of the following service:
— Preflight Lens subscription, Premium;
— Subscribed on: …………;
— Google Play order number: GPA.…………, or Apple order ID: …………;
— Name of consumer: …………;
— Address of consumer: …………;
— Signature of consumer (only if this form is notified on paper): …………;
— Date: …………