Privacy Policy

Effective date: 2 November 2026 · Version 1.16 · Privacy contact: [email protected]

Changes in 1.16: route subscriptions and alerts now also cover Qatar Airways and Japan Airlines; from extension 0.4.8 the side-panel alert banner also shows matches from British Airways, Qatar Airways and Japan Airlines, and asks our server for them by sending the list of sites it can show together with the installation ID it already sends. Changes in 1.15: from extension 0.4.7, Japan Airlines International award results are read and recorded while Japan Airlines support is enabled; section 1 lists the uploaded Japan Airlines fields, and section 2 no longer lists Japan Airlines as a button-only site. Changes in 1.14: new section 6 describes FeiLog (feilog.feifinder.com), the separate trip-log site: what it stores, the one-time email sign-in and browser storage, the optional OpenFreeMap basemap that receives your IP address and the map areas you view, local-only share images and videos, export, deletion and how to contact us about retained data. Changes in 1.13: from extension 0.4.6, Qatar Airways searches with more than one passenger and return searches are also recorded; the uploaded Qatar fields now include the trip type and the numbers of adults, children and infants in the search. Changes in 1.12: describes how extension 0.4.5 reads and shows your British Airways and Qatar Airways Avios balances on your device only. Changes in 1.11: describes Qatar award-result processing and the floating button on specified additional airline booking pages introduced in extension 0.4.5. These features do not apply to extension 0.4.4. Changes in 1.10: clarifies how Cathay calendar data is handled, how long failed digest records and personal search history are kept.

FeiFinder ("we", "the extension") is a browser extension that helps users find award-flight seat availability. It works by passively capturing availability results from your own searches on the airline booking websites the extension operates on (see the host permissions in the extension listing), pooling that availability data (stored against a random installation ID, never your contact details), and using the pool to send the route alerts that users choose to subscribe to. This policy explains exactly what data we handle. FeiFinder is an independent project and is not affiliated with, endorsed by, or connected to any airline.

This policy covers the FeiFinder browser extension and the separate FeiLog website. Sections 1–5 describe the extension; section 6 describes FeiLog; section 7 applies to both.

1. Data we collect

