Privacy Policy
LogVector is a pilot logbook app operated by LogVector LLC ("we", "us"). It exists to keep your flying records, so the data it handles is yours, it is used only to run the app, and it is never sold or used for advertising.
What we collect, and why
- Your account. When you sign in (email, Google or Apple), we store your email address, display name, and optional profile photo, to identify your logbook, let you sign in across devices, and remember which version of the beta notice your account acknowledged. For each device where you allow notifications we also keep a notification token and the device's time zone, so alerts reach that device in your local time.
- Your logbook. The flights, aircraft, endorsements, qualifications, schedules, and hotel notes you enter, import, or scan. This is the product: it is stored so you can keep a legal flying record. If you enter medical-certificate details, we store the certificate class and examination date with your profile.
- Location, only if you turn tracking on. The optional "Track my device" feature uses your phone's GPS, including in the background while the app is closed, to detect your takeoffs and landings and log flights automatically. You are asked explicitly before it is ever enabled, and you can turn it off at any time. For each detected flight, a simplified route line is stored in your account so your logbook can draw it, and a detailed trace of that leg (from ten minutes before takeoff to ten minutes after landing) is backed up to your account's private storage, where it is deleted after 90 days. Location samples outside those windows are not uploaded.
- Photos and files you submit. Paper-logbook photos, roster screenshots, pasted roster text, pasted flight-history text, and CSV files you import are processed to extract your flying data, which becomes part of your logbook. Pay-statement PDFs are read on your device; only the flight references they contain leave it. If a file comes from an app we don't read yet and you choose Ask us to add your app, that whole file is attached to your support report so we can add the app. Only the LogVector team can open it, and it is deleted once that app is added, or after 90 days.
- Diagnostics. Crash reports (via Firebase Crashlytics), error reports the app files by itself (the app version, platform and screen, with the error), and per-feature usage counters used to enforce fair-use limits. These identify your account, not your flights. When you report a problem from the app, the report carries the app version, platform, OS version, device model, language and time zone, plus any screenshots you choose to attach.
- Flight lookups. When the app looks up a flight for you, the request and the provider's answer are recorded with your account for support and billing checks. These raw records expire after 30 days; separate per-flight summaries are kept longer.
- Your plan and purchases. Which plan your account is on (Free, Standard, Pro, or Beta while the beta lasts), when it started and when it ends or renews, whether a trial is running, and the extra scan pages and flight lookups you hold, with a ledger of how each unit was earned, bought or spent. When you subscribe or buy a pack, the store tells us that the purchase happened and whether it is active, renewed, cancelled, refunded or in a billing grace period. We never receive your card number or bank details. Support actions on your account (a plan set by hand, units added or removed) are written to an administrative audit trail together with the reason given.
Who processes it for us
LogVector runs on trusted service providers. Each receives only what its job needs, under privacy commitments that protect your data at least as well as this policy does:
- Google Firebase (Google Cloud): stores your account and logbook (including scan photos, flight-trace backups and the screenshots and files you attach to a report), runs our server code, delivers notifications, checks that requests come from a genuine copy of the app, and hosts this site.
- Anthropic: reads the logbook photos, the roster text and screenshots, the pasted flight-history text, and the column headers and sample rows of the files you import, and transcribes them into structured flights. Anthropic's commercial API does not use this content to train models by default; explicit opt-in arrangements and materials reported to Anthropic are exceptions under its terms.
- FlightAware: receives flight numbers and dates from your schedule and your lookups to fetch live flight status and actual times, airport codes when the app matches a flight your phone sensed, and airport pairs when you ask for recently filed routes.
- Geoapify: receives an airport's coordinates when you search for layover hotels near it, your phone's position when you choose "near me now", and the hotel name you type when you search by name.
- Map and weather-radar tile providers: when the map or the radar overlay is on screen, tile requests go straight from your device and carry standard web-request data (your IP address).
- Weather and airport-information services: public US government and community sources for METARs and TAFs, D-ATIS, SIGMETs, pilot reports, storm cells, radar timing and worldwide precipitation frames. Our server asks them with airport or station codes, or the area of the map on screen; nothing about your account is sent.
- Apple App Store and Google Play: sell the subscriptions and packs. The store you buy through is the seller: it takes your payment, applies tax, issues your receipt and handles cancellations and refunds under its own privacy terms. It reports the purchase and its status to us and to our billing processor below. We never see your payment details.
- RevenueCat: our billing processor. It receives an app user id (your account id, the same one Firebase assigns) and, from the stores, your purchase and subscription status: which product, when it started, renews, was cancelled or refunded, and whether a trial or grace period is active. Like any web service it also sees the technical details of each request, such as your IP address, app version and platform. It does not receive your logbook, schedule, location, photos, roster text or email address from our app. Purchase history is also used for subscription analytics and fraud prevention.
We do not sell your data, share it with advertisers, or use it for any purpose other than running LogVector.
Sharing with people you choose
If you use Family & Friends sharing, you decide who sees your schedule and how much: which weeks, whether your layover hotel is included, and which live flight updates they may receive. Each person you invite gets their own separate copy containing only what you picked for them. People you share with must sign in, so you always know which account is watching; there are no read receipts and no location sharing beyond your published schedule. The private name you give a person (“Mom”) stays in your own account and is never visible to them.
Career history is a separate choice and is off by default. If you turn it on for someone, they receive one redacted row for each real flight: date, departure and arrival, logged hours, aircraft type, permitted time categories, day/night takeoffs and landings, approach count, holds, and distance when recorded. This is enough to reconstruct individual flights. Simulator and ATD time and opening balances are not shared. We also exclude crew, remarks, the registration field, audit/source details, checkride events and approach details. The internal source flight ID is retained so changes update the correct row; some imported IDs may themselves contain source details such as a tail number.
Removing a person, pausing sharing, or turning Career history off stops future server access and updates. The app stops displaying that shared data, and the redacted flight copy is deleted when nobody has Career access. We cannot remotely erase information that a recipient already downloaded, copied, cached, or screenshotted.
Signing by link. If you send an instructor a link to sign training flights or an endorsement, anyone holding that link can open a page showing your name and what it asks them to sign: for each flight its date, route, aircraft and the times being signed, or the endorsement's wording. If that instructor signed for you before, the page also shows the name, ratings and date they used last time and only the last three characters of their certificate number; they type the full number, which has to match, and five wrong tries close the link. A link works once, for 14 days, and you can cancel it at any time. What the instructor enters (their name, certificate number, ratings, a date, remarks and their drawn signature) is saved in your logbook as their signature, and their copy stays viewable at the link until those 14 days end. Signing pages are marked so search engines do not list them.
Security
All data travels encrypted (TLS) and is stored encrypted at rest on Google Cloud. Access to your logbook requires your sign-in, and server rules restrict every logbook record to its owner. A schedule you share through Family & Friends, including an optional redacted Career history, is a copy you chose to publish to a specific signed-in person, readable by that person alone.
Retention, deletion, and export
Your data is kept for as long as your account exists. You can export everything in your account from the app at any time (Export tab: one ZIP holding spreadsheets plus a machine-readable exact copy). To delete your account and all its data, open Profile > Delete account in the app, or email support@logvector.app from your account's email address. Either way your account locks immediately (signed out everywhere, flight alerts cancelled) and deletion is completed within 30 days and is permanent; within those 30 days an email to support can undo it. See also account deletion.
Your plan record is archived for the same 30-day undo window and then removed; your extra-unit balances and their ledger are deleted with your account. While paid plans are offered, we also ask our billing processor to delete your customer record there. That request is best-effort: if it fails, your LogVector account is still deleted, and you can email support to have the processor's record removed by hand. Two records outlive an account because they identify no flights: account-wide usage counters that keep our cost books honest, and the administrative audit trail, which keeps your account id and dates only. Your purchase history also stays with the store under the store's own terms, and deleting your account does not cancel a store subscription. Cancel it in the store first.
Changes
If this policy changes materially, the app will say so and this page will carry the new effective date.