Skip to content

Privacy Policy

Last updated: October 2, 2026

Velocity Digital Labs LLC (“we”, “us”) operates fairtravels.ai (the “Site”): destination guides, a travel blog, an AI travel assistant, Fai, where it appears on the Site, and, where checkout is offered, flights we arrange and take payment for. This policy explains what personal information we collect, how we use and share it, how long we keep it, and the choices and rights you have. It also covers our own fairtravels.ai accounts on social platforms (section 1).

The controller responsible for your personal information is Velocity Digital Labs LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, United States. Contact us at privacy@fairtravels.ai or through our privacy request form.

1. Information we collect

What you give us

  • Account: Your name, email address and password (stored only as a one-way hash, never in plain text). If you sign in with Google, we receive your name, email address and profile photo from Google, and keep your name and email address.
  • Profile: An optional phone number, and the country and language settings of your account.
  • Saved travellers: For you and people you choose to save with their permission — names as on the passport, title, date of birth, gender as on the travel document, nationality, passport number, expiry and issuing country, and optionally their own email and phone, Known Traveler and redress numbers, frequent-flyer numbers, and seat and meal preferences. A meal preference can reveal religious beliefs or health information: it is optional, shown only to you, and not currently sent to airlines.
  • Chats with Fai: The messages you send Fai, our AI travel assistant, and its replies.
  • Voice input: If you use the microphone button in the chat or the trip planner, we receive only the text your browser makes from your voice, as if you had typed it.
  • Searches: What you search for on the Site, linked to your account if you are signed in.
  • Booking data: If you book through checkout, your travel dates, flights and booking history; passenger details, including passport and ID details when the route requires them; the booking contact's email and phone; and where you live (your country and, in the US, your state), which we ask to check that we can sell to you.
  • Payment information: Processed securely by Razorpay if your account region is India, or by Stripe for all other accounts. When you pay through Stripe, you enter your billing address on Stripe's payment page; Stripe uses it to verify the payment and to calculate any sales tax. We do not keep your card numbers, bank account details, UPI IDs or billing address in our booking systems. Stripe holds your billing address, and the tax reports Stripe provides to us, which include the address used to calculate tax, are kept with our tax records. When Stripe confirms a payment, we also check the state in the billing address, only to confirm we can sell to you. We don't store the address from this check, only whether it let the payment through; the tax areas Stripe reports, which can include your state, are kept with your booking records.
  • Messages: What you send us, including support messages and privacy requests.