Data	When	Why
Anonymous installation ID — a random identifier (UUID) generated on install and stored locally and through Chrome sync, so the same identifier may be reused across your devices or after a reinstall; contains nothing about you by itself — if you connect an email address, our database links the two	Always	Attributes your contributions and shows your own search history and credits
Flight availability data — route, dates, per-cabin seat counts, miles and tax / cash amounts (adult and child), flight numbers and per-segment details (including the marketing airline of each segment, e.g. CX or a partner such as JL), passenger count, the source URL on the booking site (the Cathay page or availability-request address, including its query parameters; no URL is uploaded for British Airways or Qatar Airways), and capture timestamps; for British Airways also the seat count BA shows for each cabin (or "9+" when BA shows the cabin as available without a number), the booking classes of each cabin, and the counts of adults, young adults, children and infants in the search; for Qatar Airways, from extension 0.4.5 while support is enabled, the uploaded fields are the search type (one way; from extension 0.4.6 also return, with each direction recorded separately) and, from 0.4.6, the numbers of adults, children and infants in the search; segment airports, flight numbers, local departure and arrival times, aircraft codes, site-reported operator names and codes, segment and connection durations, stop airports, stop durations and change-of-aircraft indicators; total itinerary duration and the stop count Qatar reports; per-cabin seat counts and whether a cabin was reported or not shown; Avios per adult (not recorded when the search includes children or infants), Classic/Flexi fare type and Privilege Deal flag; and the observation time and batch identifier, linked to the installation ID. Eligible offers returned in Qatar’s response may be recorded even when Qatar’s screen does not display them for the cabin you selected. Unsupported or unreadable searches and answers with no offers produce no Qatar record. Qatar URLs, taxes and directional listings are not uploaded. For Japan Airlines, from extension 0.4.7 while support is enabled, only offers that JAL’s International award results data marks as bookable are uploaded; for each such offer the uploaded fields are the search type (one way or return, each direction recorded separately) and the numbers of adults, young adults, children and infants in the search; segment airports and terminals, marketing airline and flight number, local departure and arrival times, aircraft code, technical-stop count, connection time and airport-change indicator; total itinerary duration; the cabin; the seat count from JAL’s embedded result data (1 to 8 recorded as exact counts; the value 9 recorded as a lower bound and shown by FeiFinder as “9+”); the booking class, the fare family, the cabin of each segment and whether cabins are mixed; the price scope (one way, one direction of a return, or return-combination-only); miles and taxes per adult and the tax currency, where readable — for return searches without readable per-direction adult prices, miles, taxes and currency are left empty; and the observation time, the batch identifier and an offer-variant identifier derived from the uploaded offer fields to distinguish otherwise matching offers, linked to the installation ID. Wait-listed, sold-out and zero-seat offers, Japan Airlines URLs and directional listings are not uploaded. Embedded page data is processed locally to identify supported award-result pages; flight offers from standalone partner-airline and oneworld award-result pages are not extracted or uploaded. Airline and flight number are recorded from the marketing-airline details JAL provides; the operating airline is as shown on JAL’s page. From version 0.4.3, for each cabin also whether the page showed it as available, not available or not shown, with observation times and identifiers linking capture batches, directional listings and related records. We also upload complete lists of the itineraries a search showed for one direction (a "listing"), including qualifying empty lists. Cathay listings are limited to qualifying one-passenger, one-way searches; British Airways listings may also be uploaded for multi-passenger searches and for each direction of a return search, and only eligible listings for a party requiring one seat (lap infants are not counted) are used — together with other users' searches — to treat a flight that keeps not being listed as no longer having seats. Dates you did not pick (shown alongside your search), searches with no results and empty listings may also be uploaded automatically; you do not share each one by hand	When your own search produces data on Cathay, including prefetched calendar availability; on British Airways redemption pages while support is enabled; and, from extension 0.4.5, on Qatar award searches while support is enabled; and, from extension 0.4.7, on Japan Airlines International award results pages while support is enabled	Recorded flight results support your personal history; eligible contributions also support the shared availability pool used for route alerts. Cathay date-strip observations are handled separately: the extension uploads only dates the site explicitly marks as unavailable. Dates you selected can be stored in your personal history; observations from eligible approved contributors searching for one passenger can also update shared day-level records. Dates you did not select are not added to your personal history. Cathay’s prefetched calendar summaries are still uploaded but are discarded by our server on receipt; the store that held them was retired and cleared on 11 October 2026.
British Airways price you open — the Avios and cash total BA shows after you pick a cabin (for all passengers), stored together with the per-adult amount (total divided by the number of adults; cash rounded to the cent), the currency, which flight and cabin it belongs to, the time it was seen, a sequence number and a reference to the matching record in your personal history. This is the price BA shows at that step, not a guaranteed final price. To find it, the extension looks at BA's own answer to your pick inside your browser. That answer can also contain other details of your BA session (for example your member name); those are only looked at in your browser to find the price line and are never stored or uploaded	Only when you yourself pick a cabin on a one-way, adults-only British Airways results page, while British Airways support is switched on	Shown in your own search history only. Not added to the shared pool, not used for alerts, not shown to other users
Your airline balances (Cathay Asia Miles; from extension 0.4.5 also British Airways Avios and Qatar Airways Avios) — one number per site and the time it was read, stored only in browser local storage; never uploaded	When a supported page of that site, while you are signed in, loads your balance itself (Cathay pages; British Airways redemption pages; Qatar award booking pages)	Show each balance separately in the panel; for Cathay results, mark whether a result is within your Asia Miles balance
Floating-button position and first-use hint state — stored only in browser local storage	When the button is first shown or moved on an eligible page; additional airline sites are included from extension 0.4.5	Remember the button’s position and whether its introduction has been shown
Extension version number (for example 0.4.1) — stored only as a daily count per version; not linked to your installation ID or email	Each time you open the extension panel	Knowing which versions are still in use, for example before retiring an old one
Email address (double opt-in)	Only if you choose to connect email	Login verification, sending your alert digests, and — unless you turn it off — FeiFinder product news (our own features, updates and offers only; see section 5)
Telegram chat ID and username — not currently enabled	Only if you choose to connect Telegram. Telegram delivery is built but switched off. Scheduled alert digests currently go by email; matching results may also appear in the extension’s side-panel banner	Sending your alert digests via Telegram
Product-news preference — your on/off choice and a history of changes (time and where you changed it)	Only if you connect an email	Deciding whether to send product news, and showing what you chose
Notification preferences — timezone, delivery windows, subscriptions (routes / dates / cabins you follow, and which redemption sites each subscription covers)	When you subscribe	Delivering the alerts you asked for
Referral codes — your own code and codes you enter or redeem	Only when the referral feature is switched on: your own code may be created automatically for an approved account; codes you enter or redeem and related referral records are also stored	Crediting referrals

