Privacy policy

Last updated 12 October 2026 · Norsk

Logbook is a logbook app for iPhone and iPad for pilots and cabin crew, made by Peks AS. This policy explains what the app and logbook.no process, where it is kept, who can see it, how long it is kept and what your rights are.

1. Who is responsible

Peks AS is the controller for data processed on our servers and by our service providers. Apple keeps your logbook in iCloud on your behalf; we have no access to it. Send privacy questions to kontakt@logbook.no.

2. Your logbook

What you log or import: flights with date, route, times, aircraft, crew, remarks, signatures and photos; planned legs and roster codes from your roster; trips, aircraft and aircraft types; people you have flown with, with the name, employee number and contact details you enter; certificates, limits and settings.

• On the device. Deleted flights stay in the device's trash for 30 days.
• In your private iCloud database (CloudKit), so iPhone and iPad show the same.
• Settings in iCloud. Among them your name, employee number, home base, username, profile photo, your signature for the EASA logbook, which calendar is your roster, and your answers in Sleep and fatigue (how sleepy you were, and sleep you added or corrected).
• Backups in iCloud Drive (the Logbook folder), or on the device when iCloud Drive is off. Automatic backups are deleted after a year at the latest. Backups you make yourself are kept until you delete them.

What is in iCloud is tied to your Apple Account and processed by Apple under Apple's privacy policy. Turn off iCloud for Logbook in iOS Settings and everything stays on the device.

3. Permissions the app asks for

• Calendar: the app reads only the calendar you choose as your roster, also in the background to notice that your roster changed. Other calendars are not read, and nothing is written to the calendar.
• Health: sleep only, and only if you turn on Sleep and fatigue. Sleep is read and used on the phone, and what the model learns about you stays there. Health data is not synced, never sent to us, and the app writes nothing to Health. What the app shows is an estimate, not a medical assessment.
• Location: once, when you add a new flight, to suggest the nearest airport. It is not stored or sent anywhere.
• Photos: only the photos you pick, for flights, aircraft, your profile or a wallpaper under Tools. The wallpapers you make are saved to Photos when you ask; they never leave the phone.
• Notifications: see section 8.

The motion sensor only drives a visual effect on the welcome screen. The app does not use the camera, the microphone or your contacts.

4. Features that use our server

Our server is a database with a few small server functions at Supabase in the EU (Stockholm), and our own server for the website and the e-mail import. These features work without an account too:

The aircraft directory

To show the name, age and photo of the aircraft you have flown, the app sends the registrations in your logbook, such as LN-RGL, to our server. When we do not know an aircraft, the server looks it up at AeroDataBox and keeps the answer in a shared aircraft directory. Photos come straight from Planespotters.net, which therefore sees your IP address and the registration. On our side these requests are not tied to you.

Roster codes and news

The app fetches the list of known roster codes for your airline and the changelog from our server, and asks the App Store whether a new version is out.

Live Activity on duty days

