Privacy Policy

Optional email subscription

When email forms are enabled, you can choose to send FlyingWith your email address, language and signup placement (for example, homepage or packing tool) through Brevo. We use these to send a confirmation message, a free checklist link and the travel tips you requested. You must confirm the subscription by email before joining the mailing list, and can unsubscribe using the link in a message. We record the consent version with the provider. Your personalized checklist, saved trip answers, medical needs and shared-trip link are not sent with a signup or linked to your email. No email form is shown until the provider and localized confirmation templates are configured. Subscription data stays with the provider until you unsubscribe or request deletion, subject to its suppression and legal recordkeeping settings. Contact FlyingWith through the privacy contact listed below to request access or deletion.

Careers and the talent pool

If you join the FlyingWith talent pool through the careers page, you send us your first and last name, email address, the role you are interested in, an optional portfolio or profile link, and an optional short message, through Brevo. We use them only to consider you for future roles and to contact you if a matching role opens. Joining the pool is not an application for an open position: FlyingWith states on the page when it is not actively hiring. We keep talent pool applications for up to 12 months and then delete them. They are never added to the marketing newsletter, never shared or sold, and never used for advertising. We record the consent version with the provider. To see, correct or delete your application at any time, contact FlyingWith at info@flyingwith.com. While the online form is being switched on, applications are also accepted by email at info@flyingwith.com; emailed applications follow the same rules: used only for future roles, kept for up to 12 months, then deleted.

Information we collect

You can browse FlyingWith and use its free tools without an account. Optional usage analytics starts only after you select Allow analytics. Vercel Web Analytics records visit times, public page paths, referring domains, browser and operating-system versions, device type, script version and approximate location, including city. It derives a temporary visitor hash from incoming request details, which include the IP address. It uses no cookies and discards visitor sessions after 24 hours. When a Google Analytics 4 property is configured, it also measures public page visits, partner clicks, search submissions, tool completion and confirmation-email requests. Email addresses, typed destinations, travel dates, planner answers, baggage measurements and private shared-trip links are not included in analytics. Health-related page paths and their campaign/sub-ID details are omitted or reduced to the language homepage. Only allowlisted public social-source labels are retained for attribution; arbitrary URL queries and fragments are removed. We do not enable advertising signals or personalized advertising. Reporting retention is controlled in the analytics providers’ account settings.

How we use information

We use the limited information we collect to operate, maintain and improve FlyingWith: for example, understanding which travel scenarios are most useful to visitors, fixing broken pages, and deciding what to build next. We do not sell your information, and we do not currently use it for targeted advertising.

Cookies and similar technologies

Analytics is off until you choose to allow it. Your consent choice and its date are kept in this browser for up to 180 days; you can change the choice below. When Google Analytics is configured and allowed, its measurement cookies can last up to 180 days. Choosing Essential only disables future measurement and removes Google Analytics cookies set for this site. Vercel Web Analytics does not use cookies. Planning features keep their answers on this device as described in the tool and offline-storage sections. A manual booking-currency preference and an allowlisted social-source label can be kept in this tab’s session storage; clearing site data removes them. Partner websites may set their own referral cookies after you follow a partner link; their privacy policies apply there.

Affiliate links and third-party partners

FlyingWith uses Travelpayouts referral links to Trip.com, Airalo, Yesim, GetTransfer and AirHelp. We may earn a commission on an eligible booking, purchase or paid service. A referral code describes the public placement, language and coarse device class; it does not contain planner answers, private trip links or claim documents. The provider handles payment and support under its own terms and privacy policy. FlyingWith also uses Stay22 accommodation search links and optional maps. Their selected search details and explicit load behavior are described below. Campaigns describe only the public page, known destination ID or worldwide category, language and optional app channel. They never contain a visitor’s typed place, dates, guest details or private travel data. The embedded Trip.com form retains the provider’s approved tracking code.

Flight search widget

The booking page embeds the Trip.com flight-search form supplied by Travelpayouts. When it loads, your browser connects to the widget provider and its airport-suggestion services; they receive technical request data such as your IP address. Airport text is sent to the suggestion service as you type. Searching sends your selected airports, dates, passenger counts and cabin class, plus the referral identifier, to Travelpayouts and Trip.com. The widget runs in a separate sandbox that cannot read FlyingWith’s browser storage, planner answers, expense data or other page fields. Trip.com opens in a separate tab with its own privacy policy and cookies. FlyingWith does not receive your flight-search fields, booking details or payment information from this form. The optional nearby-airport helper uses browser location only with permission (including an existing grant). It compares coordinates on your device with our public airport directory; FlyingWith does not store them or transmit them to a server, analytics service or flight provider. Choosing an airport sends its code to the isolated form. The helper locks once you start using the form, so location results cannot replace your entries.

