Privacy Policy

Version 2026-10-18 — last updated 18 October 2026

This policy explains what personal data this Service collects, why, and what rights you have. It is written to meet the UK General Data Protection Regulation (UK GDPR) and, where it applies, the EU GDPR.

1. Who is responsible for your data

The operator of this website is the data controller for the personal data described here. Contact details are published on this website. If you have a question about this policy or your data, please use them.

2. What we collect, and why

We only collect what the Service needs to work. Nothing here is sold, and nothing is used for advertising profiling.

Account and identity

• Email address — to identify you, sign you in, and send account emails such

as address confirmation and password resets.

• Password — stored only as a salted PBKDF2-SHA256 hash. We never store

or see your actual password.

• Account state — role, status, approval state, and sign-in timestamps, used

to run permissions and to keep the site secure.

• Consent records — which version of these documents you accepted, and when.

Kept because we must be able to demonstrate that consent was given.

Your pilot profile (optional, you choose what to enter)

Full name, date of birth, nationality, licence type, number and issuing authority, medical type and expiry, home aerodrome, preferred units, date/time format and time zone. These are used only to personalise your own logbook — for example, to show your home base weather or to format dates and times.

Your logbook and related records

Flight entries (dates, times, aircraft, routes, hours, take-offs, landings, remarks), aircraft, ratings, instructors, currency rules, and any documents you upload. These are private to you. They are used solely to provide the logbook to you.

Community forum

If you choose to join the community: your chosen username and display name, your posts and replies, votes, reactions, badges, warnings, and the timestamps of your activity. Your real name is never shown on the forum — your profile's full name is not used there.

Public website comments

If you comment on a blog post, the comment, the name you give, and your account link are stored and shown publicly with the comment.

Technical and security data

• Session cookie (see section 4).
• Rate-limiting counters, keyed by account and by IP address, to stop

credential guessing and spam.

• Audit log — administrative and moderation actions, with the acting

administrator, the action, and the affected record. Kept for accountability.

• Traffic counts — aggregate page views. See section 5.

3. Lawful basis

• Contract — most of the above is processed because it is necessary to

provide the Service you signed up for (running your logbook, keeping you signed in).

• Consent — for the community forum, which is optional and opt-in. You

choose to join, and you can leave at any time. We also rely on consent for the optional non-essential cookies described in section 4.

• Legitimate interests — security, fraud and abuse prevention, rate limiting,

and keeping an audit trail of administrative actions.

• Legal obligation — retaining records of consent, and handling rights

requests.

4. Cookies

We use as few as possible.

• pl_session — strictly necessary. An HttpOnly cookie holding your

signed-in session. Without it you cannot stay signed in. It is not used for tracking or advertising, and it is not shared.

• Your theme preference is stored in your browser's local storage, not in a

cookie, and is not transmitted to us.

Non-essential cookies (analytics or advertising) are only set if you accept them in the cookie notice. Until you accept, none are set. If we run no non-essential cookies at all — which is the case today — the notice is purely informational and there is nothing to opt out of.

You can clear or block cookies in your browser at any time. Blocking the strictly-necessary session cookie will prevent you from signing in.

5. Analytics and advertising

Website traffic is counted on our own server. That means:

• No third-party analytics script is loaded, so no third-party analytics

cookie is set and no data is sent to an analytics provider.

• Visitors are counted using a rotating, non-reversible hash that changes

daily. It is not a persistent identifier and cannot be used to follow you across sites or over time.

If advertising is enabled on the public website, ad slots may be served by a third-party advertising network, which is described in the cookie notice and subject to that network's own privacy policy. Advertising is never shown inside the logbook application.

6. Who we share it with

We do not sell your personal data. We share it only with the service providers needed to run the site, and only as far as necessary:

• Cloud hosting and database infrastructure, which stores the data on our

behalf.

• Email delivery, used to send account emails such as address confirmation

and password resets.

• Advertising network (only if advertising is enabled on the public site).

Some providers may process data outside the UK/EEA. Where that happens, the transfer relies on an appropriate safeguard such as the UK International Data Transfer Addendum or the European Commission's Standard Contractual Clauses.

We may also disclose data where we are legally required to do so.

7. How long we keep it

• Account and logbook data — kept while your account is open. If you ask us

to delete your account, it is erased (see section 8).

• Forum posts — when an account is deleted, posts are anonymised rather

than removed, so that conversations other members took part in are not destroyed. The author is shown as "Deleted User" and is no longer linked to you.

• Consent and audit records — retained for as long as needed to demonstrate

compliance and accountability.

• Security and rate-limit data — short-lived.

8. Your rights

Under the UK GDPR (and the EU GDPR where it applies) you have the right to:

• Be informed — this policy.
• Access your data, and receive a portable copy of it. You can download

your data yourself from the Export section of the app, which produces a complete machine-readable file. If you would prefer us to do it, ask us.

• Rectify inaccurate data — most of it you can edit yourself in your profile

and logbook.

• Erase your data ("the right to be forgotten"). Request deletion from your

account, or by contacting us. We will delete your credentials, your profile, and your private flight records, and anonymise your forum posts as described in section 7.

• Restrict or object to processing.
• Withdraw consent at any time — for example, by leaving the community forum.

Withdrawing consent does not affect processing carried out before you withdrew it.

• Complain to a supervisory authority. In the UK this is the **Information

Commissioner's Office (ICO)** at ico.org.uk. We would rather you came to us first, but you are entitled to go straight to the ICO.

To exercise any of these rights, use the relevant option in your account or contact the site operator. We will respond within one month, as the law requires.

9. Security

Passwords are hashed with PBKDF2-SHA256 and a per-user salt. Sessions are signed tokens, and the session cookie is HttpOnly. Your flight records are readable only by you (and by an administrator only where a specific administrative capability has been granted, with the access itself recorded in the audit log). Access to the administrative area is role-based and audited.

No system is perfectly secure. If we ever become aware of a breach affecting your rights and freedoms, we will notify you and the relevant authority as required by law.

10. Changes to this policy

If we change this policy materially we will publish a new version and ask you to accept it. The version you accepted, and when, is on record.