What we collect automatically

  • Technical data: With every request to the Site, your IP address, browser and device type, the page and the time, which we use to deliver the Site, keep it secure, limit abuse and fix faults, and work out which country you're in, to know whether to ask before analytics run (section 4).
  • Server monitoring: When your browser asks our servers for a page, they send JustAnalytics the path of that page request (the part of its address after fairtravels.ai, up to any "?", which can include a booking or other record number), the request method, the host name your browser asked for, your browser's user-agent string, the response status and timing, the addresses our servers call while handling the request, and details of any server error (its message and technical trace, sent as they are), which can quote a page address or other parts of the request. Requests whose address carries query details, such as a search term or a sign-in link's token, are not sent, though a server error's details can still quote such an address. A request whose only query is a technical one the Site adds as you move between pages is sent without that query. Your IP address is not sent, and nothing is stored on your device.
  • Browser error reports: If a page fails, your browser sends our servers the error and the page address without any query string. We remove email addresses, IDs and long numbers from them where we can, and nothing is stored on your device.
  • Browser analytics (JustAnalytics): The pages you visit (their full address, including anything after "?", and their title) and how long you spend on them, the page that referred you and any campaign tags in the link, page speed, errors in your browser, signs that clicks aren't working (the clicked element's technical description and where on the screen you clicked), and your browser type, language, time zone and screen size. JustAnalytics collects these with a random identifier stored in your browser and an identifier calculated from your browser and device characteristics, and receives your IP address. Section 4 says when browser analytics run.
  • Browser analytics (Google Analytics): Google Analytics, an analytics service run by Google, also collects browser analytics on the Site. It records the full address of each page you visit (including anything after "?", apart from the values it removes, below) and its title, how long you spend on it, the page that referred you and any campaign tags in the link, and your browser, device, operating system, language and screen size. It also records when you scroll to the bottom of a page, click a link to another site, search the Site, watch an embedded YouTube video or download a file, and these actions, with these details as well as the page details above:
    • Starting a trip plan: where on the Site you started it, how you entered your request (for example, typed or spoken) and, if you started from a link that already names them, the destination and number of days.
    • Searching for flights: the city or airport code your search was matched to (or that it couldn't be matched), never the words you typed; whether the trip is one-way or return; the number of travellers; whether you searched with the form or in your own words; how many results were shown; and whether booking was open.
    • Booking, where checkout is offered: choosing a flight, adding it to your booking, starting checkout, going on to payment and completing the booking, with the route, flight, price per traveller, number of adult travellers, total value, currency, payment type and your booking reference, and whether you picked the flight from search results or a chat.
    • Creating an account or signing in: only the method you used, such as email or Google.
    • Using a share button: which network and which post you shared.
    • Clicking a contact email link: only the type of contact, such as support.

    We do not send Google Analytics the text of your chats with Fai, or the names, email addresses, phone numbers or passport details of you or the travellers you add. It is set up to remove email addresses, and the values of the token, callbackUrl and session_id parts of a page address, before anything is sent. Google Analytics collects these with a random identifier stored in a cookie in your browser. As with any site your browser contacts, Google receives your IP address. Google says Google Analytics uses it to work out your approximate location, down to your city, and to protect its service, and then discards it. Section 4 says when Google Analytics runs, and the pages where it never does.

What we receive from others

Booking status, ticket numbers and schedule changes from airlines and our booking partner, Duffel; confirmation of your payment, the tax charged, the tax areas it applies to and the state in your billing address from Stripe; and your name and email address from Google, if you sign in with it.

Our accounts on social platforms

We run our own fairtravels.ai accounts on X, Facebook, Instagram, Threads, Pinterest and LinkedIn, and publish to them through each platform's API (the connection a platform offers apps). We use these connections only to publish our own posts. When we publish, the platform sends back details of the post, such as its ID, its web address and whether it was published. We do not use these connections to collect our followers' personal information.

The platforms also show us statistics about our accounts and posts, such as how many people saw or interacted with a post, in summary form. For our Facebook Page, Meta provides these statistics under its Page Insights Controller Addendum (https://www.facebook.com/legal/terms/page_controller_addendum), and for our LinkedIn page, LinkedIn provides them under its Page Insights Joint Controller Addendum (https://www.linkedin.com/legal/l/page-joint-controller-addendum). Under these, Meta and LinkedIn take responsibility for meeting the GDPR's obligations for these statistics, including answering people's requests about them. What you do on a platform, such as following, messaging or commenting on our accounts, is covered by that platform's own privacy policy. To ask us to delete personal information, see "How to delete your data" in section 7.

2. How we use it, and our legal bases

We use personal information for the purposes below. For people in the EU and UK, the table also gives the legal basis we rely on for each.

How we use personal information, and the legal basis for people in the EU and UK

Purpose
Your account
Legal basis (EU and UK)
Contract: to provide the account you ask for.
Purpose
Bookings made through checkout, and messages about them
Legal basis (EU and UK)
Contract. Passport and ID details also help the airline meet its legal duties.
Purpose
Saved travellers
Legal basis (EU and UK)
Contract, for your own details. For people you save, our legitimate interest in providing the feature you ask for, relying on your confirmation that you have their permission. A meal preference is optional: you choose whether to add one, and can remove it at any time in Profile > Travellers.
Purpose
Chats with Fai
Legal basis (EU and UK)
Contract, if you have an account; otherwise our legitimate interest in answering the questions you ask.
Purpose
Searches
Legal basis (EU and UK)
Legitimate interests: running search and understanding how it is used.
Purpose
Checking whether we can sell to you
Legal basis (EU and UK)
Legitimate interests: following US state laws on who may sell travel to their residents.
Purpose
Tax and accounting records
Legal basis (EU and UK)
Legal obligation; for obligations outside the EU and UK, our legitimate interest in meeting them.
Purpose
Security, preventing abuse, server monitoring and fixing faults
Legal basis (EU and UK)
Legitimate interests: keeping the Site working and secure.
Purpose
Browser analytics (JustAnalytics): understanding how the Site is used and fixing faults
Legal basis (EU and UK)
Consent: in the UK, Switzerland and the European Economic Area, browser analytics run only after you accept them in our cookie banner, and you can withdraw your consent at any time with Cookie settings (section 4).
Purpose
Browser analytics (Google Analytics): understanding how the Site is used
Legal basis (EU and UK)
Consent: in the UK, Switzerland and the European Economic Area, browser analytics run only after you accept them in our cookie banner, and you can withdraw your consent at any time with Cookie settings (section 4).
Purpose
Working out which country you're in from your IP address, to know whether to ask before browser analytics run (section 4)
Legal basis (EU and UK)
Legitimate interests: knowing whether to ask you before browser analytics run.
Purpose
Our accounts on social platforms, and the statistics the platforms show us about them (section 1)
Legal basis (EU and UK)
Legitimate interests: presenting fairtravels.ai on social platforms and seeing how our posts do.
Purpose
Support and privacy requests
Legal basis (EU and UK)
Legal obligation, or our legitimate interest in answering you.
Purpose
Records of what you accepted or declared, and enforcing our terms
Legal basis (EU and UK)
Legitimate interests: showing what was agreed or declared, including for legal claims.

We don't use personal information for advertising.

3. Who we share it with

We share personal information with the organizations below, for the reasons given.

  • Payment processors: Stripe (all accounts outside India) and Razorpay (India) process your payments. They receive your payment details, and Stripe your billing address, directly and are governed by their own privacy policies. From Stripe we receive confirmation of the payment, the tax charged and the tax areas it applies to (the state and local areas such as county or city), which we keep with your booking records.
  • Travel suppliers: Airlines and our booking partner (Duffel) receive the traveller details needed to issue tickets, including passport and ID details when the route requires them, Known Traveler and redress numbers if you give them, and frequent-flyer numbers for the airline you fly.
  • AI services: Our assistant (Anthropic) processes your chat messages, including your search queries and preferences, to generate personalized suggestions. Traveller details you save in your profile or enter at the web checkout are sent directly to our systems, not to AI services. When you book in the chat, you enter traveller details in a secure card that sends them to our systems, not to the assistant, which sees only a short confirmation such as first names and last initials. Passport numbers and dates of birth we recognise in chat messages are removed before a message is stored or sent to the assistant. Please don't type passport, ID or card numbers into the chat. Payment card details you enter on our payment processors' pages never reach AI services.
  • Hosting and background tasks: Railway hosts the Site, its database and its cache; Inngest runs our background tasks, such as sending booking emails.
  • Emails: JustEmails (justemails.app), our own email service, run by Velocity Digital Labs LLC, sends the emails we send you.
  • Text and WhatsApp messages: If you give a phone number for a booking, we may send you booking updates by text message or WhatsApp; the company that delivers them receives your phone number and the message.
  • Analytics and monitoring: JustAnalytics (justanalytics.app), our own analytics and monitoring service, run by Velocity Digital Labs LLC: server monitoring of the path of each page request, as section 1 describes, and browser analytics as section 4 describes. Google Analytics, an analytics service run by Google LLC: browser analytics as sections 1 and 4 describe, including, where checkout is offered, the route, flight, price per traveller, number of adult travellers, total value, currency, payment type and booking reference of a booking. Google provides Google Analytics to us under its terms, and says that, with the data-sharing settings we have turned off, it uses this data only to provide, maintain and protect Google Analytics.
  • Sign-in: Google, if you choose to sign in with Google. This is separate from Google Analytics.
  • Maps and photos on guides: When a guide's map loads, your browser fetches map tiles from CARTO, a place outline from OpenStreetMap's Nominatim service, and photos from Unsplash and Cloudflare; each receives your IP address and browser details.
  • Voice input: If you use the microphone button, your browser's own speech service (for example Google in Chrome or Apple in Safari) turns your voice into text under its own privacy policy; we receive only the text.
  • Authorities and successors: Public authorities, when the law requires it; and, if our business is sold or reorganized, the buyer or successor, under this policy.

Airlines, Google (for sign-in), your browser's speech service, and the map and photo services use what they receive under their own privacy policies. Our Service providers and other recipients page lists them in more detail. We do not sell personal information or share it for cross-context behavioral advertising (section 7).

4. Cookies and similar technologies

We use cookies and similar technologies (your browser's local storage and session storage) that the Site needs to work: to sign you in, keep the Site secure, know whether to ask you about analytics, and remember choices you make, such as a light or dark theme or your cookie settings.

Browser analytics come from JustAnalytics, our own analytics service, and Google Analytics, an analytics service run by Google. Whether they run depends on where you are:

  • In the UK, Switzerland and the European Economic Area (EEA), including Réunion, Mayotte, Martinique, Guadeloupe, French Guiana, the French part of Saint-Martin and the Åland Islands, we ask first. Neither loads, and nothing is stored in your browser for analytics, until you click Accept in our cookie banner. If you click Reject, neither loads, and we clear any analytics data stored in your browser.
  • Everywhere else, there is no banner, and both load without asking first.

Wherever you are, Cookie settings, at the bottom of every page, lets you turn analytics off at any time, including after you have accepted them; that works like Reject. We remember your choice for 180 days. After that, in the UK, Switzerland and the EEA we ask again; elsewhere, analytics load again unless you turn them off again or your browser sends a Global Privacy Control or Do Not Track signal. Turning analytics off doesn't delete what they have already received: section 6 says how long that is kept, and section 7 how to ask us to delete it.

Our server works out which country you're in from your IP address, with a lookup it runs itself, so your IP address isn't sent to an outside service for this. If it can't tell, we ask first. A VPN can change the result.

Neither loads in your browser on our private pages: those at fairtravels.ai/admin, /agent, /profile, /booking, /reset-password, /verify-email and /privacy-request, and the pages under them. Google Analytics also doesn't run on a page whose address carries one of those addresses after the "?", such as a sign-in page that will take you back to your profile. Our private pages tell the next page you open, and any site you go to from them, only that you came from fairtravels.ai, not which page.

When they run, JustAnalytics stores a random identifier and details of your visit in your browser's local and session storage, and Google Analytics sets two cookies, one of them holding a random identifier. Our Cookie Policy lists each cookie and storage item.

  • We treat a Global Privacy Control or Do Not Track signal from your browser as a request to turn off browser analytics in that browser: neither JustAnalytics nor Google Analytics loads, wherever you are, and we don't show the cookie banner.
  • Providers that load content in your browser, such as the map and photo services on guides, receive technical data such as your IP address to deliver it.
  • We don't use advertising cookies or retargeting pixels. Google Analytics runs with its advertising settings off for every visitor, including those who accept analytics: it isn't linked to Google Ads, Google signals (which would add information from people's Google accounts) is off, and it is set not to store advertising cookies, personalize ads or send data for advertising.
  • Google describes how it uses information from sites that use its services in "How Google uses information from sites or apps that use our services" (https://policies.google.com/technologies/partner-sites). That page covers all of Google's services. On the Site, Google Analytics runs with the advertising settings above off and with its data-sharing settings off, and Google says it then uses the data only to provide, maintain and protect Google Analytics.

5. Security

  • We serve the Site over HTTPS.
  • If you set a password, we store only a bcrypt hash of it, never the password itself.
  • Passport, ID and frequent-flyer numbers and the contact details you save for travellers are encrypted at rest. Your profile never shows a document number in full: at most its last four characters.
  • You enter card details only on Stripe's or Razorpay's payment pages, so your full card number never reaches our servers.

No system is completely secure. If a breach affects your personal information, we will tell you and the authorities as the law requires. Our Security page says more.

6. How long we keep it

  • Your account: Kept while it is open. When you delete your account in Profile, it is closed at once. We remove your name, email, phone and chat history within 30 days, except records the law requires us to keep.
  • Saved travellers: Kept until you remove them in Profile > Travellers. Deleting your account deletes your saved travellers.
  • Booking records, including the tax amounts and tax areas our payment processor reports and the tax reports that include the billing address used to calculate tax: Retained for 7 years after the travel date to comply with tax and legal obligations.
  • Our activity log (account, booking and payment events, and where you said you live): Kept as long as needed to show what happened on your account and bookings, including for legal claims, and also after you delete your account. The Terms version you accepted for a booking is kept with that booking record, and so are activity-log entries the booking still shows, such as a refund that failed or an airline schedule change.
  • Records of privacy requests: At least 24 months.
  • Chats with Fai: Kept so you can continue a conversation, until you ask us to delete them; an account holder's chats are also removed when the deletion of the account is completed.
  • Searches: As long as needed to run search and understand how it is used. What Google Analytics receives about your searches is kept for the period given for Google Analytics under "Analytics, monitoring and server logs".
  • Analytics, monitoring and server logs: As long as needed to understand how the Site is used and to fix faults. Google Analytics keeps the data it collects, including the data tied to the identifier in its cookie, for 14 months, and Google then deletes it in a monthly clean-up. Totals in Google Analytics' standard reports, such as how many people visited a page, aren't affected by this limit.
  • Support messages: As long as needed to handle your request and meet our legal obligations.

7. Your rights and choices

Everyone

  • See and change your details in Profile. You can edit or remove any saved traveller, and any of their saved documents, at any time in Profile > Travellers.
  • Delete your account in Profile.
  • Ask us for a copy of your personal information, or ask us to correct or delete it.
  • Turn browser analytics off at any time with Cookie settings, at the bottom of every page (section 4).
  • We send service emails only, such as sign-in, booking and receipt emails. We don't send marketing emails.

To make a request, email privacy@fairtravels.ai or use our privacy request form, where we confirm it comes from you with a code we email you. We check that a request comes from you before we act on it, except an opt-out of sale or sharing sent by email, for which we don't ask you to prove who you are. We reply within 30 days. Someone you authorize can make a request for you, with proof that you authorized them. We won't treat you differently for using your privacy rights.

How to delete your data

You can delete your account in Profile. To ask us to delete your personal information, use our privacy request form at fairtravels.ai/privacy-request, or email privacy@fairtravels.ai. The form emails you a one-time code to confirm the request comes from you. Once we have confirmed a request, we delete the personal information we can find about you, except what section 6 says we keep, such as booking records.

Google Analytics data is tied to a random identifier in your browser, not to your account or email address. We can find it only if you send us that identifier, which is in the _ga cookie, or, for some bookings completed where checkout is offered, through the booking reference. JustAnalytics browser analytics data is tied to a random identifier stored in your browser, not to your account or email address, so we can find it only if you send us that identifier, which is kept as ja_visitor_id in your browser's local storage. Turning analytics off, or clearing your cookies and site data, removes both identifiers from your browser, so send them to us first if you want us to find that data. Deleting data from Google Analytics doesn't change totals in its standard reports, such as how many people visited a page.

The same route covers any request about our accounts on social platforms (section 1).

People in the EU and UK

You have the right to access, rectify and erase your personal information, to restrict or object to how we use it (including where we rely on legitimate interests), and to data portability. Where we rely on your consent, you can withdraw it at any time. You can complain to your data protection supervisory authority; in the UK, that is the Information Commissioner's Office (ICO), ico.org.uk. We reply within one month.

We rely on your consent for browser analytics: in the UK, Switzerland and the EEA, they run only if you accept them in our cookie banner, and you can withdraw your consent at any time with Cookie settings, at the bottom of every page (section 4). The rights above and the legal bases in section 2 also apply to people in Switzerland, Iceland, Liechtenstein and Norway. In Switzerland, your supervisory authority is the Federal Data Protection and Information Commissioner (FDPIC), edoeb.admin.ch.

Your California Privacy Rights

  • If you live in California, you can ask to know what personal information we collect, use and disclose, and ask us to delete or correct it.
  • We do not sell personal information or share it for cross-context behavioral advertising (as the CCPA defines "sell" and "share"), and we have not done so in the past 12 months. We do not knowingly sell or share the personal information of consumers under 16. See Do Not Sell or Share My Personal Information.
  • Passport and ID numbers are sensitive personal information. We use them only to provide the bookings you ask for, and we do not sell them or share them for advertising.
  • We use sensitive personal information only to provide the services you ask for, so there is no separate choice to limit its use.
  • Shine the Light: we do not disclose personal information to third parties for their own direct marketing purposes.

Notice at collection

The categories of personal information we collect, where each comes from, why we collect it, who we disclose it to and how long we keep it:

Personal information we collect

Category
Identifiers
Examples
Name, email address, phone number, account ID, booking reference, IP address, and the random browser identifiers browser analytics uses
Sources
You; your browser or device; Google, if you sign in with it
Purposes
Running your account and bookings, keeping the Site secure, service emails and messages, browser analytics, and checking which country you're in to know whether to ask before analytics run (section 4)
Disclosed to
Our hosting, email and messaging services; Anthropic (in chats); airlines and Duffel (for bookings); payment processors (for payments); JustAnalytics, our own analytics service; Google Analytics (your IP address, the random identifier in its cookie and, where checkout is offered, your booking reference); Google (if you sign in with it); map and photo services on guides (CARTO, OpenStreetMap Nominatim, Unsplash, Cloudflare), which receive your IP address
Kept
While your account is open, as section 6 explains; booking records 7 years after travel; what Google Analytics receives, as section 6 explains
Category
Personal records (Cal. Civ. Code § 1798.80(e))
Examples
Passport details, date of birth, contact details, and where you live (your country and, in the US, your state)
Sources
You; the state in the billing address you give Stripe
Purposes
Bookings, saved travellers, and checking whether we can sell to you
Disclosed to
Airlines and Duffel (for bookings); payment processors (your email address, for payments)
Kept
Saved travellers until you remove them; booking records 7 years after travel; where you live, as section 6 says for our activity log
Category
Characteristics protected under California or US law
Examples
Age (from a date of birth), gender as on the travel document, and nationality
Sources
You
Purposes
Bookings and saved travellers
Disclosed to
Airlines and Duffel (for bookings)
Kept
Saved travellers until you remove them; booking records 7 years after travel
Category
Commercial information
Examples
Bookings, payments, refunds and booking history
Sources
You; Stripe; airlines and Duffel
Purposes
Bookings, payments and refunds, tax and accounting records, and browser analytics (section 4)
Disclosed to
Payment processors; airlines and Duffel; Google Analytics (where checkout is offered, the route, flight, price per traveller, number of adult travellers, total value, currency, payment type and booking reference of a booking, and whether you picked the flight from search results or a chat)
Kept
7 years after travel; what Google Analytics receives, as section 6 explains
Category
Internet or other electronic network activity
Examples
Pages you visit, page speed and errors, searches you run, and your chats with Fai
Sources
Your browser or device; you
Purposes
Running the Site, keeping it secure and fixing faults, browser analytics (section 4), and answering your chats
Disclosed to
JustAnalytics, our own analytics service; Google Analytics (pages you visit, and the actions section 1 lists with their details, such as the city or airport code a flight search was matched to, whether the trip is one-way or return, the number of travellers, whether you used the form or your own words, how many results were shown, whether booking was open, and the network and post you share); Anthropic (chats); our hosting service; map and photo services on guides (which part of the map, and the destination, you view)
Kept
As section 6 says for each
Category
Geolocation data
Examples
Your approximate location: the country our server works out from your IP address, and the country, region and city Google Analytics works out from it
Sources
Your browser or device, from your IP address
Purposes
Knowing whether to ask before analytics run (section 4), and browser analytics
Disclosed to
Google Analytics, which works it out itself from your IP address
Kept
The country our server works out isn't kept, apart from whether to ask you, which the ft_cr cookie holds until you close your browser; what Google Analytics works out, as section 6 says
Category
Sensitive personal information
Examples
Passport and ID numbers, citizenship (the nationality on a travel document), your account sign-in details, and a meal preference
Sources
You
Purposes
Only to provide the services you ask for: bookings, saved travellers and signing in
Disclosed to
Airlines and Duffel (passport and ID details, and nationality, when the route requires them)
Kept
Saved travellers until you remove them; booking records 7 years after travel; sign-in details while your account is open

We do not collect precise geolocation, and we do not sell or share any category of personal information. Our hosting and background-task services (Railway and Inngest) handle all of these for us. The location in the Geolocation data row is approximate, worked out from your IP address.

Other US states

If you live in Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Florida or another US state with a consumer privacy law, you can ask to access, correct or delete your personal information, get a copy of it, and opt out of targeted advertising, the sale of personal information and profiling (we do none of these). If we decline your request, you can appeal by replying to our decision; we answer an appeal within 45 days. If we deny your appeal, you can contact your state attorney general.

Nevada

We do not sell covered information as Nevada law (NRS 603A) defines it. You can still send us an opt-out request at privacy@fairtravels.ai.

India

If you are in India, under the Digital Personal Data Protection Act, 2023, you can ask for a summary of your personal data and how we use it, ask us to correct, complete, update or erase it, and nominate someone to exercise these rights if you die or cannot do so yourself. For a grievance, contact privacy@fairtravels.ai; we respond within 30 days. You may also approach the Data Protection Board of India.

8. Children

Accounts are for adults. fairtravels.ai is not directed at children under the age of 18, and we do not knowingly let minors create an account.

A parent or guardian may save and book a child's travel details. When you save anyone other than yourself, you confirm that you have their permission, or that you are their parent or legal guardian. We use a child's details only for the bookings their parent or guardian asks for.

If you believe a child has created an account or given us personal data, please contact us and we will delete it promptly.

9. International transfers

We are based in the United States. If you use the Site from another country, your personal information is transferred to the United States, where we process it, and our service providers may process it in other countries.

Where the law requires a safeguard for personal information from the European Economic Area, the United Kingdom or Switzerland, we rely on the European Commission's Standard Contractual Clauses, with the UK International Data Transfer Addendum and the changes Swiss law requires, where a service provider's data processing terms incorporate them, or on an adequacy decision, such as the EU-US Data Privacy Framework, where a provider relies on it. To ask about these safeguards, email privacy@fairtravels.ai.

For Google Analytics, Google says that, when its advertising and analytics products are used, it relies on the EU-US Data Privacy Framework to transfer personal information from the European Economic Area to the United States and, in certain circumstances, on the Swiss-US Data Privacy Framework and the UK Extension to the EU-US Data Privacy Framework for personal information from Switzerland and the United Kingdom. Where no such framework applies, it may rely on Standard Contractual Clauses.

10. Fai, our AI travel assistant

Fai is an AI system, not a person, and its answers can be wrong: check visas, prices and availability before you rely on them. We store your conversations so you can continue them, and Anthropic processes them to generate Fai's replies (section 3).

11. Changes to this policy

We post every change to this policy on this page with a new date. If a material change affects how we use personal information you have already given us, we will email account holders or show a prominent notice on the Site before it applies to that information, and ask for your consent where the law requires it.

12. Contact us

Questions about this policy or your personal information: email privacy@fairtravels.ai or use our privacy request form. Our postal address is below.

Velocity Digital Labs LLC131 Continental Dr, Suite 305Newark, DE 19713United StatesEmail: privacy@fairtravels.ai