App and offline storage

Adding FlyingWith to your home screen is optional and free. Your app opens in the language of its installation address; we do not set a language cookie. A local preference records that the one-time install suggestion has appeared, and session storage records an app launch for the current tab. Guides are saved only when you select “Save for offline”. Public reading copies and a limited number of their images remain in this browser’s cache until you remove them, clear site data, or the browser evicts them. Anyone using this browser can see these saved guides. Copies show their save date and may be out of date; they do not include checklist answers, booking forms or shared-trip data. App support files and the baggage calculator are also cached for offline use. When you choose to refresh for an update, a temporary copy of an unfinished planner or baggage form may be kept in session storage, restored once, and then removed; unused copies expire after ten minutes. Other unfinished forms are not copied automatically. The installed app does not request notification permission or monitor flight or hotel prices.

Shared trip expense tracker: what we store

If you use the shared trip expense tool, we store what you and your group enter: the trip name and main currency, the names of the people you add, and each expense's description, amount, currency, category, who paid and how it was split. We also store the date the trip was created, the date it's set to expire, the trip's share-link token, and a one-way hash of its owner key (never the key itself). You don't need an account, and we don't ask for email addresses. Please use first names or nicknames, and don't put sensitive information in trip or expense names. The tool doesn't process payments.

Who can access a shared trip

Access is based on links, not accounts. Anyone who has a trip's share link can view the trip and add people and expenses, so share it only with your group. When you create a trip, your browser receives a separate owner key, kept only in that browser's local storage. Only that key can edit or delete expenses, replace the share link, or delete the trip, and it's sent to us in a request header, never in a link. If that browser's data is cleared, or you switch devices, the owner key can't be recovered or reissued: without accounts, we have no reliable way to confirm who created a trip, so we won't hand owner controls to anyone who asks. Trips created before owner keys were introduced (September 2026) don't have one, so their link can't be replaced and they can't be deleted from the trip page.

How long trip data is kept

A trip stays available for 90 days after its last change. The changes that restart this period are creating the trip, adding a person, adding, editing or deleting an expense, and replacing the share link. Simply opening or viewing a trip doesn't restart it, so visits to a link, including by automated crawlers, don't keep a trip alive. Once a trip reaches 90 days without changes, it can no longer be opened, and a scheduled job that runs once a day permanently deletes it along with its people and expenses, normally within about a day. The trip's owner can also delete it at any time from the trip page. Deleted data may remain for a limited time in our database provider's short-term recovery backups before those are overwritten.

Security and abuse prevention

To limit abuse of the trip tool, we count recent requests per connection. To do that, we store a one-way hash of your IP address made with a secret key, along with a counter, and delete these records after about a day. The IP address itself is not stored. Our hosting provider (Vercel) processes technical request data, such as IP addresses and requested URLs (which can include trip links), to deliver and secure the service, under its own retention policies. Trip data is stored with our database provider (Neon).

How we share information

We do not sell or rent your personal information. Our analytics are processed by Vercel, our hosting provider, on our behalf; we share them with no one else, and they are aggregated so that they cannot identify an individual visitor. We may disclose information if required by law.

Data retention and security

Our analytics results are aggregated and held by Vercel on our behalf, under its own retention policies: no persistent identifier is stored, and there is nothing in them that singles out an individual visitor. Shared trip data follows the 90-day inactivity rule described above. No method of transmission or storage is completely secure, and we can’t guarantee absolute security.

Children's privacy

FlyingWith is not directed at children, and we do not knowingly collect personal information from children under 13 (or the applicable age of digital consent in your region). If you believe a child has provided us with personal information, please contact us and we'll remove it.

Your privacy rights

If you are located in Quebec or elsewhere in Canada, provincial and federal privacy laws, including Quebec's Act respecting the protection of personal information in the private sector (Law 25) and the federal PIPEDA, may give you rights to access, correct, or request deletion of personal information we hold about you. If you're located elsewhere, similar rights may apply under your local law (such as the GDPR in the EU/EEA). Because trips aren't tied to accounts or email addresses, we may need a trip's link to find its data. Never send us an owner key. To make a request, see the privacy section of our Contact page.

International visitors

FlyingWith is based in Quebec, Canada, and welcomes visitors worldwide. If you access the site from outside Canada, your information (limited as it is) may be processed in Canada or in the countries where our service providers operate.

