Privacy policy
Early access. InFlight is new and still changing. This policy is a plain description of how the service handles your data today. We will update it as the product grows and tell you about material changes.
Who we are
InFlight (“we”, “us”) runs the work OS at inflightwork.com. You can reach us at hello@inflightwork.com about anything in this policy.
What we collect
- Your account. Your email address and the sign-in details our authentication provider, Clerk, needs to sign you in.
- Your workspace content. What you and the agents you connect put into InFlight: items (title, summary, a link back to the source, and optional details such as a channel or ticket key), tasks, notes, attachments, projects, priorities, people you track, and settings.
- The event log. Every change in a workspace is recorded as an event: who or which agent made it, what changed, and when. This powers history, undo and the audit log.
- Agent tokens. Tokens you issue to agents are stored as a one-way hash, with their scopes and when they were last used. We cannot show you a token again after it is created.
- Technical data. Standard request logs (for example timestamps, request ids and errors), used to run and debug the service.
InFlight does not pull data from your other tools. Content only arrives when you, or an agent holding a token you issued, sends it.
Where it is stored
Workspace content is stored in a Postgres database run by Neon, and the application is hosted on Vercel. Each workspace is isolated by row-level security in the database, so one workspace’s queries cannot read another’s data.
How AI is used
To suggest a project, priority, effort and urgency for new items, InFlight sends a trimmed, redacted version of the item (capped in length) to AI models through the Vercel AI Gateway. We request zero data retention from the model providers for these calls. Suggestions the model is unsure about wait in your review queue instead of being applied.
We do not sell your data, and we do not use your workspace content to train AI models.
Cookies and local storage
We use the cookies Clerk needs to keep you signed in. The app stores your appearance preferences (theme, density, accent) in your browser, and, so it opens quickly and works offline, keeps a copy of app files, your most recent Cockpit and Inbox pages and their data, and any tasks you add while offline in your browser. That copy is cleared when you sign out or another account signs in on the same browser. We do not use advertising or cross-site tracking cookies.
Who else processes it
- Clerk: sign-in and account management.
- Vercel: hosting, and the AI Gateway that routes AI calls to model providers.
- Neon: the Postgres database.
- Error monitoring: if enabled, technical error reports (stack traces and request ids) go to Sentry.
We share data with these providers only to run InFlight, and we disclose it beyond that only if the law requires it.
Export and deletion
A workspace owner can export the workspace at any time as a zip of NDJSON files, one per table. Attachment files themselves are not in the zip, only their records. An owner can also delete the workspace. Deletion locks it right away, revokes its agent tokens, and permanently deletes its data straight after. Copies can remain in our database provider’s backups for a short window (about 7 days) until they expire.
To delete your account itself, or for any request about your data, email hello@inflightwork.com.
Changes
If we change this policy in a way that matters, we will update the date above and let account holders know. See also the terms of use.