Logger – Pilot Logbook

Logbook signing

Privacy notice for signers

Last updated 29 September 2026. This notice supplements the Logger privacy policy, which applies to pilots using the app.

You are reading this because a pilot who uses the Logger app asked you to sign entries in their logbook — as their instructor, examiner, or the pilot-in-command they flew with. This notice explains what happens with your information when you do.

Who is responsible

737 Publishing s.r.o., Jaurisova 515/4, Praha 4, Michle, 140 00, Czech Republic (“we”), is the data controller. Contact: support@getlogger.com.

Where your information comes from

The pilot enters your email address in the Logger app to send you the request. We did not obtain it from any other source. Everything else listed below you provide yourself when you sign.

What we process

• Email address — to deliver the request and to verify that the person signing controls that address (passwordless sign-in link). Signing in creates a Firebase Authentication account for that address; no password is stored.
• Name and licence/certificate number — as you type them when signing; they identify you on the pilot's record. We also record whether you told us the certificate is FAA-issued, and its expiry date if so, because 14 CFR 61.51(h)(2)(ii) requires that date on training entries.
• Your signature — stored as a small vector drawing (the strokes you draw, or your typed name rendered in a script font), not as an image or biometric template. Whether it was drawn or typed is recorded.
• Time of signing and the identifier of the request.
• The pilot is told you signed — a notification may be sent to their devices giving your name and how many entries you signed, so their app knows to collect the signature.
• Technical data collected by Firebase Authentication for security, such as the IP address and time of sign-in.

We also show you the pilot's entries so you can check them before signing (dates, aircraft, routes, logged times, block times, approaches flown, the names of other crew on the flight, and remarks; or certificate names, numbers, categories and dates). That is the pilot's information, shown to you on their request, and it is not linked to you except through your signature.

Why, and on what legal basis

• To deliver the request, verify your identity and record your signature — our legitimate interest, and the pilot's, in providing a verifiable way to sign logbook entries remotely (GDPR Art. 6(1)(f)). Pilots are required by aviation regulations (e.g. EASA Part-FCL.050, FAA 14 CFR 61.51) to keep a logbook whose entries may need to be certified by an instructor, examiner or pilot-in-command, and to be able to show it to their aviation authority on request. Your signature is that certification.
• Where the entries you sign concern a medical certificate, the pilot chose to share that with you by sending the request (Art. 9(2)(a)); we only display what the pilot entered, and it is not processed further.

We do not use your information for marketing, profiling or any other purpose.

How long we keep it

• The signing record (request, your name, licence number, email, signature, time of signing) is kept for as long as the pilot's logbook may need to be verified by an aviation authority, and at least as long as the pilot keeps their Logger account. It is the durable evidence that a specific entry was signed by a specific person at a specific time, and it cannot be edited after signing — by the pilot, by you, or by us.
• Delivery copies written to the pilot's logbook are deleted by the app once applied, and automatically after 90 days at the latest.
• The email we sent you is kept in our sending queue for up to 30 days, then deleted.
• Your sign-in account exists until you ask us to delete it.
• The receipt we email you, and the file attached to it listing what you signed, are yours. They sit in your mailbox, not on our systems, and we cannot withdraw or delete them. If you are a flight instructor signing under FAA rules, 14 CFR 61.189 requires you to keep your own record of the training you give for three years, and the attachment is written to serve that purpose.

Who receives it

• The pilot — your name, licence number, issuing authority, certificate expiry where you gave one, and your signature become part of their logbook, on their device.
• Google (Firebase / Google Cloud) — stores and transmits the data on our behalf as our processor; it may not use it for its own purposes. Data is stored in the European Union; some processing (such as sign-in and sending email) takes place in the United States, where Google is certified under the EU-US Data Privacy Framework and bound by the EU standard contractual clauses in its data-processing terms.

We do not sell or share your information with anyone else.

Your rights

You can ask for access to, correction of, or deletion of your information, object to processing, or ask us to restrict it, by emailing support@getlogger.com. Because a signature is a certification of someone else's regulatory record, we may have to refuse to delete or alter the signing record itself while the pilot's logbook remains subject to verification; we will explain if that is the case. You can complain to your data protection authority — in the Czech Republic, the Úřad pro ochranu osobních údajů (uoou.gov.cz).

If you were not expecting this

If you do not know the pilot or did not expect a request, ignore the email. Nothing is stored about you unless you sign in and sign. To stop further requests from a particular pilot, contact us.

How Logger signatures work · Logger is operated by 737 Publishing s.r.o. · getlogger.com