Privacy Policy
This privacy policy applies between you, the User of the Logger app and 737 Publishing s.r.o., the owner and provider of this Logger app. 737 Publishing s.r.o. takes the privacy of your information very seriously. This privacy policy applies to our use of any and all Data collected by us or provided by you in relation to your use of the App.
Please read this privacy policy carefully.
Definitions and interpretation
In this privacy policy, the following definitions are used:
Data — collectively all information that you submit to 737 Publishing s.r.o. via the App. This definition incorporates, where applicable, the definitions provided in the Data Protection Laws;
Data Protection Laws — any applicable law relating to the processing of personal Data, including but not limited to the GDPR and any national implementing laws, regulations and secondary legislation, for as long as the GDPR is effective in the Czech Republic;
GDPR — the General Data Protection Regulation (EU) 2016/679;
737 Publishing s.r.o., we or us — 737 Publishing s.r.o. of Jaurisova 515/4, Praha 4, Michle, 140 00, Czech Republic;
User or you — any third party that accesses the App and is not either (i) employed by 737 Publishing s.r.o. and acting in the course of their employment or (ii) engaged as a consultant or otherwise providing services to 737 Publishing s.r.o. and accessing the App in connection with the provision of such services;
Signer — a person who is not necessarily a User and whom a User asks, through the App, to sign entries in the User's logbook (for example an instructor, an examiner or a pilot-in-command). Where this privacy policy refers to "you" in the section headed "Remote signatures", it applies equally to a Signer where the context requires; and
App — the Logger – Pilot Logbook application that you are currently using, the logbook-signing website at sign.getlogger.com, and any related products unless expressly excluded by their own terms and conditions.
In this privacy policy, unless the context requires a different interpretation:
the singular includes the plural and vice versa;
references to sub-clauses, clauses, schedules or appendices are to sub-clauses, clauses, schedules or appendices of this privacy policy;
a reference to a person includes firms, companies, government entities, trusts and partnerships;
"including" is understood to mean "including without limitation";
reference to any statutory provision includes any modification or amendment of it;
the headings and sub-headings do not form part of this privacy policy.
Scope of this privacy policy
This privacy policy applies only to the actions of 737 Publishing s.r.o. and Users with respect to this App. It does not extend to any apps or websites that can be accessed from this App including, but not limited to, any links we may provide to social media websites.
For purposes of the applicable Data Protection Laws, 737 Publishing s.r.o. is the "data controller". This means that 737 Publishing s.r.o. determines the purposes for which, and the manner in which, your Data is processed.
Data collected
We may collect the following Data, which includes personal Data, from you:
name;
contact information such as email addresses;
user ID;
purchase history;
operating system (automatically collected);
logbook entries you choose to send for signature, and the signature data described in the section headed "Remote signatures";
a registration identifier for each device you sign in on, so that we can notify the App when a signature arrives (see "Remote signatures");
in each case, in accordance with this privacy policy.
We collect the following data which is not linked to you:
general usage data;
crash and error reports.
How we collect Data
We collect Data in the following ways:
data is given to us by you; and
data is collected automatically.
Data that is given to us by you
737 Publishing s.r.o. will collect your Data in a number of ways, for example:
when you sign in through "Sign In With Apple";
when you send a signing request, or sign one, as described under "Remote signatures";
in each case, in accordance with this privacy policy.
Data that is collected automatically
To the extent that you access the App, we will collect your Data automatically, for example:
when you make a purchase. This information helps us to make improvements to App content and navigation, and includes your user ID, the date, time and country the purchase was made in;
when the App crashes. Data about the crash is sent automatically for analysis; it is not linked to your identity.
Our use of Data
Any or all of the above Data may be required by us from time to time in order to provide you with the best possible service and experience when using our App. Specifically, Data may be used by us for the following reasons:
internal record keeping;
improvement of our products / services;
in each case, in accordance with this privacy policy.
We may use your Data for the above purposes if we deem it necessary to do so for our legitimate interests. If you are not satisfied with this, you have the right to object in certain circumstances (see the section headed "Your rights" below).
For the delivery of direct marketing to you via e-mail, we will need your consent, whether via an opt-in or soft-opt-in:
soft opt-in consent is a specific type of consent which applies when you have previously engaged with us (for example, you contact us to ask us for more details about a particular product/service, and we are marketing similar products/services). Under "soft opt-in" consent, we will take your consent as given unless you opt-out;
for other types of e-marketing, we are required to obtain your explicit consent; that is, you need to take positive and affirmative action when consenting by, for example, checking a tick box that we will provide;
if you are not satisfied about our approach to marketing, you have the right to withdraw consent at any time. To find out how to withdraw your consent, see the section headed "Your rights" below.
When you register with us and set up an account to receive our services, the legal basis for this processing is the performance of a contract between you and us and/or taking steps, at your request, to enter into such a contract.
Keeping Data secure
We will use technical and organisational measures to safeguard your Data, for example:
access to your account is controlled by Sign in with Apple; Signers can open a signing request only through a single-use link sent to their email address, and no password is stored for them;
we store your Data on secure servers;
payment details are encrypted using SSL technology (typically you will see a lock icon or green address bar (or both) in your browser when we use this technology).
Technical and organisational measures include measures to deal with any suspected data breach. If you suspect any misuse or loss or unauthorised access to your Data, please let us know immediately by contacting us via this e-mail address: support@getlogger.com.
If you want detailed information from Get Safe Online on how to protect your information and your computers and devices against fraud, identity theft, viruses and many other online problems, please visit www.getsafeonline.org. Get Safe Online is supported by HM Government and leading businesses.
Data retention
Unless a longer retention period is required or permitted by law, we will only hold your Data on our systems for the period necessary to fulfil the purposes outlined in this privacy policy or until you request that the Data be deleted. Signing records are retained for longer, as explained under "Remote signatures", because they certify entries in a logbook that aviation regulations require you to keep and to present to your aviation authority on request.
Even if we delete your Data, it may persist on backup or archival media for legal, tax or regulatory purposes.
Your rights
You have the following rights in relation to your Data:
Right to access — the right to request (i) copies of the information we hold about you at any time, or (ii) that we modify, update or delete such information. If we provide you with access to the information we hold about you, we will not charge you for this, unless your request is "manifestly unfounded or excessive." Where we are legally permitted to do so, we may refuse your request. If we refuse your request, we will tell you the reasons why;
Right to correct — the right to have your Data rectified if it is inaccurate or incomplete;
Right to erase — the right to request that we delete or remove your Data from our systems;
Right to restrict our use of your Data — the right to "block" us from using your Data or limit the way in which we can use it;
Right to data portability — the right to request that we move, copy or transfer your Data;
Right to object — the right to object to our use of your Data including where we use it for our legitimate interests.
To make enquiries, exercise any of your rights set out above, or withdraw your consent to the processing of your Data (where consent is our legal basis for processing your Data), please contact us via this e-mail address: support@getlogger.com.
If you are not satisfied with the way a complaint you make in relation to your Data is handled by us, you may be able to refer your complaint to the relevant data protection authority. In the Czech Republic this is the Úřad pro ochranu osobních údajů (uoou.gov.cz).
It is important that the Data we hold about you is accurate and current. Please keep us informed if your Data changes during the period for which we hold it.
Transfers outside the European Economic Area
Data which we collect from you may be stored and processed in and transferred to countries outside of the European Economic Area (EEA). For example, this could occur if our servers are located in a country outside the EEA or one of our service providers is situated in a country outside the EEA.
We will only transfer Data outside the EEA where it is compliant with data protection legislation and the means of transfer provides adequate safeguards in relation to your Data, e.g. by way of a data-processing agreement incorporating the current standard contractual clauses adopted by the European Commission, or where the organisation in receipt of the Data is based in the United States of America and certified under the EU-US Data Privacy Framework.
To ensure that your Data receives an adequate level of protection, we have put in place appropriate safeguards and procedures with the third parties we share your Data with. This ensures your Data is treated by those third parties in a way that is consistent with the Data Protection Laws.
Links to other websites
This App may, from time to time, provide links to other websites. We have no control over such websites and are not responsible for the content of these websites. This privacy policy does not extend to your use of such websites. You are advised to read the privacy policy or statement of other websites prior to using them.
Changes of business ownership and control
737 Publishing s.r.o. may, from time to time, expand or reduce our business and this may involve the sale and/or the transfer of control of all or part of 737 Publishing s.r.o. Data provided by Users will, where it is relevant to any part of our business so transferred, be transferred along with that part and the new owner or newly controlling party will, under the terms of this privacy policy, be permitted to use the Data for the purposes for which it was originally supplied to us.
We may also disclose Data to a prospective purchaser of our business or any part of it.
In the above instances, we will take steps with the aim of ensuring your privacy is protected.
General
You may not transfer any of your rights under this privacy policy to any other person. We may transfer our rights under this privacy policy where we reasonably believe your rights will not be affected.
If any court or competent authority finds that any provision of this privacy policy (or part of any provision) is invalid, illegal or unenforceable, that provision or part-provision will, to the extent required, be deemed to be deleted, and the validity and enforceability of the other provisions of this privacy policy will not be affected.
Unless otherwise agreed, no delay, act or omission by a party in exercising any right or remedy will be deemed a waiver of that, or any other, right or remedy.
This Agreement will be governed by and interpreted according to the law of the Czech Republic. All disputes arising under the Agreement will be subject to the exclusive jurisdiction of the Czech courts.
Remote signatures
This section applies to Users who send signing requests and to Signers who receive them.
Logger lets you ask another person — an instructor, examiner or the pilot-in-command you flew with (the "Signer") — to sign entries in your logbook remotely. When you use this feature we process additional Data, and we also process Data about the Signer, who may not be a User of the App.
Data we process
About you (the pilot)
your user ID and the name shown in your profile, which we show to the Signer and include in the request email so they know who is asking;
the Signer's email address, which you enter;
a copy of the logbook entries you selected, exactly as the Signer sees them. Assume that everything recorded on an entry is shown. The Signer is not given a summary: every field you have filled in on that flight or certificate is displayed to them, and fields added to the App in future are shown too. Two kinds of field are never sent: what you record for yourself — private notes, tags and custom times — and operational data that has no place in an authority logbook, namely duty and scheduled times, Hobbs/Tach, distance and fuel. As an illustration, for a flight that typically means the date, entry type, aircraft type and registration, route, block times, every logged time, landings and other counts, approaches, crew names and remarks; for a certificate, the name, number, category (e.g. medical, rating, licence, endorsement), issuing body, examiner, issue and expiry dates, endorsement and remarks. You choose which entries to include; do not include information you do not want the Signer to see.
Other people named on an entry. Normally an entry names only you and the Signer. Where you have also recorded someone else — another crew member, or an instructor or examiner who is not the person you are asking to sign — that name is part of the entry and is shown to the Signer along with it, and kept in the signing record. We do not use those names for anything else and never contact the people named; we usually hold nothing but a name and have no way of reaching them, which is why this notice is where we set out what happens to it (GDPR Art. 14(5)(b)). Because you are the one who knows who those people are, it is your responsibility to have their agreement before you send an entry that names them, or to remove the name from the entry first. Anyone named in an entry can contact us at support@getlogger.com; we may have to keep the signing record while your logbook remains subject to verification by an aviation authority, and we will explain if that is the case.
About the Signer
their email address (entered by you) and the technical data collected by Firebase Authentication when they sign in with the emailed link (such as IP address and time);
the name and licence/certificate number they enter when signing, which authority issued it, and, for an FAA certificate, its expiry date (14 CFR 61.51(h)(2)(ii) requires that date on training entries);
their signature, stored as a small vector drawing (the strokes drawn, or their typed name rendered in a script font), and whether it was drawn or typed;
the time of signing.
Why we process it and on what basis
We process this Data to deliver the request, to verify that the signature comes from the person you addressed it to, and to return the signature to your logbook. The legal basis is the performance of our contract with you (GDPR Art. 6(1)(b)) and, for the Signer's Data, our and your legitimate interest in providing a verifiable way to certify logbook entries remotely (Art. 6(1)(f)). Pilots are required by aviation regulations (for example EASA Part-FCL.050 and 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 present it to their aviation authority on request; a remote signature is that certification.
Where the entries concern a medical certificate, sharing it with the Signer is your decision when you send the request (Art. 9(2)(a)); we display what you entered and do not process it further.
How long we keep it
The signing record — the request, the entries as shown to the Signer, the Signer's name, licence number, issuing authority and email, the certificate expiry date where one was given, their signature and the time of signing — is kept for as long as your logbook may need to be verified by an aviation authority, and at least as long as you keep your Logger account. It exists so that it can be shown that a specific entry was signed by a specific person at a specific time. Once signed it cannot be changed by you, by the Signer, or by us.
Delivery copies used to transfer the signature into your logbook are deleted by the App once applied, and automatically after 90 days at the latest.
Request and receipt emails, including the attached copy of what was signed, are kept in our sending queue for up to 30 days and then deleted.
Signer sign-in accounts exist until the Signer asks us to delete them.
Notifications. So that the App can tell you a signature has arrived even when it is closed, we store a registration identifier for each device you are signed in on, and send it a notification through Apple's Push Notification service when a request you sent is signed. The notification says who signed and how many entries; it carries no logbook data and confers no access. The identifier is removed when you sign out on that device, and we delete it when Apple reports it is no longer valid.
Your logbook itself, including applied signatures, is stored on your device and in your iCloud account as described elsewhere in this policy; the signing record described here is a separate copy held by us.
Where it is processed
Signing Data is stored in the European Union by Google (Firebase / Google Cloud), our hosting and email provider acting as our processor. 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.
Who receives it
You can see the requests you have sent and their status in the App.
The Signer sees the entries you selected. Their access through the App ends when the request does — a request expires 14 days after it is sent unless you set otherwise, and ends immediately if you withdraw it — and Signers can never see other entries, other requests, or your logbook.
The Signer keeps a copy of what they signed. When they sign, we email them a receipt with a file attached listing the entries they certified, in the same detail the App showed them. That file is their record of a certification they are responsible for, and aviation regulations may require them to keep it — 14 CFR 61.189 asks a flight instructor to keep three years of such records. Once sent it is in their mailbox: it is outside our control and outside the App, we cannot withdraw it, and the limits above on what they can see through the App do not apply to it. If an entry names someone else, that name is in the file too — see "Other people named on an entry" above.
Google (Firebase / Google Cloud) stores and transmits the Data on our behalf as our processor, as described above; it may not use it for its own purposes.
We do not use signing Data for marketing or profiling.
Your rights, and the Signer's
Both you and the Signer have the rights described under "Your rights". A signature is a certification of a regulatory record, so we may have to refuse to delete or alter a signing record while your logbook remains subject to verification; we will explain if that is the case. If you delete your Logger account, your pending requests and delivery copies are deleted; completed signing records are retained as described above. Signers can ask us to delete their sign-in account at any time via support@getlogger.com.
The Signer-facing version of this section is published at sign.getlogger.com/privacy and is linked from every request email.
Referral programme
This section applies if you share your referral code with someone ("the referrer") or use someone else's code ("the friend").
When a friend who is a new Logger PRO subscriber uses a referrer's code, each of them can claim one free month: the App Store moves their next renewal date back by 30 days. To run the programme and keep it fair we process the following Data.
Data we process
your user ID and your referral code;
the identifier our subscription provider, RevenueCat, uses for your purchases — this is the identifier Sign in with Apple gives the App, not your email address;
for each referral, the user IDs of the referrer and the friend, the code used and when it was entered;
subscription information needed to decide whether you can take part and to give the free month: whether and when you were first charged for Logger PRO, whether your subscription is currently active and paid by you through the App Store (rather than shared through Family Sharing), whether you have bought with an App Store offer code, refunds, and your subscription's transaction identifier. We receive this from RevenueCat, and where needed from Apple's App Store Server API, which may include reading your App Store transaction history for Logger to check for offer codes;
the free months given: when each was claimed, the new renewal date, and a record of every extension of your subscription (Apple allows two per year);
the device registration identifier described under "Remote signatures", which we also use to tell you that a friend has joined with your code, that a free month is ready, or to remind you once that it has not been claimed;
the referrer's user ID, stored with RevenueCat against the friend's purchases so that we can see how subscribers found us.
What the other person in a referral can see
The referrer and the friend can both see their shared referral in the App: its status, when the friend's first payment was made, when the referrer's free month becomes available, whether each free month has been claimed, and, if the referral was cancelled, the reason — a refund, the friend's subscription ending within 14 days of their first payment, or the use of an offer code. Neither sees the other's name or email address. If you would rather the referrer did not learn this about your subscription, do not use a referral code.
Why we process it and on what basis
To run the programme and give you your free month — the performance of our contract with you (GDPR Art. 6(1)(b)), under the programme's terms.
To keep the programme fair and prevent abuse — checking that a friend is a genuinely new subscriber, has not used an offer code, was not referred in a loop, that a referrer has paid and that the friend is still subscribed after 14 days, and applying Apple's limit of two extensions a year — our legitimate interest (Art. 6(1)(f)).
These checks are made automatically. They only decide whether a free month is given; if you think one was wrongly refused, contact us at support@getlogger.com and we will review it. We do not use referral Data for marketing or profiling.
How long we keep it
Referrals, your referral code and your free-month records are kept while you have a Logger account.
The record of your App Store purchases (whether and when you were first charged, offer-code use, refunds, and transfers of your purchases) and the record of extensions to your subscription are kept for as long as the referral programme runs, including after you delete your account. Without them, a new account could be used to take part again as a "new subscriber", and Apple's yearly limit could not be applied.
Notifications we receive from RevenueCat about purchases are kept for 30 days to avoid processing them twice.
If you delete your account
Your referral code stops working and your referral profile is deleted. Referrals you were part of are kept so that the other person can still see and claim their free month, but your user ID is removed from them; any free month of yours that you had not yet claimed is lost. We keep the purchase and extension records described above.
Who receives it
The other person in each referral — see "What the other person in a referral can see".
RevenueCat, our subscription provider, processes purchase Data on our behalf as our processor. It is based in the United States and certified under the EU-US Data Privacy Framework.
Apple receives our request to extend your subscription, and our requests for your App Store transaction information, through the App Store Server API. Apple processes this as part of your App Store account, under Apple's own privacy policy.
Google (Firebase / Google Cloud) stores the referral Data in the European Union and sends notifications, as our processor, as described under "Remote signatures".
Changes to this privacy policy
737 Publishing s.r.o. reserves the right to change this privacy policy as we may deem necessary from time to time or as may be required by law. Any changes will be immediately posted on the Website with a link provided through the App. You are deemed to have accepted the terms of the privacy policy on your first use of the App following the alterations.
You may contact 737 Publishing s.r.o. by email at support@getlogger.com.
Last updated: 23 October 2026