So that the Live Activity (gate, departure time and the day's flights on the Lock Screen) appears three hours before check-in without opening the app, the app sends our server the next 14 days of duties: the start and end time, the first flight's number, route and times, and a push address from Apple for this device. It is tied to a random code made on the device, not to your account. The server uses it to send the push that opens the Live Activity, and to update it 75 and 30 minutes before each flight with the gate and any new time: for Norwegian airports from Avinor's public flight data (shown as "Flydata fra Avinor"), elsewhere from our flight status service if you have Logbook Pro, for which the app also sends its Pro receipt. Each duty is deleted a day after it ends. Turn it off under Settings › Notifications, which deletes the duties not yet started.

Import by e-mail

SAS Airside and Flighty can only send their exports by e-mail. The app therefore makes a random code on the device and shows an address, import_<code>@logbook.no. Mail sent there lands in a mailbox at the mail provider Purelymail. Our server collects it, puts the attachment in a private storage bucket at Supabase and deletes the mail. The app fetches the file and reads it on the device, and the file is then deleted on our side. Files that are never fetched are deleted at the next clean-up after 24 hours. We do not read the contents, but the server keeps an operations log for each mail: sender, recipient address, and the attachment's name and size, plus the subject when the mail has no valid code.

So that the app can fetch the file without you opening it, it registers the device's push address from Apple together with the code when it starts. This also happens if you do not use import by e-mail. The push address is not tied to any account and is deleted when Apple reports that it is no longer in use.

Live flight status (Logbook Pro)

For planned legs in the next 24 hours, the app sends the flight number, date and departure airport to our server, together with Apple's signed receipt for your subscription and your sign-in if you are signed in. The server asks AeroDataBox for gate, times and aircraft. The answer is kept in a shared cache that is not tied to you, and the aircraft is added to the aircraft directory. The receipt is only used to check the subscription and is not stored.

5. Account

An account is optional and only needed for friends, the shared roster, suggestions and chat with the team. You sign in with Apple. Apple gives us an anonymous user ID and an e-mail address, which may be Apple's relay address if you hide your own. The name Apple shares is kept only in the app, as your name.

• The sign-in: user ID, e-mail address, when the account was created and when you last signed in.
• Visible to other signed-in users: username, name, airline, role (pilot or cabin), profile photo if you add one, when the account was created, and whether you share your roster.
• Visible only to you: your e-mail address, employee number and which notifications you want. The employee number is used to recognise your own legs in files from your airline.
• For notifications: the push address from Apple for each device you are signed in on. It is removed when you sign out.

Please use a private e-mail address, not your work address. Your employer can read work e-mail, so the app does not accept addresses from known airlines.

Deleting your account: Settings › Profile › Delete account. This deletes your profile, photo, private details, push addresses and everything else tied to the account, such as friendships, the shared roster, chat, suggestions, comments, votes and blocks, and we revoke the access at Apple. Three things remain: feedback you sent, no longer tied to you and without e-mail address and screenshot; reports you filed, no longer tied to you; and the admin log, which may contain your name and username if the team took action on your account. The logbook on your devices and in iCloud stays.

6. Friends and the shared roster

A friendship needs both to say yes. Friends see this from your roster, from 30 days back and as far ahead as your roster goes:

• Days without flying: only the kind of day (off, vacation, standby, training or other duty), not the roster code or the times.
• Flights: route, departure and arrival time, flight number, aircraft type and whether the flight is planned or flown. Simulator sessions are not shared.

Block time, PF, landings, remarks, crew and the rest of the logbook are never shared. Sharing is on when you create an account. You can turn days and flights off separately under Settings › Profile, which deletes what was shared at once. The app updates what it shares when it opens and something has changed, and then removes anything older than 30 days. Remove a friend or block someone and you no longer see each other's roster.

Phone number

You can add a mobile number to your profile so friends can call, text or WhatsApp you. It is stored apart from the profile and is off until you turn on "Show to my friends". Then only friends you have accepted can read it, never people who find you in search, crew on layover or others in your company; the database enforces this. Turn the switch off, remove the friend or block them, and it is hidden at once. Calls and messages go through your phone's own apps, not through Logbook. Remove the number and it is deleted.

Crew in the same city

When turned on in the profile, verified crew on layover in the same city at the same time can see each other. It is off by default. While you are on a layover we store the airport, city and country, when you leave (to hide you afterwards), and as much of the departure time as you chose to show: part of the day, the exact time or nothing. The others see your name, username, company and that departure time. Outside your own company only your first name and the initial of your last name are shown, and only when both chose "All verified crew". You only see others while you share yourself. Your hotel and the rest of your roster are never shared. The entry is replaced when the roster changes and deleted when the layover is over or you turn the feature off.

To take part, your company must be verified. That happens when you send an export from SAS Airside to your import address: our mail server checks that the mail came from SAS (sender and DKIM/DMARC), and we store only that the account is verified for SAS and a keyed hash of the employee number in the file name, so one employee number cannot verify several accounts. The employee number itself is not stored for this. Unclaimed proofs are deleted after 30 days.

7. Feedback, suggestions and chat

• Feedback (shake the phone, Settings, the contact form on logbook.no, or the form for other airlines in the welcome): the text, app version, device model and iOS version, the airline you chose, your account if you are signed in, your e-mail address if you give it, and a screenshot if you leave it attached. The screenshot is attached by default, and you see it before you send. Only the team reads feedback.
• Suggestions, comments and votes are visible to all signed-in users with your name, and other signed-in users can see who voted for what. You can delete your own suggestions and comments.
• Aircraft names: when you suggest a name for an aircraft, the suggestion is kept with your account. When two accounts suggest the same name, it becomes the aircraft's name in the directory, not tied to you.
• Roster codes: when you decide what an unknown roster code means while signed in, the code, your airline and your choice are sent as a suggestion, so the code can be added for everyone at your airline. The suggestion is deleted once handled.
• Chat with the team: your messages and the replies, and any pictures sent in the chat, are kept with your account, read only by you and the team, and deleted with the account. We also keep when messages were read. A screenshot sent with feedback can have your drawing on it.
• Reports: when you report a user, a suggestion or a comment, we keep who reported, the reason, what you wrote and a copy of what was reported. The person you report is not told who reported them.
• Blocking: we keep whom you blocked, so it works on all your devices. The person you block is not told.
• Moderation: when an account breaks the terms, the team can stop it from posting suggestions, sending friend requests, reporting or chatting for a period, or close the account. The app shows you what applies and why.

What the team sees: in the admin tools the team sees profiles, when an account last signed in, the number of devices, activity, reports, restrictions, chat, feedback with e-mail address, and the waiting list. The team does not see your logbook, nor the employee number or e-mail address on your account. What the team does is logged, so mistakes can be put right. Whoever operates the database has technical access to everything stored in it and uses it only to run and fix the service.

8. Notifications

• From the app itself: before certificates and currencies expire, when your upcoming roster changes, when an export sent by e-mail has been imported, and in Sleep and fatigue a reminder the evening before a duty that looks harder than usual, and a question after landing about how sleepy you were.
• From the server, with an account: friend requests and replies, comments and status changes on suggestions, and replies from the team in the chat. These go through Apple's push service and may contain the sender's name, the suggestion's title or the text of the chat message.
• A silent notification without text when a file has arrived at your import address.

Choose which notifications you want under Settings › Notifications, and turn them off in iOS Settings.

9. Logbook Pro

The subscription is bought and paid for through Apple. We never receive card details, your name or other payment information. When the app fetches live flight status, it shows our server Apple's signed receipt, which is only used to confirm that the subscription is valid. Testers we have given Pro are on a list tied to their account. More in the terms.

10. The website and the waiting list

logbook.no has no cookies, tracking or analytics. The server may keep technical logs, such as IP address and time, for operations and security.

Waiting list: when you sign up at logbook.no/bli-med, we keep your e-mail address and whatever else you fill in: name, whether you are pilot or cabin crew, airline and which logbook you use today. It is only used to invite you to the beta and tell you about it. Invitations are sent through the e-mail service Resend. Once we have sent an invitation, your e-mail address is also in the admin log. Write to kontakt@logbook.no and we will delete you.

The contact form on the support page is stored as feedback, see section 7.

11. Service providers

These process data for us or for you. Apple, Purelymail, Resend, AeroDataBox and Planespotters may process data outside the EEA.

12. How long we keep data

13. Legal basis

• Contract (GDPR art. 6(1)(b)): what the features you ask for need, such as the account, sharing, chat, import by e-mail, the aircraft directory, flight status and the subscription.
• Consent (art. 6(1)(a)): the waiting list, e-mail address and screenshot in feedback, and the permissions you grant in iOS. Health data is processed only on your device, with your consent. You can withdraw consent at any time.
• Legitimate interest (art. 6(1)(f)): security, operations logs, moderation, the admin log and improving the app from feedback.

14. Your rights

You can ask for access, correction, deletion, restriction and a copy of your data, and you can object to processing based on legitimate interest. You control your logbook in the app: correct and delete what you like, export everything as a backup (JSON), CSV or EASA PDF, or reset the logbook under Settings. For data we hold, write to kontakt@logbook.no and we will answer within 30 days. If you think we process data unlawfully, you can complain to the Norwegian Data Protection Authority, Datatilsynet.

15. Security, children and changes

Security: all traffic is encrypted. In the database each user sees only their own data and what others chose to share. Supabase encrypts stored data. Your sign-in and import code are kept in the device's keychain.

Children: the app is made for flight crew and is not directed at children under 16.

Changes: when we change this policy, we update the date at the top. We tell you about major changes in the app.

Peks AS · kontakt@logbook.no