When Qatar Airways support is switched off, new writes are refused once the server’s check observes the disabled setting. The extension checks the setting before uploading each answer and may reuse an enabled result for up to 30 seconds within a batch. It stops the remaining uploads when it observes the disabled setting or receives a disabled response. Requests already started may still reach the server; switching support off does not immediately stop local page processing or cancel in-flight work. Qatar result capture is available from extension 0.4.5 while support is enabled. Route subscriptions and alerts cover Cathay Pacific, British Airways, Qatar Airways and Japan Airlines, each while subscriptions for that site are switched on. When we switch British Airways support off, the extension stops reading British Airways flight results and prices from the next page load (the Avios balance described in section 2 is still read and stays on your device), and an open page stops reading prices once the extension's background check sees the change. Separately, the server refuses new data it receives for a site that is switched off; that does not by itself stop your browser from processing a page that is already open.

Before reading embedded Japan Airlines page data, the extension requests permission from our server using the installation ID. If that check returns disabled or no usable permission, the data is not read. During uploads, an enabled check may be reused for up to 30 seconds within a batch. The server refuses new writes once its check observes that support is disabled. Switching support off does not synchronously cancel an already-authorised page read or an already-started request. Japan Airlines results are never used to mark a flight as no longer having seats.

Your personal history is stored on our server. A search can be uploaded and kept in your history even when it is not added to the shared pool and earns no credit.

2. Data we do not collect

No airline account credentials, passwords, or booking/payment details.
No names, phone numbers, addresses, or government IDs.
No general browsing history is collected. The extension runs on the domains and paths declared in its manifest. It processes supported award-search data and British Airways selected-cabin prices as described above, and checks page URLs and layout to provide its floating button. Cathay source URLs are uploaded as disclosed in section 1; URLs from the additional button-only sites are not uploaded.
Other airlines listed in the extension’s permissions (Alaska Airlines, Hawaiian Airlines, American Airlines, Finnair, Iberia, Malaysia Airlines, Oman Air, Qantas, Royal Air Maroc, Royal Jordanian and SriLankan Airlines; Japan Airlines until extension 0.4.6): From extension 0.4.5, selected booking pages of these airlines can show a floating button that opens FeiFinder’s side panel. The extension checks the page URL and layout, but does not read or upload flight results from these sites. Some cash-booking pages sharing the same engine also show the button. The panel identifies the site as unsupported; future result-reading support and its timing are not guaranteed.
Raw website responses are processed locally on your device; only the parsed availability fields and the British Airways price details listed above are uploaded.
Your Asia Miles balance and, from extension 0.4.5, your British Airways and Qatar Airways Avios balances are read from the balance answer each site’s own page loads in your signed-in session on the supported pages listed in section 1 — one number per site and the time it was read. The extension sends no request of its own for them. They are shown separately in the panel and never added together; only the Asia Miles balance is used to tell you whether a Cathay result is within your balance. Each balance is stored only on your own device (browser local storage, not synced), is never uploaded or transmitted to us or to anyone else, and is not linked to your history or the shared pool. Snapshots older than 24 hours are hidden; expiry does not itself delete the locally stored value. On supported pages, BA and Qatar snapshots are cleared when the monitored balance or session responses return an authentication failure recognised by the extension, when Qatar’s balance response requests a security check, or when the site’s balance response does not give one clear number (for example two different figures or linked accounts). Signing out elsewhere may not be detected. You can also remove the values by removing the extension or clearing its data. The British Airways balance is read even while British Airways result support is switched off.
No British Airways member details: the extension never stores or uploads your BA member name, number or tier, even when BA's pages or answers in your browser show them; only the balance number described above is kept, on your device.
No Qatar Airways member details: from Qatar’s award search answers the extension keeps only the flight and offer fields listed above; your Privilege Club name, number and tier are never stored or uploaded; only the Avios balance number described above is kept, on your device. Text of travel notices in Qatar’s answers is checked in your browser only and never uploaded.
No Japan Airlines member details: the extension reads the data embedded in JAL’s results page in your browser; your JMB name, membership number and mileage balance, which the page also contains, are never stored or uploaded; only the flight and offer fields listed in section 1 are uploaded.
A background photo you choose for a holiday-plan export image is processed only on your device and is never uploaded.

