Skip to content
  • How it works
  • Itinerary
  • Trip tools
  • Questions
  • Blog

App privacy policy

Last updated 28 October 2026

This policy explains what personal data the FlyBees app collects, why, who else receives it, and what you can ask us to do with it. The website at flybeesapp.com has its own privacy notice.

Who runs FlyBees

FlyBees is run by Het Dave, an individual based in Ahmedabad, Gujarat, India. FlyBees is not a registered company. In this policy, “FlyBees”, “we” and “us” mean Het Dave.

For anything about your personal data, write to [email protected]. Het Dave reads and answers these messages, and replies within 30 days.

The FlyBees app is for people aged 18 or over.

What we collect, and why

Your account

  • Your email address, to create your account and sign you in.
  • Your password. It goes from the app straight to Firebase Authentication, our sign-in provider, and never reaches our servers.
  • Whether you have confirmed your email address. Firebase sends the confirmation email, and any password reset email you ask for.

Your profile

The details you add to your profile: your name, phone number, preferred way to be contacted, profile photo, nationality, passport country, home city, travel styles, how often you travel, budget range, favourite destinations, diet and lifestyle, languages and any accessibility needs.

We use them to show your profile to you and to shape the plans FlyBees makes for you. Planning with AI, below, explains which of them are sent to Anthropic and TypeSafe.

Trips, itineraries, checklists and expenses

  • The trips FlyBees plans with you: destinations, dates, who is travelling, the day-by-day itinerary, its activities and places, and any changes you make.
  • Your checklist items, including any you type yourself.
  • The expenses you record (amount, currency, category, date and description) and your trip budget.

We use them to keep each trip in one place and show it to you before and during the trip.

Documents and the vault

  • The files you upload, such as tickets, bookings or a copy of your passport, with their names and categories. They are stored in Firebase Cloud Storage.
  • If you turn on Lock documents, your phone asks for your face, fingerprint or passcode before the app shows your documents. The setting and the check stay on your phone; we receive neither.

No AI reads your documents. Their contents, names and categories are never sent to an AI provider.

Chat with AI

  • Your messages and the replies, saved so that you can return to a conversation.
  • A usage record for each AI request: the feature, the provider, how much it used, its estimated cost and the date. Usage records hold nothing you wrote. We use them to keep a daily limit on AI use and to watch our costs.
  • A record of each time you agree to AI trip planning or turn it off, so that we can show what you agreed to.

Feedback

When you tap the heart or the thumbs-down on a place in an itinerary, we record that choice with the trip and the place, to make better suggestions.

Maps and place search

  • When you type your home city, or search for a place to add to a trip, the app sends what you type to our servers, which ask Google to suggest matching places.
  • The maps in the app come from Google Maps, which receives the places shown on them. Place details come from Google too.
  • Our servers ask Google for routes and travel times between the places in your trip. These requests carry only the places and the way you are travelling.
  • Because the app loads its maps and place details from Google directly, Google also receives your device’s IP address.

App updates

The app checks with Expo for updates. Expo receives a random ID created for your copy of the app, your platform (iOS or Android) and the app version. Like any server the app contacts, it also receives your IP address.

Planning with AI

FlyBees uses two AI providers in the United States. Anthropic plans trips, builds and changes itineraries, suggests checklist items and answers your travel questions. TypeSafe works out what each message asks for and which places best suit your trip. Nothing is sent to either until you agree.

What Anthropic receives

  • your messages and change requests, with the earlier messages in the same conversation
  • trip details: places, dates, travellers, activities and checklist items
  • profile details: home city, travel styles, budget, favourite destinations, diet and lifestyle, languages and mobility needs

FlyBees does not add your email, phone number, nationality, passport details or documents. Anything you type is sent as you wrote it, so leave out anything a plan does not need.

To answer some questions, Anthropic searches the web. It writes those searches from your request, and they can include the country you live in.

What TypeSafe receives

  • each message you send, with the reply before it
  • trip details: the cities, days and activities of your trip, and the places FlyBees found for it
  • trip preferences from your messages and profile: interests, pace, who is travelling (including children’s ages), diet, mobility needs, budget, the kinds of places you like, places to see or avoid, and other notes about the trip

TypeSafe uses them to work out what you are asking for and which places suit you.

What Google receives

To find real places and routes, FlyBees and Anthropic write place searches that FlyBees sends to Google Maps. These searches can include details sent to Anthropic, such as your home city, your diet (for example “halal friendly” restaurants) or your mobility needs. When you ask to change an activity or name a hotel, what you type is sent to Google as you wrote it. The searches carry no account ID or contact details.

What Langfuse receives

Langfuse, a monitoring service in the United States, receives about 1 in 10 chat requests, so that we can check how well the AI works: your account ID, the conversation ID, your messages (including earlier ones in the conversation), the replies, the web, place and route searches made for them, and usage counts. It does not receive your profile or saved trips as such, but messages, replies and searches can mention details from them.

How Anthropic and TypeSafe handle it

Neither provider trains its models on this data. Anthropic deletes it within 30 days, unless it must keep it longer to enforce its usage policy (up to 2 years for a request its safety systems flag) or to comply with the law. TypeSafe keeps it for as long as it reasonably needs to run its service, and sets no fixed period.

Agreeing, and turning it off

Before FlyBees first sends anything to Anthropic or TypeSafe, the app shows you what is sent and to whom, and asks you to agree. You can turn this off at any time in You > AI trip planning, and turn it on again in the same place. Once it is off, from your next request FlyBees sends nothing to Anthropic or TypeSafe, and makes no AI place searches for Google. Turning it off does not affect what was sent before.

