Draft. This policy is under legal review and not yet final. Bracketed items are placeholders pending completion.

Privacy Policy

MinLine — operated by [Company Legal Name] — Effective [Effective Date]

This Privacy Policy describes what information MinLine (the "Service") collects, how it is used, and the choices you have. It is written to match how the Service actually works. The short version:

The bid package you upload is parsed and immediately deleted. The original PDF is never stored. Only the extracted trip data — kept private to your account — is retained, and you can delete it at any time. We never share your bid data with any airline, employer, union, or other user, and we do not sell any of your information.

1. Information We Collect

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.
Bid data	The trip data extracted from bid packages you upload (pairings, times, credit values, layovers). The uploaded PDF itself is parsed in temporary storage and deleted immediately — it is never retained.	The core function of the Service: generating your bid groups.
Preferences	The bidding criteria you set (days off, credit targets, commute times, city and trip preferences) and trips you discard.	Personalizing your results; carrying settings month to month.
Session & security data	Login sessions with IP address, browser identifier, and timestamps; security events such as a device being signed out when the device limit is reached.	Enforcing the per-account device limit, detecting account sharing and unauthorized access.
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.
Beta list	If you join the beta waitlist: your email address and signup time.	Contacting you about beta access — personally, not via marketing automation.

We do not run advertising trackers or third-party analytics scripts on the Service. The Service uses only functional cookies: a session cookie to keep you signed in.

2. How Your Information Is Used

Only to provide, secure, and improve the Service: parsing your bid package, generating bid groups, remembering your preferences, processing your subscription, enforcing device limits, and responding when you contact us. We do not sell personal information, and we do not share your bid data or usage with any airline, employer, or union.

3. Service Providers

The Service runs on infrastructure operated by a small set of providers, each receiving only what their role requires:

Supabase — database and authentication. Stores account, bid, preference, and session data, encrypted at rest, with per-account access isolation enforced at the database level.
Render — application hosting. Traffic to and from the Service is encrypted in transit (TLS).
Stripe — payments. Handles all card data on Stripe-hosted pages under their own privacy policy; we receive only subscription status.
Google — beta-waitlist processing only. New waitlist signups (email address and time) are recorded in a private Google Sheet and emailed to the founder so he can reply personally. No bid data is ever sent to Google.
[Email delivery provider — to be added when custom SMTP is configured] — delivers account emails (verification, password reset).

4. Retention and Deletion

Uploaded PDFs: deleted immediately after parsing, automatically. Not retained even transiently beyond the parse itself.
Bid data and preferences: kept until you replace them, delete them, or delete your account.
Account deletion: deleting your account removes your profile, bid data, preferences, sessions, and security events from the live database in one cascading operation. Backups age out on our database provider's schedule.
Session and security records: retained while relevant to account security.
Payment records: retained by Stripe per their requirements; we retain subscription status while your account exists.

To delete your account and data, use the account controls in the app or contact [support email].

5. Security

Data is encrypted in transit (TLS) and at rest. Database access is isolated per-account at the row level. Passwords are hashed with an industry-standard algorithm by our authentication provider. Accounts are limited to a small number of concurrent devices, and unusual sign-in activity is logged. No system is perfectly secure, and we cannot guarantee absolute security, but the Service is designed so that the most sensitive thing you give it — your bid package — is not stored at all.

6. Your Rights and Choices

You may access the data in your account at any time through the Service, correct your preferences directly, and delete individual months 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 email] and we will honor them. We do not discriminate against users who exercise privacy rights.

7. Children

The Service is for working airline crewmembers and is not directed to anyone under 18. We do not knowingly collect information from minors.

8. 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.

9. Contact

Privacy questions or requests: [support email].