Changes to this policy

We may update this Privacy Policy as FlyingWith grows, for example when we add booking accounts, payments, or new analytics tools. We'll update the "Last updated" date above when we do, and for significant changes, we'll make that clear on the site.

Person responsible for the protection of personal information

At FlyingWith, the protection of personal information is the responsibility of our Privacy Officer. Contact information for this role is provided on our Contact page.

My packing list

Your list stays in this tab unless you choose to save it on this device. Anyone using this browser can see a saved device copy. Browser storage can be cleared. Download a PDF to read later or a restore file to edit on another device; both include your own items and should stay private.

Search and data-saving preferences

Site search downloads a public catalogue for your language when you open it. Matching happens in your browser; your query is not sent with that request. The data-saving setting is stored only in this browser under flyingwith:connection:v1. Automatic mode reads supported browser connection hints to pause optional map downloads and motion on constrained connections. It does not collect your country or location. You can change or reset the setting in the footer. If browser storage is blocked, the choice lasts only for this session.

Optional saved packing lists and disruption checks

The packing-list and flight-disruption tools keep their current state in this tab’s session storage. If you select “Save for another visit on this device”, the tool also writes its own copy to this browser’s local storage. This can include packing choices, custom packing text, a departure date, the selected disruption type and checked steps. These tool states are not sent to FlyingWith or a booking partner. Anyone using the browser can see a saved copy. Turning saving off removes that tool’s device copy; clearing the packing list removes its tab and device copies. Browser storage can be blocked or cleared. PDF and backup downloads contain the state you choose to export and should be kept private.

Preparation checks and accommodation dates

When you tick a booking or scenario preparation checklist, this tab keeps the checklist text and checked positions under flyingwith:visitor-checks:v1. This records only your explicit checks, not pages you visit. Clear the checks to remove that checklist’s entry. Changed checklist text invalidates previous checks.

If you choose “Keep these dates in this tab”, flyingwith:stay-dates:v1 stores only your accommodation check-in and check-out dates. They can be reused across public accommodation search pages and languages. Uncheck that option or clear the dates to remove the saved dates. A selected destination, scenario, search question or cost comparison is not stored by these features.

Both entries use sessionStorage, which normally lasts for the tab; browser session restore may recover it. Nothing is uploaded to FlyingWith. Only your chosen destination and dates are sent to the accommodation provider when you follow its labelled booking link. Copying a comparison sends it to your clipboard so you can decide where to paste it.

eSIM and airport pickup planning

The travel eSIM tool and pickup questions hold your answers only in the current page’s memory. They do not save a device record or send the answers to a provider. You can explicitly copy or download an eSIM shopping list; those actions create a local copy you control. Clearing the eSIM answers does not clear any other planning tool or trip ownership key.

Approved affiliate links can include a public social-source label when the current URL names TikTok, YouTube, Instagram, Facebook or Pinterest. Only that allowlisted label is added to the existing attribution code; other query values and full referrers are not retained by this feature. The affiliate network’s reports record eligible clicks and transactions under its own policies. A site click does not establish an approved commission.

Your exploration board

The exploration board keeps only explicitly saved public guide/destination IDs, a selected reading trail and manually marked reading steps. It uses page memory until you opt in to saving on this device under flyingwith:explore-board:v1 in localStorage. Saved links can reveal your travel interests to other people using this device. Turning device saving off or using Reset board removes this key; other tools, offline reading copies and expense ownership are preserved. Cross-tab changes synchronize this board. No account, passive visit history, search text, quiz answers, flight dates, booking references or tracking requests are added. Clipboard and text downloads contain the selected public links and reading progress only.

Accommodation search and maps

Destination suggestions and country matching run in your browser. You can select a city, town, village or area, including places outside our suggestion catalogue. An explicit homepage-to-booking handoff keeps one chosen place in page memory, without putting it in the URL or browser storage. Guest counts, child ages and currency remain on the page. Only accommodation dates can be kept in the tab when you choose the existing date-saving option. Opening booking results sends the selected place, optional dates, adult count, child count and ages, currency, language and public campaign to Stay22. Loading the optional embedded accommodation map sends the selected place, optional dates, guest counts, currency, language and public campaign; the map does not receive child ages. The map is never loaded automatically. Stay22 and its embedded services may use their own cookies and privacy policies. Changing the place, dates or guest preferences closes an open map, so it needs an explicit new load. These values are never added to FlyingWith analytics events or campaign labels.