Flight

Privacy policy

Last updated 6 October 2026

Flight (“Flight”, “we”, “us”) runs Flight at askflight.io, a workspace where teams track their work, talk about it and see what is on time and what is slipping. This policy explains what personal information we collect when you use Flight, why, who it is shared with, how long we keep it, and the choices you have.

For account and workspace information you give us, we are the data controller. Where your organisation invites you into a space, the content of that space is also under its control.

Information we collect

Account details. Your name, email address, and your password (stored only as a one-way hash). If you add them: a profile photo, your time zone, two-factor authentication settings, passkeys, and your notification and display preferences.

Sign in with Google or GitHub. If you choose to sign in with Google or GitHub, we receive your name, your email address, whether that address is verified, and the account identifier the provider assigns you. We use these only to create your account and sign you in. We do not receive or store your Google or GitHub password, and we do not keep the access token the provider issues.

What you put into Flight. The spaces, matters, messages, comments, documents, files, plans, deadlines and decisions you and your team create, and any audio or video recordings you choose to make and attach.

Connected services you turn on. If you connect Relay channels (email, Telegram, WhatsApp, SMS or Discord), we store the address or account needed to reach you there and the messages that pass between you and Flight. If a space owner connects a work tool (GitHub, Figma or Google Drive), we store the access granted for that connection and the activity it reports about the repositories, projects, files or folders you link. If you subscribe to a calendar feed, we store its address and read its events. If you connect Google Calendar, we store the access you grant and the events described under Google user data.

Usage and device information. Server logs (including IP address and browser type) kept for security and troubleshooting, the time you were last active, and browser push subscriptions if you allow notifications. We count page visits using a keyed, one-way hash of a visitor rather than storing IP addresses in those counts.

How we use it

  • To create and secure your account, and to sign you in.
  • To run Flight for you and your team: showing, organising and searching your work, and delivering the notifications, reminders and summaries you ask for.
  • To provide Flight’s AI features, such as summaries, answers to your questions, drafted replies and voice commands, using the content those features need.
  • To keep Flight safe: preventing abuse, investigating problems and enforcing our rules.
  • To tell you about changes to Flight or to this policy.

We do not sell your personal information, we do not show advertising, and we do not use your information to build advertising profiles. Our legal bases are performing our contract with you, our legitimate interest in running and securing Flight, and your consent where we ask for it (for example, push notifications), which you can withdraw at any time.

Google user data

When you sign in with Google, Flight requests only the openid, email and profile scopes. We use your name, email address and Google account identifier solely to create your Flight account, sign you in and show your name to your team. We do not use Google user data for advertising, we do not sell it, we do not use it to train AI or machine-learning models, and we do not allow people to read it except with your permission, for security purposes, or where the law requires.

If you choose to connect Google Calendar, Flight also requests the https://www.googleapis.com/auth/calendar.events scope. We read the events on your primary calendar from the last 30 days to the next 180 days and store only each event’s title, start and end. They are shown to you alone, as busy time on your Flight calendar, and are used to find free time when Flight schedules its own events. We write to your calendar the time blocks you schedule in Flight and the deadlines and decisions you have chosen to see there, and we change or delete only events Flight itself created. The access Google grants is stored encrypted. Google Calendar data is not shared with your team and is not sent to AI service providers.

Flight’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect Google from Settings → Security → Connected accounts at any time. Google Calendar is disconnected from Calendar → Calendars → Disconnect: this revokes Flight’s access and deletes the events we read from Google, while events Flight wrote stay in your Google Calendar. You can also remove Flight’s access from your Google Account permissions.

Who we share it with

Your team. People in a space can see what is shared in that space, according to its visibility settings.

Service providers who process data for us under contract and only on our instructions:

  • Hosting and databases (our servers are in the United Kingdom).
  • Email delivery.
  • AI service providers, which process the content an AI feature needs in order to answer. We do not permit them to use your content to train their models.
  • Speech-to-text, for voice notes you send to Flight.
  • The messaging services you choose to connect (Telegram, WhatsApp and SMS carriers, Discord), and the browser vendors that deliver push notifications.

Services you connect. When you or a space owner connect Google, GitHub, Figma or Google Drive, information flows between Flight and that service as the connection requires, under that service’s own privacy policy.

The law. We may disclose information where required by law, or to protect the rights, property or safety of our users or others. If Flight is sold or merged, your information may transfer to the new owner under this policy.

Where a provider processes data outside the UK, we rely on appropriate safeguards such as the UK International Data Transfer Agreement or Standard Contractual Clauses.

Cookies

Flight uses only the cookies it needs to work: a session cookie that keeps you signed in, a security token that protects forms, and an optional “remember me” cookie. Your appearance setting is kept in your browser’s local storage. We do not use advertising or third-party tracking cookies.

How long we keep it

We keep your account information for as long as your account is open. You can delete your account from Settings at any time; your account details and connected sign-ins are then deleted, and remaining copies leave our backups as they cycle out. Content you contributed to a shared space may stay with that space, as part of its record, for as long as the space exists. Security logs are kept for a limited period and then deleted.

Security

All traffic to Flight is encrypted in transit. Passwords are stored as one-way hashes, and you can protect your account with two-factor authentication or a passkey. No system is perfectly secure, but we work to protect your information and will tell you if a breach affects you where the law requires.

Your rights

Depending on where you live, including under UK and EU data protection law, you have the right to access the personal information we hold about you, to correct it, to delete it, to receive a copy in a portable format, and to object to or restrict how we use it. Much of this you can do yourself in Settings; for anything else, email us at the address below. You also have the right to complain to a data protection authority — in the UK, the Information Commissioner’s Office (ico.org.uk).

Children

Flight is a tool for work and is not directed at children. We do not knowingly collect information from anyone under 16. If you believe a child has given us information, contact us and we will delete it.

Changes to this policy

When we change this policy we will update the date at the top, and if a change is significant we will tell you in Flight or by email before it takes effect.

Contact us

Questions or requests about your privacy: [email protected].