Privacy Policy

Who we are

OpenLogbooks is operated by Six Two Whiskey LLC, doing business as OpenLogbooks ("we", "us", "our"). When you use the OpenLogbooks application or website, you are entering into a relationship with Six Two Whiskey LLC.

Questions about this policy or your data? Email [email protected].

What we collect

We collect the minimum information needed to operate the service:

• Account information. When you sign in with Google, Discord, or GitHub, we receive your email address, display name, and a provider account identifier. We do not store passwords ourselves.
• Aircraft and logbook data. Information you enter about your aircraft (registration, make, model, serial number), logbook entries (date, description, hours, certifying-statement data), AD compliance records, life-limited parts, major alterations, and any photos or PDF attachments you upload.
• Billing information. If you upgrade to a paid plan, Stripe processes your payment. We never see or store your card number; we receive only a customer identifier and the subscription state from Stripe.
• Product analytics. If PostHog analytics is enabled in your environment, we collect anonymized usage events (which features you use, in what order, with what frequency). We do not send your email, name, aircraft registration, owner contact information, or any other identifying field to PostHog.
• Operational logs. Standard server logs (request paths, IP address, response codes, timing) used to diagnose availability and security issues. Logs are retained for up to 30 days.

How we use it

• To run the service: render your logbook entries, generate PDFs, send transactional email through Resend.
• To bill paid plans through Stripe.
• To diagnose bugs and improve the product.
• To respond to your support requests.

We do not sell your data.

Who we share it with

We share data only with the service providers we need to run OpenLogbooks:

• Stripe — payment processing for paid plans.
• Resend — transactional email delivery (verification, export-ready notifications).
• PostHog — product analytics (anonymized, no PII).
• OAuth providers (Google, Discord, GitHub) — only when you choose to sign in with them.
• Our hosting provider for application servers and file storage.

We do not share your aircraft or logbook data with anyone else. If a court order or subpoena requires us to disclose data, we will notify you first unless legally prohibited from doing so.

Where it lives

Your aircraft data, logbook entries, and uploaded files are stored on servers we operate in the United States. Photos and PDF attachments are stored on the application server's local disk; we may migrate to cloud object storage in the future and will update this policy if we do.

Your data, your rules

You can:

• Export your full logbook as PDF or CSV at any time, free or paid tier.
• Edit or delete any entry, photo, or aircraft you've added.
• Transfer ownership of an aircraft (and its complete maintenance history) to another OpenLogbooks user.
• Delete your account from the Account page. Account deletion removes your user record, your aircraft, and every dependent record. Photos and exports are purged within 7 days.
• Request a copy of all data we hold about you, by emailing [email protected]. We will respond within 30 days.

If you are a California resident (CCPA) or in the EU/UK (GDPR), you have the additional rights granted by those laws — including the right to object to processing and the right to data portability. Email us to exercise them.

Cookies

OpenLogbooks uses a small set of cookies needed for the application to function: a session cookie that keeps you signed in, a CSRF token for form submissions, and a signed cookie that remembers when you've dismissed the upgrade banner. We do not use third-party advertising cookies.

Children

OpenLogbooks is not directed at children under 13 and we do not knowingly collect data from them. If you believe a child has provided us with personal information, contact us and we will delete it.

Changes

If we materially change this policy, we will email registered users at least 30 days before the change takes effect. Minor edits (typo fixes, clarifications that don't expand what we collect or how we use it) will be reflected by updating the "Last updated" date at the top of this page.