Without it, your saved trips, documents, checklists and expenses keep working. Chatting in Plan and planning a new trip need it, and so do AI changes to activities and AI checklist suggestions.

Sensitive information

Two details you may give FlyBees are sensitive:

  • Your diet can reveal your religion, for example if you choose halal.
  • Mobility or accessibility needs reveal something about your health.

If you add them, both are sent to Anthropic and TypeSafe to shape your plans, and both can appear in place searches sent to Google. You do not have to add either; FlyBees can plan without them.

Who processes your data for us

These providers process personal data on our behalf, under their own terms. They are required to protect it to the same standard as this policy.

  • Anthropic (United States): plans trips, changes activities, suggests checklist items and answers questions, as described in Planning with AI.
  • TypeSafe (United States): works out what each message asks for and which places best suit your trip, as described in Planning with AI.
  • Firebase Authentication (Google): your account and sign-in, and the emails that confirm your address or reset your password.
  • Firebase Cloud Storage (Google): your documents and profile photo.
  • Google Maps Platform (Google): place search and place details (Places), city locations (Geocoding), routes and travel times (Routes), the maps in the app, and place suggestions as you type.
  • DigitalOcean: hosts our servers and database. Our planned hosting is a DigitalOcean droplet and DigitalOcean Managed PostgreSQL.
  • Langfuse (United States region): monitors how well the AI performs. In the released app it receives about 1 in 10 chat requests, as described in Planning with AI.
  • Expo (United States): app update checks. It receives a random ID for your copy of the app, your platform and the app version.
  • Cloudflare, Inc. (United States): forwards email sent to [email protected], and may process it in data centres outside India.
  • Our email provider: receives the messages forwarded from [email protected], so that we can read and answer them.

Data that leaves India

Most of these providers are based in the United States, and they may process your data there or in other countries outside India. We transfer personal data outside India only as Indian law allows.

How long we keep it

  • Account, profile, trips, itineraries, checklists, expenses and documents: until you delete them (or ask us to) or delete your account.
  • Chats, feedback and AI consent records: until you delete your account.
  • AI working records: the reply stream of each request, deleted soon after it is a day old; TypeSafe’s decisions about each request (what it asks for, how places rank), which hold no message text, deleted soon after they are 90 days old; and the assistant’s memory of each conversation, kept until you delete your account.
  • Usage records: these hold no content. Each is deleted after 90 days. When you delete your account, they are unlinked from you.
  • A deleted account’s ID: kept for at least a day, so that an old sign-in cannot create the account again.
  • Emails you send us: for as long as we need them to deal with your request.
  • Anthropic: deletes what it receives within 30 days, unless it must keep it longer to enforce its usage policy or by law.
  • TypeSafe: keeps what it receives for as long as it reasonably needs to, with no fixed period.
  • Langfuse: keeps its monitoring records until we delete them. They can include the messages and replies of the requests it receives.

Your rights

You can ask us at any time to:

  • tell you what personal data we hold about you, how we use it, and which providers have received it;
  • correct it or bring it up to date;
  • delete it;
  • stop using it, by withdrawing your consent. Withdrawing is as easy as giving it, and does not affect what we did before you withdrew;
  • let someone else exercise these rights for you if you die or become unable to.

You can do much of this in the app:

  • See and correct your profile: in You.
  • Delete a document, an expense or a checklist item: where it appears in the app.
  • Turn off AI trip planning: You > AI trip planning.
  • Delete your account: You > Delete account.

For anything else, such as a copy of your data or deleting a single trip or chat, write to [email protected] from the email address on your FlyBees account, so that we can find it. We reply within 30 days, and usually much sooner.

If you are not satisfied with our answer, you can complain to the Data Protection Board of India.

Delete your account

In the app: open You and tap Delete account. The app asks for your password, then deletes your account.

Without the app: write to [email protected] from the email address you use for FlyBees, and say that you want your FlyBees account deleted. You do not need the app for this. We reply within 30 days and tell you when it is done.

We delete your sign-in, profile and photo, trips, itineraries, checklists, expenses, documents, chats, feedback and AI consent records.

We keep:

  • usage records, unlinked from you, until they are deleted at 90 days;
  • your account ID, for at least a day, so that an old sign-in cannot create the account again;
  • copies our providers already hold, for as long as they keep them: Anthropic for up to 30 days (longer only to enforce its usage policy or as the law requires), TypeSafe for as long as it reasonably needs them, and Langfuse’s monitoring records until we delete them.

Children

The FlyBees app is for people aged 18 or over. If you are under 18, please do not use it. If we learn that we hold a child’s personal data, we delete it.

Security

  • The app talks to our servers over an encrypted connection (HTTPS).
  • Our servers check your sign-in token on every request.
  • Your documents are kept in private storage. The app opens each one through a link that expires after an hour.
  • Lock documents, if you turn it on, uses your phone’s own face, fingerprint or passcode check.

If a breach affects your personal data, we will tell you, and the Data Protection Board of India, as Indian law requires.

No ads, no tracking, no selling

FlyBees shows no ads and does not track you across other companies’ apps or websites. We never sell your personal data.

The law we follow

We handle personal data in line with Indian data protection law, including the Digital Personal Data Protection Act, 2023.

Changes to this policy

When this policy changes, the date at the top changes too. If we change what FlyBees sends to an AI provider, or which provider receives it, the app asks for your consent again first.

  • Privacy
  • Terms

Contact: [email protected]

© 2026 FlyBees