Legal
Privacy Policy
Effective 26 October 2026
The short version: A bid package or pay statement you give us is read and never kept as a file: MinLine deletes the PDF as soon as it is parsed, and Waypoint reads statements in your browser and sends only the fields it shows you. What is kept is private to your account, and you can delete it at any time. We never share your data with any airline, employer or union, and we do not sell any of your information.
1.Who we are and what this covers
PocketFE is operated by Pocketfe LLC ("PocketFE," "we," "us"). This Privacy Policy describes what information we collect through pocketfe.com, minline.bid and the apps we offer, MinLine, Waypoint and the Insights Suite (together, the "Services"), how it is used, and the choices you have. It is written to match how the Services actually work, and it is part of our Terms of Service.
2.Information we collect
Account
What, exactly: Email address and a password. Passwords are cryptographically hashed by our authentication provider; we never store or see them in plain text.
Why: Sign-in, account recovery, service notices.
Employment check
What, exactly: A Delta email address you confirm with a one-time code, kept against your account. One live account per address.
Why: Confirming you are a crew member before you subscribe, and allowing one free month per pilot.
Pilot details
What, exactly: If you give them: phone number (optional), Delta employee number, seat, fleet, domicile and date of hire.
Why: Setting up your logbook and the Services around your position.
MinLine bid data
What, exactly: The trip data extracted from bid packages you upload (pairings, times, credit values, layovers). The PDF itself is parsed in temporary storage and deleted immediately. It is never retained.
Why: The core of MinLine: generating your bid groups.
MinLine preferences
What, exactly: The criteria you set (days off, credit targets, pre-posted credit, commute times, city and hotel highlights), the trips you sort into lists, and saved bid groups.
Why: Personalizing your results; carrying settings month to month.
Waypoint logbook
What, exactly: The flights, times, aircraft, notes and journal entries you import or enter, and the crew names and notes you choose to keep. Pay statements are read in your browser; only the fields shown to you before import are sent. If you link a crew calendar, its address, which our server reads to import your trips.
Why: Keeping your logbook, map and journal, on any device you sign in to.
Friends
What, exactly: The people you choose to let read your Waypoint logbook and map, read-only.
Why: Sharing your logbook with the people you pick.
Support and help
What, exactly: What you send through Get in touch or Need help?: your name, email, optional phone number, message, and the page you sent it from. Files you attach to a help report are emailed to us and not stored by the Services.
Why: Answering you.
Session and security data
What, exactly: Sign-in sessions and timestamps; on MinLine, with IP address and browser identifier. Security events, such as a device being signed out when the device limit is reached, and failed sign-in attempts.
Why: Enforcing the per-account device limit, detecting account sharing and unauthorized access.
Visit counts
What, exactly: A daily count of visitors and page views. Each visitor is a one-way code made from the IP address and browser identifier for that day only. No address is stored, no cookie is set, and the same browser counts as someone new the next day.
Why: Knowing how much the Services are used.
Payment status
What, exactly: Your subscription status, plan and billing period, received from our payment processor. Card numbers never touch our servers: checkout happens on Stripe's hosted pages.
Why: Determining subscription access.
Referrals
What, exactly: If you sign up through an affiliate's link: that the link brought you, and the date of your first payment.
Why: Crediting the affiliate.
Category What, exactly Why Account Email address and a password. Passwords are cryptographically hashed by our authentication provider; we never store or see them in plain text. Sign-in, account recovery, service notices. Employment check A Delta email address you confirm with a one-time code, kept against your account. One live account per address. Confirming you are a crew member before you subscribe, and allowing one free month per pilot. Pilot details If you give them: phone number (optional), Delta employee number, seat, fleet, domicile and date of hire. Setting up your logbook and the Services around your position. MinLine bid data The trip data extracted from bid packages you upload (pairings, times, credit values, layovers). The PDF itself is parsed in temporary storage and deleted immediately. It is never retained. The core of MinLine: generating your bid groups. MinLine preferences The criteria you set (days off, credit targets, pre-posted credit, commute times, city and hotel highlights), the trips you sort into lists, and saved bid groups. Personalizing your results; carrying settings month to month. Waypoint logbook The flights, times, aircraft, notes and journal entries you import or enter, and the crew names and notes you choose to keep. Pay statements are read in your browser; only the fields shown to you before import are sent. If you link a crew calendar, its address, which our server reads to import your trips. Keeping your logbook, map and journal, on any device you sign in to. Friends The people you choose to let read your Waypoint logbook and map, read-only. Sharing your logbook with the people you pick. Support and help What you send through Get in touch or Need help?: your name, email, optional phone number, message, and the page you sent it from. Files you attach to a help report are emailed to us and not stored by the Services. Answering you. Session and security data Sign-in sessions and timestamps; on MinLine, with IP address and browser identifier. Security events, such as a device being signed out when the device limit is reached, and failed sign-in attempts. Enforcing the per-account device limit, detecting account sharing and unauthorized access. Visit counts A daily count of visitors and page views. Each visitor is a one-way code made from the IP address and browser identifier for that day only. No address is stored, no cookie is set, and the same browser counts as someone new the next day. Knowing how much the Services are used. Payment status Your subscription status, plan and billing period, received from our payment processor. Card numbers never touch our servers: checkout happens on Stripe's hosted pages. Determining subscription access. Referrals If you sign up through an affiliate's link: that the link brought you, and the date of your first payment. Crediting the affiliate. We do not run advertising trackers or third-party analytics scripts on the Services. We use only functional cookies: session cookies to keep you signed in, and short-lived ones that carry a sign-in safely from one of our sites to another.
To work offline, the apps keep copies of your own data in your browser on your device. Signing out clears them.
3.How your information is used
Only to provide, secure and improve the Services: parsing your documents, generating bid groups, keeping your logbook, remembering your preferences, processing your subscription, enforcing device limits, and responding when you contact us. Our small team can see account and subscription records to support you and run the Services. We do not sell personal information, and we do not share your data or usage with any airline, employer or union.
4.Service providers
The Services run on infrastructure operated by a small set of providers, each receiving only what its role requires:
- Supabase (database and authentication). Stores account, bid, logbook, preference and session data, encrypted at rest, with access isolated per account.
- Render (application hosting). Traffic to and from the Services is encrypted in transit (TLS).
- Cloudflare (network and security). Carries traffic to our sites.
- Stripe (payments). Handles all card data on Stripe-hosted pages under its own privacy policy; we receive only subscription status.
- Resend (email delivery). Sends account emails (verification codes, password resets, receipts of your support messages) and delivers support messages and help-report files to us. It receives the recipient's address and the message.
- Google (support inbox). Support messages are recorded in a private Google Sheet and emailed to us. No bid or logbook data is sent to Google.
- Widget Insights (the Insights Suite). Insights is provided with our partner Widget Insights. When you open Insights, we tell it your account identifier, email address and whether your plan includes Insights. Documents and questions you give Insights are handled by Insights.
- Iowa Environmental Mesonet and OurAirports (public weather and airport data for Waypoint). Our server asks them for an airport's weather on a date; they receive no information about you.
5.Retention and deletion
- Uploaded bid packages: deleted immediately after parsing, automatically. Not retained even transiently beyond the parse itself.
- Your data and preferences: kept until you replace them, delete them, or delete your account.
- Account deletion: deleting your account from your account settings removes your profile, bid data, logbook, preferences, sessions and security events from PocketFE, Waypoint and MinLine, and cancels any subscription. Backups age out on our database provider's schedule.
- After deletion: we keep a record that your email address and Delta email address have used a free month, so that each pilot gets one, and the Delta address may confirm only one new account. Support messages you sent are kept as correspondence.
- Session and security records: retained while relevant to account security.
- Payment records: retained by Stripe per its requirements; we retain subscription status while your account exists.
To delete your account and data, use the controls in your account settings or contact support@pocketfe.com.
6.Security
Data is encrypted in transit (TLS) and at rest. Access to each account's data is isolated per account. Passwords are hashed with an industry-standard algorithm by our authentication provider. MinLine accounts are limited to a small number of concurrent devices, repeated failed sign-ins are slowed, and unusual sign-in activity is logged. No system is perfectly secure, and we cannot guarantee absolute security, but the Services are designed so that the most sensitive documents you give them, your bid packages and pay statements, are not stored as files at all.
7.Your rights and choices
You may see the data in your account at any time through the Services, correct it directly, and delete individual bid packages, logbook entries or your entire account. Depending on where you live, you may have additional legal rights (such as access, portability, correction or deletion requests): contact support@pocketfe.com and we will honor them. We do not discriminate against users who exercise privacy rights.
8.Other people's information
Waypoint lets you record the crew you fly with, and MinLine's and Insights' reports can involve other pilots. Keep only what you have the right to keep, as our Terms of Service require. Bid Results shows award data with names and employee numbers removed.
9.Children
The Services are for working airline crew members and are not directed to anyone under 18. We do not knowingly collect information from minors.
10.Changes to this policy
If this policy changes materially, we will post the updated version with a new effective date and notify active subscribers directly. Continued use after changes take effect constitutes acceptance.
11.Contact
Privacy questions or requests: support@pocketfe.com. PocketFE LLC · 2050 Graystone Hills, Conroe TX 77304.