3. How data is used and shared

Availability data is the product: seat availability you capture is pooled and shared with other users only through the route alerts they subscribe to (flight, date, cabin, seats, miles). It is never publicly attributed to you or your contact details.
Contact details are never shown to other users, never sold, and never shared for anyone else's advertising. We use your email for FeiFinder's own product news only as described in section 5, and you can turn that off at any time.
We use these service providers to operate FeiFinder: Supabase (database hosting), Brevo (email delivery), Telegram Bot API (Telegram delivery), Cloudflare (web hosting). Each receives only what is needed to provide its function.
We do not sell user data, do not use it for creditworthiness or lending purposes, and do not transfer it except as described here — consistent with the Chrome Web Store User Data Policy, including its Limited Use requirements.

4. Storage, security and retention

Data is stored in a managed database (Supabase) with row-level security; management credentials are stored only as salted HMAC hashes; transport is encrypted (TLS).
Availability data is retained while it is useful to the pool; personal channel data (email / Telegram), your product-news preference and its change history, and your subscription records, including cancelled ones, are kept until you ask us to delete them. Delivery records are cleared automatically by daily jobs: the content and error details of a finished digest after about 7 days and the record itself after about 30 days (a failed digest still awaiting our review may be kept beyond 30 days; once resolved it becomes eligible for deletion under the same daily cleanup, and its content and error details are still cleared after about 7 days); older-format digest logs and email send logs after about 90 days.
Personal search-history records on our server are trimmed daily, separately for each installation ID and redemption site: records created today (Hong Kong time) and up to the 200 most recently created older records are kept; older records beyond that are deleted. One search can create more than one record.

5. Your choices and deletion

You can use FeiFinder without connecting an email address to view your own history. Email verification and approval are required to contribute to the shared pool, earn credits and subscribe to alerts.
You can stop alerts at any time: cancel individual subscriptions under “My Subscriptions” in the extension, or use the link included in every digest, which — after a confirmation page — cancels all active subscriptions of that email address (once a cancellation is completed, links in earlier digests stop working). Credits already spent are not refunded; the extension stays signed in and you can subscribe again later.
Product news. If you connect an email, we may send FeiFinder product news (new features, updates and our own offers). New users choose this when linking an email (the box starts ticked). For emails connected before this option existed, we show a notice in the extension first, with the start date, at least about a month before any product news is sent, unless you tell us you want it earlier. Turn it off any time: in the extension Settings, with the link in every product email (no login needed), or with the checkbox on the cancel-all page. Signing in or subscribing again does not turn it back on. This does not affect alert digests, login codes or access notices. Product emails already being sent when you turn it off may still arrive.
To delete your channel data or anything attributed to your installation ID, email [email protected] — we will action requests within 30 days. Availability facts already merged into the shared pool are stored against your random installation ID (never your contact details); if you ask us to delete the data attributed to your installation ID, we remove that link and keep the facts by default (a request covering only your email address removes the email channel but leaves the installation ID link in place); see section 3 of the Terms of Service, and tell us if you want those considered too.
Uninstalling the extension stops all collection immediately.

6. FeiLog (feilog.feifinder.com) — your own trip log

FeiLog (飛記) is a separate FeiFinder website for keeping your own record of past and planned journeys by air, rail, sea and road. It is currently a trial: access is by application and manual approval. FeiLog is a standalone website. The Chrome extension does not link to FeiLog or transfer trip records to or from it. Award-seat searches captured by the extension are not added to FeiLog, and FeiLog records are not added to the shared availability pool.

