In short
- We collect your account details and the flight training records you choose to add, and use them only to run PilotMetrics.
- We don't sell your data or show adverts. We use Google Analytics cookies to see how people use the site; they never see your flights, username or email, and you can turn them off at any time with Cookie settings.
- Your profile is public by default: anyone who knows your username can view your full flight log through a share link, on the pages you choose to share. You can make it private at any time under Account. The leaderboard and Battle Mode are separate and opt-in.
- Our server is in the UK. Account emails are sent through a provider in the United States.
- If you buy Pro, PayPal handles the payment. We keep a record of the purchase, including your agreement that Pro starts straight away.
- You can export your data at any time and ask us to delete your account.
Who we are
PilotMetrics (pilotmetrics.app, "PilotMetrics", "we", "us") is a flight training analytics service for student pilots.
We are the controller of your personal data under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.
For anything about your data, email [email protected].
Data we collect
Account details (you give us)
- Username: shown on your profile, share links, the leaderboard and battles.
- Email address: used to log in and to send account emails.
- Password: stored only as a one-way hash. We can never see your actual password.
- Two-factor sign-in (if you turn it on): the secret your authenticator app shares with us, kept encrypted, and your recovery codes, stored only as one-way hashes. They're deleted when you turn it off.
- Passkeys (if you add any): each passkey's public key, the name you give it, its signature counter, whether it syncs between your devices, and when it was added and last used. The private key never leaves your device or its keychain, and we store nothing else about the device. Each is deleted when you remove it, or with your account.
Training records (you add)
- Flights: date, off- and on-block times, aircraft registration and type, instructor, pilot-in-command or co-pilot name, whether you were pilot flying or monitoring, departure and arrival airfields, route, take-offs and landings (day and night, full stops, go-arounds), remarks and linked syllabus lessons, and any night, instrument, cross-country, co-pilot, instructor, examiner and multi-pilot time, simulator type, instrument approaches and holds you enter on a flight, and (Pro) any totals you bring forward from another logbook, and the class and features you set for your aircraft (by registration).
- FlightLogger imports: if you import a FlightLogger CSV, we keep each imported row in full, including logbook time categories (for example dual, PIC, night and instrument time).
- Other logbook apps' imports: if you import an export from ForeFlight, LogTen, myFlightbook, Garmin Pilot, CrewLounge or another logbook app, it's read in your browser and we keep, for each flight, its logbook columns PilotMetrics uses (date, aircraft, route, block and total times, dual, PIC, solo, night, instrument and cross-country time, landings, instructor, lesson and remarks) and which app it came from. The rest of the file isn't sent to us.
- Change history of your flights: whenever a flight is added, changed or deleted (by you, an import, FlightLogger or your flight school's records), we record when, by what, what changed (its values before and after) and, for a deleted flight, the whole flight, so it can be put back. It's kept on every plan and shown with Pro, only to you: never on your share link, to your instructor, your flight school, sponsors or Family view. It's kept while your account is, and deleted when you clear your logged flights or reset all your data, or delete your account.
- Backups of your logbook: copies of everything above that you keep in PilotMetrics (flights, cancellations, standbys, your lists, settings and Pro entries), made each week when your training has changed, when you choose "Back up now", and before you restore one. We keep your newest ones (1 on Free, 5 on Lite, 10 on Pro); a new one replaces the oldest. Only you see them. They're deleted when you delete them, when a plan ends and leaves more than the free plan keeps (the oldest go), or with your account. Clearing your data doesn't delete them, so you can restore it.
- Endorsements and signatures (Pro): the endorsements you add (title, wording, date and expiry), and the signatures on them and on your flights: the signer's name, the licence or certificate number they give, when they signed, how (with their PilotMetrics account, or drawn on your device: then the drawing itself) and a fingerprint of the entry as it was signed, so a later change shows. When you ask an instructor to sign, they see that entry (a flight's date, times, aircraft, route, PIC, landings and remarks, or the endorsement's wording) on their Instructor Dashboard; the instructor must be linked to you or assigned to you by your flight school. Only you and the instructor you ask see them: never your share link, other staff at your flight school, sponsors or Family view. They're deleted when you delete them (an endorsement takes its signatures with it), or with your account; a signature you were given stays, with the signer's name, if the instructor's account is deleted.
- Saved logbook queries (Pro): the name and conditions of each query you save on the Queries page. Only you see them.
- GPS tracks (Pro): if you add a GPX, KML or IGC file to a flight, we keep its path (up to 2,000 points, each with its position and, if the file has them, altitude and time), its name and the figures worked out from it (distance, highest altitude, start and duration). Only you see your tracks: never your share link, your instructor, your flight school, sponsors or Family view. A track is deleted when you delete it, delete its flight or delete your account.
- ADS-B lookups: for each of your flights you look up on the ADS-B Import card, we keep what public flight tracking saw its aircraft do between your block times (when it was first and last seen, the airfields nearest those points and its transponder address), whether a departure or arrival airfield was suggested, whether you approved it or kept your own, and how many lookups you made each month (for your plan's monthly limit). Looking up a new flight keeps nothing but that count; what it finds only fills in the Log a Flight form for you to save. Only you see them: never your share link, your instructor, your flight school, sponsors or Family view. A flight's match is deleted when the flight is, or with your account. See ADS-B flight matching for what our server asks for.
- Mass & balance (free): if you set up an aircraft's mass and balance (Settings > Your Lists), we keep its figures (registration, empty mass and arm, loading stations, fuel, limits and envelope, and where they came from), every earlier version of them, and any documents you add (PDF or images, up to 3.5 MB each). If you save a mass for yourself or an instructor, we keep it (in kg) with the instructor's name as your flights spell it. Pilots at the same flight school (in PilotMetrics for Flight Schools, or the same flight school in Settings) are shown, as an unverified suggestion, the aircraft figures and the instructors' masses most of them saved for the same registration or instructor's name (only when at least two pilots saved the same), with how many pilots and when: never who saved them, never your own mass, and never your documents. If your instructor or your flight school sets an instructor's mass for their students (below), you see it with who set it and when, as a suggestion you confirm for each flight; it never changes the masses you saved. Nothing else of this is shown to anyone: not your share link, your instructor, your flight school's staff, sponsors or Family view. It's kept until you delete it or your account. The loading you type on the Mass & Balance page stays on your device.
- Pre-flight briefs (Lite and Pro): if you save a brief on the Briefing page, we keep it: the flight (date, time, aircraft, airfields, instructor, lesson and the FlightLogger booking it's for), the METARs, TAFs and NOTAMs (the airfields' and those along the line between them), the airfields' frequencies and the airspace along that line with its frequencies, as they were fetched, the loading and the mass and balance and performance figures worked out from it, and what you write (the tech log, fuel plan, threats and errors, and the lesson brief). Only you see your briefs: never your share link, your instructor, your flight school, sponsors or Family view. A brief is deleted when you delete it or your account; a brief you haven't saved yet is kept on your device only. The weather is fetched by our server with only the airfields' codes, and the NOTAMs come from our own copy (below).
- Nav logs (free): if you save a nav log on the Nav Log page, we keep it: its title, date, aircraft and type, the route's points (their names, positions, frequencies and notes), each leg's altitude, safe altitude, TAS, wind, track, distance, variation and notes where you typed them, the alternate, the aircraft's TAS, fuel burn and fuel on board, the fuel plan's allowances, the compass deviation card, the times you write in (time off and the time at each checkpoint), the diversion you plan (where it starts, which can be your device's position if you choose that, where it goes, its time and fuel and any figures you typed for it) and your notes. Finding the airfields nearest a diversion point sends only that position, rounded to about a kilometre, and we don't keep it. The headings, times and fuel are worked out on your device, not kept. Only you see your nav logs: never your share link, your instructor, your flight school, sponsors or Family view. A nav log is deleted when you delete it or your account. Until you save it (or without an account), the one you're making is kept on your device only.
- Support requests: if you send one from the Support page, we keep what you write and our replies, what it's about, the page you came from (its address without any query) and your device and browser type (such as "Chrome on Android"). We use them to answer you and fix problems, and each message is emailed to the other side through our email provider. They're deleted with your account. If they're misused, we can turn off sending requests for that account, and we keep when we did.
- Flight attachments (Lite and Pro): the photos and files (PDF or images, up to 3.5 MB each) you attach to a flight or a pre-flight brief, kept encrypted, with what you enter about each (its kind, name and notes) and the flight or brief it's on. Photos are made smaller on your device before they're sent, which leaves out where they were taken and the camera's details. Only you see them: never your share link, your instructor, your flight school, sponsors or Family view. They're deleted when you delete them, the flight they're on, or your account; a deleted brief's attachments move to the flight you logged for it (or are deleted with it if there's none).
- Licences & Documents: the documents you add to your wallet (PDF or images, up to 3.5 MB each), kept encrypted, with what you enter about each (its kind, name, issuer, reference, issue and expiry dates, notes and when to remind you), and (Lite and Pro) your qualification history: each entry's qualification, what happened (obtained, revalidated, renewed, superseded or lapsed), its dates, authority, reference, notes, when to remind you and the document you link to it. A reminder's email names the document or qualification; its push notification only says the date. Only you see them: never your share link, your instructor, your flight school, sponsors or Family view. They're deleted when you delete them, or with your account.
- Custom logbook fields (Pro): the fields you add on the Logbook (name, kind, choices and the aircraft they're for) and what you enter in them on your flights. They're part of your logbook, so they're shown wherever your flights are (your share link, your instructor and your flight school, if you share with them), and kept in your flights' change history and backups.
- Your own recency rules (Pro): the name, description, reference and conditions of each rule you add on the Currency page. Only you see them.
- Cancellations: date, reason, planned hours, aircraft, instructor, location and remarks.
- Standby shifts: date, location, start and end times, outcome and notes.
- Timeline events (Pro): milestones, school and personal events you add to your timeline: type, date, title and notes.
- Ground school exams (Pro): subject, exam date, result (passed or failed), score, attempt number, exam provider and notes.
- Deadlines: if you enter them (Licences & Documents and Flights), your medical certificate's expiry date and class (Lite and Pro), and your solo authorisation's expiry date and length in days (or, FAA, the date of your last solo endorsement), and your stall currency's expiry date and length in days, and (Currency) your SEP class rating's expiry date or the date of your last FAA flight review. Nothing else about your health.
- Settings: your flight school or course, the licence you're training for (for example UK CAA or EASA), the dates you moved between your school's training locations, and whether you've opted into the monthly battle.
- Training plan: your training start date, expected training duration, and the Pace Planner details you enter: target completion date, current training stage, expected flights and hours per week, and any planned breaks or holidays (dates and an optional label).
- Battles: battles you create, join or are invited to as a rematch or challenge, and group and course battles you start or join, their settings, when they started (and closed) and their results, and your final place each month in the monthly battle.
- Training groups: the groups you create or join (name, join code, the creator's flight school), when you joined, whether you're the group's owner, whether you share your figures with the group, whether you have a page in its Yearbooks, and the Yearbooks unlocked for it (which year, when and by whom).
- Instructor links: if you add an instructor, who they are, their flight school at the time, when you asked, when they accepted, and whether the link is pending, active, declined or removed.
- Reports: each PDF report or CSV export you make: its title, the period it covers, the options you chose, when you made it, its headline figures (for example flights, flight time, flying days and the longest interval between flights) and its verification code. The report itself is made in your browser and isn't stored by us. We keep this record so we can count your report allowance, let you download the report again, and confirm the report is genuine: anyone you give a report to can enter its code at pilotmetrics.app/verify-report and see its title, period, your username and those headline figures, even if your profile is private. Records are deleted with your account.
Instructor Mode (only if you turn it on)
- Instructor details: the name students know you by, the flight school or training organisation you work for, an optional instructor ID or staff number, and the instructor code we create for you. Students can find you by your instructor code or account email (not your username); we show them your name, flight school, username and code, never your email or staff number.
- Your mass for your students' mass & balance (only if you set it): the mass you enter (in kg), the name your students' flights give you, and when you set it, from the Instructor Dashboard. Your linked students, and the active students of the flight schools whose staff you're on, see it (with the date) on their Mass & Balance page. The flight schools whose staff you're on see it in their settings. It's deleted when you remove it, or with your account.
Purchases (only if you buy Pro)
- Purchase record: the account and username it was for, the amount and currency, PayPal's order and payment references, the payment's status (for example completed, refunded or reversed), any amount refunded, and when you paid.
- Your PayPal email address: PayPal tells us the email address on the PayPal account that paid. We use it only to match up and resolve payment problems.
- Your agreement to start Pro straight away: before paying, you tick a box agreeing that Pro starts immediately and that you then lose your 14-day right to cancel. We record the exact wording you agreed to, when, and the IP address you agreed from, as evidence of that agreement.
- Checkouts you didn't finish: the record above (with your agreement, but without a PayPal email address) is created when you click a PayPal button, so we also keep it for checkouts you start but don't complete.
- PayPal notifications: the messages PayPal sends our server about a payment (for example to say it completed or was refunded), which include the payment details above.
We never see or store your card or bank details: you enter them with PayPal, not with us.
Payments are received by Zettako, so they show as Zettako on your PayPal, card or bank statement and in PayPal's receipt, not as PilotMetrics.
Technical data (collected automatically)
- Login session: a session cookie that keeps you logged in (see Cookies).
- Account activity: when you created your account, when you last logged in, whether your email is verified, which plan you have (Free, Lite or Pro), when it started and ends, which add-ons you've bought, and, if your account has been suspended, when and why.
- Email settings and history: which notification emails you've switched on, and a record of the notification emails we've sent you (type, what it was about and when), so we never send the same one twice.
- Time zone: your browser's time zone (for example Europe/London), saved when you use PilotMetrics, so notification emails and push notifications never arrive between 10pm and 6am where you are.
- Security records: your IP address and the email, username or code you entered, recorded when you make certain requests (logins, password resets, verification emails, battle code look-ups) so we can block repeated guessing and investigate suspicious activity.
- Server logs: our web server records standard request information such as IP address, time, page requested and browser type.
- Monitoring: to keep PilotMetrics running well, we record how it's performing: how long each kind of request took and whether it worked, how long database queries took (without the values in them), how syncs and scheduled jobs went, counts such as emails sent and failed logins, and errors in our scripts that happen in your browser (the message, our script and the page's address without its details). These records never include your name, username, email address or IP address.
- How the app is used: counts of which app pages are opened and which page they were opened from, which cards are scrolled to, which buttons and links are used, that "Jump toβ¦" was used, and roughly how long a page was on screen, by page, plan (or visitor, demo or share link) and phone or computer. They're counted, not recorded per person: there's no identifier of any kind, so they can't be linked to you or followed from page to page, and nothing you type or see on the page is sent. Turning Analytics off (see Cookies) turns these counts off too.
- Site usage (Google Analytics): which pages are visited, how visitors arrived (for example a search engine, another website or a campaign link), roughly where they are (country and city, worked out from the IP address, which Google doesn't store), and the device, browser and screen size. Page addresses are sent without their details: a share link, for example, is sent as
/dashboard?share, never with the username, and email links never include their codes. Your account, username, email address and training records are never sent. You can turn Analytics cookies off at any time (see Cookies).
We don't use advertising networks or tracking pixels, and we don't buy data about you from anyone. The only outside services your browser contacts are Google Analytics, those for the Flight Map and, when you open the Pro checkout or the donation window, PayPal (see Service providers).
How and why we use it
Data protection law requires us to have a lawful basis for each use of your data:
| What we do | Data used | Lawful basis |
|---|---|---|
| Create and run your account, store your records and show your dashboards, timeline and analytics | Account details, training records, settings | Contract: providing the service you signed up for |
| Send account emails: verification, welcome, password reset, password changed, email changed, two-factor sign-in turned on or off or a recovery code used, a passkey added or removed, a one-off note the morning after you connect your FlightLogger key on turning on push notifications (only if none of your devices has them on), and instructor requests (a student asking you to be their instructor, or your instructor accepting) | Username, email address | Contract |
| Send notification emails you can switch off: battle updates, the weekly digest (on unless you switch it off, and only for a week with flying, bookings or a deadline in it), monthly training summaries, inactivity reminders, monthly leaderboard results, first solo and personal record emails, and reminders before and after a trial or a year of Lite or Pro ends | Username, email address, training records, battle and leaderboard results | Legitimate interests: keeping you up to date with your own training. Every one can be turned off under Account > Notifications or with the unsubscribe link in each email. |
| Send PilotMetrics News about new features and updates | Username, email address | Consent: off unless you switch it on, and you can switch it off at any time |
| Show your profile to others through share links, on the pages you choose, while "Public profile" is on (the default) | Username, training records, flight school, training plan, last login date | Legitimate interests: sharing your training progress is a core feature of PilotMetrics. You can object at any time by making your profile private, which takes effect straight away. |
| Show your results on the public monthly leaderboard, and email you your final rank at the end of each month | Username, email address, flight school, flight dates, times, location and category | Consent: you opt in and can opt out at any time |
| Compare your training with an opponent in a battle, or with the members of a group who join a group battle | Username, flight dates, times, location and category | Consent: you create or join the battle yourself |
| Work out statistics for the training groups you join (averages and counts only) | Flight school, flight dates, block times, aircraft type or registration, linked syllabus lessons and remarks (to match lessons), training start date, planned breaks, current stage | Consent: you join each group yourself and can leave at any time. In a small group, members can work out your figures from the totals (see Who can see your data). |
| Work out anonymised statistics for flight schools (averages and counts only) | The same data as for training groups | Legitimate interests: letting pilots compare their training with their school, never your own figures. |
| Show each pilot where their training stands among other pilots (percentages only) | The same data as for training groups, and your course | Legitimate interests: letting pilots compare their training with other students. Your own figures are never shown to anyone else. |
| Show your username and headline figures to a training group, if you switch on sharing for that group | Username, flights per week, total hours, average gap, syllabus progress and stage | Consent: off unless you switch it on, per group, and you can switch it off at any time |
| Make your PilotMetrics Wrapped (your year of flying), and show where your year stands among other pilots (percentages only) | Flight dates, off- and on-block times, category, landings, aircraft type and registration, departure and arrival airports, linked flights, and the battles and group battles you took part in that year | Legitimate interests: showing you your own year. Each percentage is worked out from at least 20 other pilots, and nobody else's figures are shown to you, or yours to them |
| Make a training group's Yearbook: the class's totals and records, and a page of your own if you switch it on | The same data as for Wrapped, your username, flight school and course (only on your page) | Consent: your flights count towards the class's totals while you're in the group; your page, and your name next to a record you hold, only if you switch on Give me a page for that group, which you can switch off at any time |
| Let the instructor you add follow your training (read-only) | Username, training records, settings and training plan, last login date | Consent: you choose your instructor and can remove them at any time |
| Let students find and add you as their instructor (Instructor Mode) | Instructor name, flight school, staff number, instructor code, username, email (for finding you only, with your instructor code) | Consent: you turn Instructor Mode on and can turn it off at any time |
| Keep accounts secure: block brute-force attempts, prevent abuse, investigate problems | IP address, login identifiers, session data, server logs | Legitimate interests: protecting you, other users and the service |
| Understand how people find and use the site, so we can improve it (Google Analytics) | Site usage (see above), Analytics cookies | Legitimate interests: improving PilotMetrics. Analytics cookies are used only for statistics about our own site, and you can object at any time by turning them off with Cookie settings at the bottom of every page. |
| Process purchases (plans, add-ons and group Yearbooks), unlock what you bought and email you a confirmation | Username, email address, purchase record, PayPal email address | Contract |
| Keep evidence that you agreed Pro starts straight away and that you lose your 14-day cancellation right | The wording you agreed to, when, and your IP address | Legal obligation (the Consumer Contracts Regulations 2013), and legitimate interests: being able to show the agreement was given if it's ever disputed |
| Keep financial records | Purchase records | Legal obligation: tax and accounting rules |
| Handle refunds and chargebacks. If a payment is reversed through a chargeback, we suspend the account and remove Pro (see our Terms) | Purchase record, PayPal notifications, username, email address | Legitimate interests: preventing fraud and protecting the service |
We only send marketing emails (PilotMetrics News) if you opt in. We don't sell or rent your data, or use it for automated decisions that have legal or similarly significant effects on you.
Who can see your data
Some PilotMetrics features are designed for sharing. Please read this section carefully.
Your profile and share links: public unless you make them private
Each account has a Public profile setting, found under Account. It's switched on when you create your account, and you can change it at any time.
- Public (the default): your profile can be opened in read-only view at
pilotmetrics.app/dashboard?share=YOUR_USERNAME(and on other pages, such as the timeline, in the same way). Anyone who has the link, or knows or guesses your username, can see your flights, including instructor names, aircraft, airfields and remarks, as well as your cancellations and standby shifts, and the timeline events and ground school exams you've added. For exams, only the subject, date, pass or fail, attempt number and exam provider are shown: exam scores and exam notes are never shown on share links. - Private: only you can see your flights, cancellations, standby shifts, timeline events and exams. If anyone else opens your share link, they're told the profile is private and shown nothing.
While your profile is public, you choose the pages your share link opens under Account > Your share link (Dashboard, Flights, Pace, Progress, Experience, Timeline and, with Pro, the Logbook, Queries, Currency and Flight Map). All of them are on to begin with. Visitors who open a page you've switched off are told you don't share it, and it's left out of their menu; the Pro pages you've switched off aren't sent at all. The pages are all drawn from the same training, though, so switching a page off hides that page rather than the flights behind it: to keep your training to yourself, make your profile private.
Your email address and password are never shown, even on a public profile.
Because profiles are public by default, choose a username you're comfortable with others knowing, and don't put anything in remarks or notes that you wouldn't want others to read. If you'd rather keep your training to yourself, turn off Public profile under Account. This stops share links working straight away, but we can't control copies someone may already have made.
Family view links: only the people you send them to
Under Account > Family view you can make read-only links for people such as your parents or partner (up to five, each named for who it's for). Anyone with one of these links sees the name you chose for it, your course's name and only the sections you chose for that link, worked out on our server: how far through your course you are, your next milestone (such as your first solo or the next stage), the hours you've flown, an estimated finish at your current pace, how many lessons of each syllabus stage you've done, your recent flying (days since your last flight, flights and hours in the last four weeks, flights a week), and a timeline of your milestones with their dates (when you started training, your first flight, first solo, first landaway, solo cross-country, first night flight, each stage finished and your skill test). They never see your flights one by one, instructors, aircraft, airports, remarks, cancellations, exams or deadlines, and nothing else from your profile is sent to their browser. You can change what a link shows at any time. The links work whether your profile is public or private. Each link is a long random code that we keep only in a form that can't be read back without our server's key; we record when it was last opened (shown to you, not who opened it). Turning a link off stops it working straight away and for good, and closing your account deletes them all.
Monthly leaderboard: only if you opt in
If you opt into the monthly battle, anyone visiting Battle Mode can see your username, flight school and your results for the month: your score and rank, number of flights, block hours, the share of your flights synced from FlightLogger, longest break from flying and the badges you've earned. When a month ends we keep your final place, score, flights, hours and badges: last month's podium shows them while you stay opted in, and your own trophy cabinet counts them. They're deleted with your account. These are worked out on our server; your individual flights, instructor names, aircraft and remarks are not shown. At the start of each month we email you your final rank for the month before, unless you switch this off under Account > Notifications. You can opt out of the battle at any time, which also stops these emails.
Head-to-head battles: only if you create or join one
When an opponent joins a battle, our server compares both pilots' flights for the battle's time window and saves the result: each pilot's totals for the rounds (such as number of flights, block hours, landings, airports visited and longest break from flying) and who won each round. Your individual flights, dates and routes are not shown to your opponent or anyone else. Anyone who has the battle code or result link can see the result for 7 days after the battle starts; after that the code and link stop working. You and your opponent can still see the result in your battle history for 1 year after the battle started. After that we keep the result (not your flights) so it can appear in your Wrapped and in the Yearbook of a training group you're both in, for that year; it's deleted when either of your accounts is.
A live challenge works the same way, except that it runs forward from the day after your opponent joins: until it ends, you, your opponent and anyone with its code can see the standings so far, and the result is saved when it ends. A "Who had it worse?" battle also compares how many cancelled slots and standbys not flown each pilot logged. A Logbook battle also compares each pilot's PIC, night, cross-country and instrument hours and the distance of their routes. Results also show the share of each pilot's counted flights synced from FlightLogger.
If you ask for a rematch, or challenge a member of one of your training groups who shows their username there, we email and send a push notification to that pilot (unless they've switched them off), and only they can join it. Nothing is compared unless they accept.
Your past self: a battle against your own earlier flying is worked out when you ask for it, shown only to you and not saved. Your trophy cabinet is worked out from the battle results we keep, for as long as your account lasts, and shows only you your own counts, never your opponents' names or figures.
Group battles: only if you start or join one
A member of a training group can start a battle that the group's other members can join. We email the other members to say it has started (unless they've switched off battle emails). You're only in it if you join it yourself, and you can leave it until it closes. It closes 24 hours after it starts, when its host closes it, or once every member has joined. Our server then compares the flights of everyone who joined over the battle's time window and saves the result: each pilot's totals for the rounds, their points and their place. The group's members (and anyone who took part, even after leaving the group) can see the result, with the usernames of the pilots who joined; nobody else can. Your individual flights, dates and routes are not shown. We email each pilot their place, unless they've switched off battle emails. The result can be opened on Battle Mode and the Groups page for 1 year after the battle closed. After that we keep it so it can appear in that year's Wrapped of the pilots who took part and in the group's Yearbook (where, as everywhere in a Yearbook, a pilot is only named if they chose to have a page). It's deleted with the group, and a pilot's entry with their account; a battle fewer than two pilots joined is deleted within 7 days.
Live group battles close to new pilots as above, then run forward from the next day; its pilots and the group's members can see the standings so far until the result is saved at the end.
Course battles: a member of a group can start a battle against another group using that group's join code. Both groups' members are emailed and sent a push notification (unless they've switched them off), and can join. If you join, the members of both groups can see your username and battle figures, and each group's averages are compared. It isn't in either group's Yearbook. It can appear in your Wrapped. Flight school cohort groups can't take part.
Training groups: only the groups you join
Training groups are private: only members can open a group, and you join one with its code. Members see statistics for the group worked out on our server: averages (flights per week, total hours, gap between flights) and counts (how many pilots are at each stage or progress level, and each aircraft type's share of the hours). Your individual flights are never shown to them.
Group statistics are shown however few members a group has, so friends can compare their training with each other. In a small group, members can work out each other's figures from the totals: in a group of two, for example, the averages together with your partner's own figures show your flights per week, total hours, average gap, syllabus progress and stage, and the aircraft you've flown. Only join groups with people you're happy to compare with. You can leave a group at any time, and its statistics stop including you straight away.
Other members aren't shown who is in a group. If you switch on Share my figures with this group, its members see your username with your flights per week, total hours, average gap and syllabus progress and stage; you can switch it off at any time.
Group Yearbooks. Once a member unlocks a group's Yearbook for a year, every member can download it as a PDF and share it with anyone they like. Your flights in that year count towards the class's totals, charts and records, but your username only appears if you switch on Give me a page in this group's Yearbooks: then you get a page of your own (your flights, hours and landings that year, your flying days, records, aircraft registrations, airports, biggest gaps, best month and worst week, battles between you and other members with a page, your places in the group's group battles, milestones and a forecast for next year) and your name is shown next to the class records you hold and the group battles you won. Without a page, a record you hold, or a group battle you won, says "a classmate". Your instructors, remarks and flight-by-flight logbook are never in a Yearbook. A Yearbook is made from the members' training at the moment it's downloaded, so switching your page off keeps you out of every copy downloaded afterwards, but we can't take back copies already downloaded.
Wrapped is yours alone: only you can open your Wrapped, and it's never on share links. The cards only reach anyone else if you share them.
Flight school statistics: anonymised
Any logged-in pilot can see anonymised statistics for a flight school, made up of every pilot who has picked that school in their Settings: the same averages as for groups. How many pilots that is is never shown: how they're spread across progress, stages and aircraft is given as percentages. Aircraft flown by just one pilot are counted under "Other", your individual flights, and your own figures, are never shown to anyone else.
How your training compares: percentages only
On the Groups page, each logged-in pilot sees where their own flight frequency, average gap between flights, current pace, share of weeks flown and longest gap stand among other PilotMetrics pilots with a verified email address, and among those on the same course, as percentages (for example "you fly more often than 72% of students"). Your figures count towards other pilots' percentages, but only the viewer's own position is shown: never anyone else's figures, names or flights.
Your instructor: only if you add one and they accept
If you add an instructor and they accept, they can see your training on their Instructor Dashboard, read-only: your flights (including instructor names, aircraft, airfields and remarks), cancellations, standby shifts, timeline events, ground school exams (subject, date, pass or fail, attempt and provider, but never scores or notes), your deadlines (your medical's expiry and class, if you've entered them), your upcoming FlightLogger bookings, your training plan and settings, and when you last logged in. Your deadlines are never shown on your share link. This works even if your profile is private. They can't change anything, and they never see your email address. They can set a flights-per-week target for you (stored with your instructor link), and can choose to get summary emails listing their students who may need attention, with your username and the reason (for example "No flight for 23 days"). It stops straight away if you remove them under Account > Instructor, if they remove you, or if they turn off Instructor Mode.
FlightLogger sync: only if you connect it
You can connect your own FlightLogger, with an API key you make in my|FlightLogger. We store the key encrypted, never show it again (only its last four characters), and use it only to read from FlightLogger, never to change anything there: every 3 hours on Free and every hour on Lite and Pro (and, for bookings that are new or changed, every hour on Free, every 30 minutes on Lite and every 5 minutes on Pro; with Pro, also when you click Sync now), we read your flights (their times, aircraft, airports, landings, logbook times, lesson and instructor) and your bookings and meetings, and add new flights, cancelled bookings and standbys (bookings or meetings marked "standby") to your logbook. We also keep your bookings for the next three weeks (date, times, aircraft, instructor and airport), replaced at every sync, to show what's coming up; they're deleted once their date has passed, when a later sync replaces them, or when you disconnect FlightLogger (or leave the school whose FlightLogger read them). FlightLogger is run by its own company, under its own privacy policy. If a synced flight or cancellation is changed or deleted in FlightLogger later, we keep a note of FlightLogger's version for you to approve or turn down on Flights. Disconnecting (Settings) deletes the key straight away; the flights already added stay in your logbook, as yours. A key your school's FlightLogger lets you make can read what FlightLogger shows you, so we only keep what's yours: other students' bookings are never stored.
Your flight school: only if you join it
If your flight school uses PilotMetrics for Flight Schools and you join it (by accepting its invite, or asking to join with its link and being approved), its staff can see your training while you're one of its active students, read-only, as an instructor can (see above): your flights, cancellations, standby shifts, timeline events, ground school exams (never scores or notes), your deadlines (your medical's expiry and class, solo authorisation and stall currency, if you've entered them), your upcoming FlightLogger bookings, training plan and settings, when you last logged in and when you last imported your logbook. They see figures worked out from it too: your pace, gaps, syllabus progress, how long you've spent in each stage, your projected finish (and, from the exams you've recorded, when your theory exam passes stop being valid for your licence's issue), your licence minimums, how long since your last flight and last solo flight, and how these compare with your cohort's averages. The school's staff are its owner, admins, training managers, instructors, schedulers and viewers; the school decides which of them can see every student and which only their own.
The school also keeps its own records about you: your cohort, base, course, start and expected finish dates, your instructors, tags, notes its staff write about your training (you don't see these), its notices and requests to you, and when your solo authorisation and stall currency expire, if it records them (you see these on your Deadlines, where they're used in place of the dates you entered while you're its student). The school is responsible for what it does with what it sees and records (it's a separate controller of that data); we hold it on the school's behalf and use it only to run the service for the school.
- What you agree to: joining lets the school see your training, and add flights from its own records to your logbook, marked as added by the school. If the school connects its FlightLogger, we read your flights and cancelled bookings from it every hour, as the school's FlightLogger user it links you to, and add new ones to your logbook and cancellation tracker; if one is changed or deleted in FlightLogger later, nothing changes in your logbook until you approve it on Flights. It can also add flights from its FlightLogger exports. Leaving the school stops this. Joining also means that when the school marks you as having finished, it keeps an anonymous record (your course, start and finish dates, flights and hours, and when you finished each phase of its syllabus and how long each took, with no name or account), which counts towards its "how long training takes" figures.
- Pro from your school: while you're an active student of a school that's paid up, your account has PilotMetrics Pro. A plan of your own is paused and carries on with the time it had left when the school's Pro ends.
- Sponsors, only if you agree: your school can ask you to let a sponsor (e.g. an airline cadet programme, an employer etc) follow your progress. Only if you agree, on your Account page, do the sponsor's people see your syllabus progress and stage, flights and hours, how often you fly, your projected finish and expected finish, and how many licence minimums you've met, with your username, course, cohort and the school's reference for you. Not your flights one by one, exam scores, notes or the school's own records about you. You can stop sharing at any time, and it stops when you leave the school. The sponsor is responsible for what it does with what it sees.
- Instructors' masses: the school can record its instructors' masses (in kg, by the name students' flights give them) for its active students' mass & balance. You see them, with the school's name and the date, on your Mass & Balance page; they're only counted once you confirm them for a flight. They're the school's records about its instructors, not about you.
- Leaving: you can leave the school at any time (it's told in its activity log, not by email), or the school can deactivate you. Either way it stops seeing your training straight away, and your account and flights stay yours. What it recorded about you (above) stays with the school, as its own records.
- Instructors' hours for the Forecast: the school can record each of its instructors' working hours a week, what they teach (aircraft types, the simulator, night) and the dates they're away (with an optional short note), to work out how much training it can deliver. Staff who see the school's Forecast see them, and changes are in its activity log. They're the school's records about its staff, kept until the school removes them or its account is closed.
- School reports and Wrapped: the school can make reports about its students (a student's progress, a cohort, the school, a cohort's progress meeting pack, a student's training record), each with a code checked at /verify-report, which shows the school and who or what the report is about. Its School Wrapped is totals and averages only: no student is named.
Us
We access your data only when we need to: to run and maintain the service, to fix problems, to respond to your requests, or where the law requires it.
If a court, regulator or law enforcement body makes a valid legal request, we may have to disclose data. Where we're allowed to, we'll tell you first.
Service providers
We use a small number of providers to run PilotMetrics. They act as our processors: they handle data only on our instructions and under contracts that protect it.
| Provider | Purpose | Location |
|---|---|---|
| Zettako | Web server, database and file hosting (all account and training data) | United Kingdom |
| Zettako | Delivering account and notification emails (your username, email address and the email content) | United States |
| PayPal | Processing Pro payments (see below). We never see or store your card or bank details. | United States |
| Google (Google Analytics) | Measuring how the site is used (see below) | Ireland and United States |
| Apple, Google or Mozilla (your browser's push service) | Delivering push notifications, only if you turn them on: an empty message to your device's push address, never what it says (see below) | United States or the EU |
PayPal (Pro purchases)
When you buy Pro, you pay through PayPal. PayPal collects your payment details itself and processes them as an independent controller, under PayPal's own privacy notice, not on our instructions. We send PayPal the price, a description of Pro and an internal reference for your account (not your name or email). PayPal sends us back the payment's result and the email address on the PayPal account that paid.
The checkout loads PayPal's buttons from paypal.com in your browser, so PayPal receives your IP address and browser details, and may set its own cookies, as soon as you open it. The donation window also loads PayPal's button when you open it, and works the same way.
Google Analytics
Every page loads Google Analytics, provided by Google Ireland Limited (with data processed by Google LLC in the United States), which acts as our processor. It sets the cookies listed under Cookies, so it can tell visits from the same browser apart. If you turn Analytics cookies off, they're deleted and Google receives only anonymous, cookieless signals that a page was viewed, which can't be linked to you or to your other visits. Google signals and advertising features are switched off, and we never send Google your account details, username, email address or training records. Links in our emails say which kind of email they're in (for example the weekly digest), so we can count visits from each kind; they never say who the email was sent to, and our emails have no tracking pixels, so we don't know whether you've opened one. See how Google uses information from sites that use its services.
Push notifications (only if you turn them on)
If you turn on notifications for a phone or computer (Account > Notifications), your browser gives us an address at its push service: Apple for Safari and the Home Screen app on iPhone and iPad, Google for Chrome and Edge, Mozilla for Firefox (in the United States or the EU, depending on the service). We store that address and its keys with your account, plus a short label for the device ("iPhone", "Chrome on Windows") and its time zone (from its browser, so notifications wait between 10pm and 6am where it is). When something happens, we send the push service an empty message for your device. Your device then collects what to show from our server, so the push services never see what a notification says, your username or your training. Notifications show on your lock screen, so they only say what happened (for example a booking's date, time and aircraft registration) and never your figures. Turn them off for a device, log out on it, or remove the site's permission in your browser, and its address is deleted.
Weather (Lite and Pro)
The weather on your flights and cancellations (the Flights page's history log) and the TAFs on your Dashboard come from public weather reports: past METARs from the Iowa Environmental Mesonet (Iowa State University, United States) and TAFs, and which airfields report them, from the US National Weather Service's Aviation Weather Center (aviationweather.gov). Our server asks them for an airfield's reports by its ICAO code and dates; it never sends your name, username, flights or anything else about you, and keeps the reports for every pilot who flies near that airfield. The airfield is a flight's departure airfield, a synced booking's, or otherwise where most of your flights start.
ADS-B import
The Flights page's ADS-B Import card looks flights up in public flight-tracking data: adsb.lol's daily archive of what its volunteer receivers saw (Open Database License), which it publishes on GitHub. Once a day our server reads that day's archive and notes where each aircraft's track is in it; when you look a flight up, it downloads only that aircraft's track for that day, by its place in the archive. If the archive doesn't name an aircraft's transponder address, our server asks hexdb.io for it by the registration alone. It never sends your name, username, flights or anything else about you, and keeps what comes back (about the aircraft, not about you) for every pilot who flies that aircraft, for up to 120 days. Your own matches are described under what we collect above.
Pre-Flight (free, for everyone)
When you look an airport up on the Pre-Flight page, our server asks the Aviation Weather Center (aviationweather.gov) for its latest METARs and TAF by the airport's code alone, and keeps them for a few minutes for everyone who looks at that airport. Its NOTAMs come from our own copy of every NOTAM, which our server keeps up to date from a NOTAM distribution service every few minutes, so looking them up sends nothing anywhere. Its runways and frequencies come from the public-domain OurAirports lists, which our server downloads. Nothing you do on the page is saved to your account: your recent airports, any runway headings you change or add and the last wind you entered stay in your browser's storage on that device. Its map loads from OpenStreetMap and the Leaflet software from unpkg, as on the Flight Map below.
The Airspace page's airspace, navaids, reporting points, obstacles, hotspots, hang gliding sites and RC airfields come from our own copy of openAIP's, which our server downloads once a day, so moving its map or adding a route sends nothing to openAIP. Looking an airport up on it works as on the Pre-Flight page. Its layers, last view, route and altitude stay in your browser's storage on that device; nothing on the page is saved to your account.
The Aerodromes page is drawn by our server from our own copy of openAIP's aerodromes (with runway lighting and links from the public-domain OurAirports lists), which it downloads once a day, so searching or opening an aerodrome sends nothing to openAIP. It keeps no contact details or telephone numbers openAIP has for an aerodrome. Nothing on the page is saved, in your browser or to your account; its map loads from OpenStreetMap and unpkg, as on the Flight Map below.
Flight Map (Pro)
When you open the Flight Map, your browser loads the map itself from two outside services: map images from OpenStreetMap (run by the OpenStreetMap Foundation, UK) and the Leaflet map software from unpkg (served through Cloudflare, United States). Like any website you visit, they receive your IP address and browser details, under their own privacy policies. Your flights, airports and routes are never sent to them: the map is drawn in your browser from data on our server. Airport locations come from the public-domain OurAirports list, which our server downloads; no personal data is involved.
Where your data is stored
Your account and training data are stored on our server in the United Kingdom.
Account and notification emails are sent through our email provider in the United States, so your username, email address and the content of those emails (including training figures in summaries) are transferred & stored there.
Google Analytics data (see Service providers) may be processed by Google in the United States, protected by Google's data processing terms.
How long we keep it
| Data | Kept for |
|---|---|
| Account details, training records and settings | Until you delete them or ask us to delete your account |
| Record of notification emails sent | Until your account is deleted |
| Push notification devices (the push service's address, its keys, a device label and its time zone) | Until you turn notifications off for that device, its browser stops accepting them, or your account is deleted |
| Push notifications waiting to be collected by your device | 7 days |
| Login session | Up to 30 days after your last visit, or until you log out |
| Security records (IP addresses in login, reset and code look-up attempts) | 90 days |
| Email verification, password reset and email change links | Valid for 1 to 48 hours, then deleted within 7 days of expiry |
| Battle codes nobody joined | Deleted within 7 days of expiring (codes can be joined for 24 hours) |
| Battles that started, and their results | Viewable with the code or result link for 7 days after the battle starts, and in both pilots' battle history for 1 year; the result is then kept for Wrapped and Yearbooks until either pilot's account is deleted |
| Group battles and their results | Viewable by the group's members and its pilots for 1 year after the battle closed; the result is then kept for Wrapped and Yearbooks until the group is deleted (a pilot's entry goes with their account). Deleted within 7 days if fewer than two pilots joined |
| Your figures for group and school statistics and the training comparison (flights per week, flight frequency, share of weeks flown, hours, average and longest gap, aircraft hours, course, syllabus progress and stage) and, if you've opted in, the monthly leaderboard (this month's and last month's totals), and your figures for each year (for Wrapped and Yearbooks), stored so these load quickly | Replaced whenever your training changes or the period they cover moves on; deleted with your account |
| Training group memberships | Until you leave the group, it's deleted, or your account is deleted. A group is deleted when its last member leaves. |
| A group's unlocked Yearbooks (which year, when, how and by whom) | Until the group is deleted. The Yearbook itself isn't stored: it's made from members' training each time it's downloaded |
| Instructor details and student-instructor links (including ended ones) | Until the student's or instructor's account is deleted |
| Web server logs | Forever |
| The days you used PilotMetrics | Until your account is deleted |
| Monitoring records and app usage counts (anonymous: no name, username, email, IP address or other identifier) | Forever |
| Google Analytics data linked to an Analytics cookie | 2 months, then only kept as anonymous totals; the cookies themselves expire after 2 years |
| Purchase records, including your agreement to start Pro straight away, and PayPal notifications | Forever, even if your account is deleted |
| Checkouts you started but didn't finish | Forever |
| Our record of changes we make to your account by hand (such as a plan given, a suspension, or deleting the account at your request): your username, what was done, when, and a note | Forever, even if your account is deleted |
| Your logbook backups (Settings > Backups) | Your newest 1 (Free), 5 (Lite) or 10 (Pro), until you delete them or your account is deleted |
| Endorsements, signatures and signature requests | Until you delete them or your account is deleted |
| Our server's backups of the whole database | 7 days, after which deleted data is gone from backups too |
When your account is deleted, your flights, cancellations, standbys, settings, files and battles are deleted with it. Purchase records are kept, because tax and accounting rules require us to keep records of payments, and so is our note that the account was deleted at your request. Groups you were in carry on without you (one you owned passes to its longest-standing member), and finished group battles you started stay with the other pilots, without your entry. When you ask us to delete your account, we close it straight away and delete it 72 hours later, so it can still be kept if you change your mind; we email you when it will be deleted.
Security
We take reasonable technical and organisational measures to protect your data, including:
- encrypted connections (HTTPS)
- one-way hashing of passwords and emailed links
- limits on repeated login, reset and code-guessing attempts
- logging out other devices when your password changes or you turn on two-factor sign-in
- optional two-factor sign-in for every account (a code from an authenticator app after your password), which a flight school can require of its staff
- optional passkeys, which log in with your device's screen lock and can't be phished
- keeping database credentials outside the public website.
No online service can be completely secure. Please use a strong password that you don't use anywhere else. If we become aware of a breach that is likely to put your rights at risk, we'll tell you and the ICO as the law requires.
Other people's data
Your training records may name other people, such as instructors, examiners or fellow students, for example in the instructor field, imported FlightLogger rows or remarks. Please only add other people's details where it's needed for your own training records, and keep remarks factual. Remember that if your profile is public, these details can be seen by anyone with your share link (see Who can see your data).
If you're named in someone's records and have a concern, contact us at [email protected].
Your rights
Under UK data protection law you have the right to:
- Access a copy of your personal data.
- Correct inaccurate data. You can edit most of it yourself in the app.
- Delete your data ("right to be forgotten").
- Restrict or object to how we use it, including uses based on legitimate interests. To stop your profile being shared, just make it private under Account.
- Data portability: ask us for a copy of your data in a machine-readable format.
- Withdraw consent at any time, for example by opting out of the leaderboard.
To use any of these rights, including deleting your account, email [email protected] from the address on your account. We may need to confirm your identity. We'll reply within one month, and there's normally no charge.
Age requirement
PilotMetrics is intended for people aged 13 and over. If you're under that age, please don't create an account without parental consent. If we learn that we hold data from a child below the minimum age, we'll delete it.
Changes to this policy
We may update this policy as PilotMetrics changes. We'll update the date at the top. If a change significantly affects how we use your data, we'll tell you by email or in the app before it takes effect.
Contact & complaints
Questions, requests or concerns: [email protected].
See also our Terms of Service.