Applying. When applications are accepted, an email address is required and a note is optional. We store these details together with application and review status and history. For application rate limiting, we store a keyed hash of the IP address rather than the raw address. Hosting providers separately process connection metadata. Approval notices are sent through Brevo, which receives the recipient email address and message content.

Signing in and browser storage. FeiLog uses one-time email codes through Supabase Auth. The codes are sent from [email protected] through Brevo, which receives the recipient email address and the message content. Receiving a code does not itself grant FeiLog access; account access is checked separately. Where available, localStorage keeps your sign-in email and session credentials so you can stay signed in. If storage is unavailable, the session is kept in tab memory. Signing out clears the active tab's session and attempts to remove its stored copy; browser restrictions can prevent removal. The browser also stores language, appearance and map preferences, and import-resume details such as file names, hashes and settings. These other values are not cleared by signing out. You can remove local values through your browser's site-data controls.

Trip data you enter. Origin and destination (airport codes or free text such as a station name with optional coordinates), date and how precise it is, transport mode, flight or service number, airline or operator, aircraft type, registration, cabin, seat, times and time zones, diversion, notes, extra columns kept from a table import (size-limited), trip groups, and any payments you record (amounts, currencies, miles, payment method). This also includes journey status and purpose, fare class, purchase date and channel, mileage programme, and import or restore metadata such as source file names, hashes and processing results. Most fields are optional. Data is stored in dedicated FeiLog tables in the same Supabase project as FeiFinder (main database in the Singapore region).

Within FeiLog, account checks restrict access to trip records to the owning signed-in account. The application-review console shows application details, review history, account and email-delivery status, and whether the applicant's email is already verified with FeiFinder; it does not provide a view of trip records. The operator and service providers may nevertheless access stored data through privileged infrastructure tools, including database administration and backup systems.

Photos. New photo uploads are currently paused. If uploads are enabled, this policy will be updated first with the storage, processing and sharing rules.

Maps and third-party map services. The default map uses bundled Natural Earth outline data and does not contact a third-party map provider. When a detailed or globe background is selected, including a saved selection from an earlier visit, the browser requests map styles, tiles, font glyphs and sprites from OpenFreeMap (tiles.openfreemap.org). These requests expose your IP address, request times, requested map areas and font character ranges, and may indicate places along your journeys. This also applies during previews and video creation. FeiLog does not include your email, notes, travel dates or full trip records in these map requests. Routes and animations are rendered in your browser. Vehicle models are served from FeiLog itself. You can switch back to the outline background.

Share images, postcards and videos. Share cards, footprint postcards and journey videos are created in your browser and are not uploaded by FeiLog. What you do with the file afterwards is up to you.

Export. While signed in, you can export your records from Settings as JSON, CSV or XLSX. JSON archives can be restored into an active FeiLog account; restore adds records without replacing existing records.

Deleting your account. Use Settings → Delete FeiLog account to remove your trip records, payments, import records and export snapshots from the active FeiLog database. This keeps your application and review history, the shared Supabase sign-in identity, and a deleted-account marker that prevents automatic reopening without a new approval. Account deletion does not automatically remove these retained records, email-delivery or platform logs, existing database backups, or copies you have downloaded. Restricted accounts retain export and deletion access after signing in, but cannot change trip data. Signing out or uninstalling the Chrome extension does not delete your FeiLog account.

To withdraw an application or request access, correction or deletion of retained personal information, contact [email protected].

Use. FeiLog data is used only to provide FeiLog to you. It is not used for advertising, is not sold, and is not combined with the extension's availability pool.

Hosting. The website is served by Cloudflare Pages and the database and authentication run on Supabase; both providers process connection metadata (such as IP addresses) under their own policies.

7. Changes

If this policy changes materially we will update this page and the effective date above. Questions, deletion requests and security reports: [email protected]. Alert digests are sent from [email protected]; that address is for outgoing mail only.

Extension summary: we collect flight-availability data from your own searches plus an optional email/Telegram contact for alerts (and, unless you turn it off, FeiFinder product news), and a daily count of which extension versions are in use, as listed in full in section 1. Local processing, no credential access, no data sales, delete on request.