Privacy Policy

Version: privacy_v2
Effective date: 4 September 2026

Privacy at a glance

EFB Logbook is a flight-simulation logbook. We collect the information needed to create and secure your account, store and display your simulated-flight records, provide requested sharing and subscription features, and support you.

• Usage Analytics is optional, off by default, and can be refused without losing access.
• We do not use personal data for targeted advertising and do not sell personal data.
• Profiles and flights are private unless you choose to make them public.
• The Scratchpad is stored on your device and is designed to expire locally.
• You can delete your account in the app or contact us about your data rights.
• EFB Logbook is for people aged 13 or over and applies high-privacy defaults to every user.

This summary is not a substitute for the full information below.

1. Who is responsible for your personal data?

The data controller is Thomas Ledger trading as AeroLine Digital (referred to as “AeroLine Digital”, “we”, “us” or “our”).

Postal address: AeroLine Digital, 49 Station Road, Polegate, East Sussex, BN26 6EA, United Kingdom
Privacy email: privacy@aeroline.digital

2. Scope

This policy covers the EFB Logbook mobile application, the EFB Logbook website, account and support services, and associated cloud functions. It does not govern services operated independently by Apple, Google, RevenueCat, SimBrief/Navigraph or another service you choose to use; their own privacy information also applies.

3. Information we process

Depending on the features you use, we process:

• Account and authentication information: email address, Firebase user ID, authentication provider, sign-in/security metadata and, where supplied by an authentication provider, basic account details.
• Profile and preference information: display name, public-profile setting, airport-code preference, onboarding state, age-threshold confirmation, document versions accepted or acknowledged, Analytics choice, marketing choice and server-recorded decision times.
• Flight-log information: information you enter or import about simulated flights, such as dates and times, departure and arrival aerodromes, routes and coordinates, aircraft, callsign or flight number, distance, duration, notes, visibility setting and derived totals or achievements.
• SimBrief import information: the SimBrief Pilot ID you provide and flight-plan/OFP information retrieved at your request.
• Public content: a display name and flight information that you deliberately mark as public.
• Subscription information: a pseudonymous app user ID, product and entitlement status, purchase/renewal status, store, transaction references and related subscription metadata. We do not receive your full payment-card details.
• Optional Usage Analytics: if you opt in, Firebase Analytics may receive app-instance and device information, operating-system/app version, approximate location derived from network information, sessions, screens and app interactions. We disable advertising-ID collection and ad-personalisation signals, do not use Analytics for advertising, and do not set your Firebase account UID as an Analytics user ID.
• Technical and security information: IP address and request, authentication, function, error and security logs generated when our cloud services are used.
• Support and rights-request information: your email address, correspondence, evidence reasonably required to verify an account, and information you choose to provide.
• Local-device information: Scratchpad entries and some preferences or cached data stored on your device. Scratchpad content is not designed to sync to our cloud service.

Please do not place real-world sensitive personal data, special-category data, passwords or confidential operational aviation information in free-text fields. EFB Logbook is intended for flight simulation, not real-world operational records.

4. Where information comes from

We receive information:

• directly from you when you register, enter or import a flight, choose settings, contact us or purchase/restore PRO;
• from Google or Apple when you choose their sign-in service;
• from Apple App Store, Google Play and RevenueCat for purchases and entitlements;
• from SimBrief/Navigraph when you request an import using your Pilot ID;
• automatically from your device and our service providers when technically necessary to operate, secure or diagnose the Service; and
• from Firebase Analytics only when the current Analytics choice recorded for your account permits collection.

5. Why we use information and our lawful bases

Where we rely on legitimate interests, we consider the necessity of the processing, its effect on users—particularly younger users—and whether those interests are overridden by individual rights. You may ask about or object to this processing.

6. Information you must provide and choices you can make

To create and use an account, you must provide or generate the account and authentication information needed to sign in, confirm that you meet the minimum age, accept the current Terms, acknowledge the current Privacy Policy, and make an Analytics choice. You can refuse Analytics; the choice itself must still be recorded so that the Service can respect it. If you do not provide the required account or legal-confirmation information, we cannot create or continue the account.

Marketing, Analytics, public-profile visibility, public flight sharing, SimBrief import, PRO purchase and free-text fields are optional. Refusing an optional feature does not prevent use of the Service’s unrelated core features.

7. Analytics and marketing choices

Usage Analytics and marketing are separate optional choices. Neither is required to use EFB Logbook and neither box is pre-selected.

Analytics remains disabled unless you actively enable it. You can change the setting under Profile → Usage analytics. Withdrawal disables future collection and resets the app’s local Analytics data/identifier. Withdrawal does not make earlier consent-based processing unlawful, and information already included in aggregated reporting may no longer be capable of being associated with an individual app instance.

You can withdraw marketing consent through the method in a message or through the app where available. We do not treat acceptance of the Terms or acknowledgement of this policy as consent to Analytics or marketing.

8. Public profiles and sharing

Profiles and flights are private by default. If you enable a public profile or mark a flight public, the displayed name and selected flight information can be viewed by other users. Do not publish information you do not want others to see or copy. Turning public visibility off removes it from our public views, although copies previously made by another person may remain outside our control.

Using your device’s share function sends the content to the app or person you choose. That recipient then controls its own use of the shared information.

9. Service providers and other recipients

We disclose only the information needed for the relevant service to:

• Google Firebase and Google Cloud: authentication, Firestore database, cloud functions, hosting, security logs and optional Firebase Analytics;
• Google Maps Platform: maps and route display;
• Apple and Google: optional sign-in, app distribution, purchases, subscription administration and store reviews;
• RevenueCat: subscription and entitlement administration using a pseudonymous app user ID;
• SimBrief/Navigraph: retrieving the latest OFP when you ask us to do so;
• our email service provider: receiving and responding to support and privacy communications; and
• professional advisers, regulators, courts, law enforcement or another recipient where disclosure is legally required or reasonably necessary to establish, exercise or defend legal rights.

Apple, Google and SimBrief/Navigraph may act as independent controllers for parts of their services. We do not sell personal data or disclose it to third parties for their own advertising.

10. International transfers

Some providers operate internationally, so personal data may be processed outside the United Kingdom. Where UK data-protection law requires a transfer safeguard, we rely on an applicable UK adequacy regulation or contractual safeguards such as the UK International Data Transfer Agreement or UK Addendum to approved standard contractual clauses, together with supplementary measures where appropriate. You may contact us for more information about the safeguard relevant to a particular provider.

11. Retention

We keep personal data only for as long as necessary for the stated purpose:

• account, profile, acceptance and private flight data are normally retained while your account remains active and are deleted when the account-deletion workflow completes;
• if you delete an account while a paid app-store subscription or entitlement remains active, the minimum RevenueCat customer identifier and subscription-status information needed to administer that entitlement and complete processor deletion is retained until RevenueCat confirms that no active entitlement remains. The RevenueCat customer is then queued for deletion, normally within 24 hours of that confirmation;
• public content remains public until you make it private, delete it or delete your account;
• optional Firebase Analytics user-level and event data is configured for a two-month retention period, with retention not reset by new user activity. This setting does not control Google’s standard aggregated reporting;
• routine cloud logs are normally retained for up to 30 days, but relevant records may be retained longer while investigating a security incident, abuse or legal claim;
• support and privacy correspondence is normally retained for up to 24 months after the matter closes, or longer where reasonably required for a continuing dispute or legal obligation;
• records required for tax, accounting, consumer or legal-claim purposes may be retained for up to six years, where applicable; and
• after account deletion, a one-way availability reservation for a claimed public display name is kept to prevent reuse and impersonation. The account UID and display value are removed from that reservation during deletion. Because the reservation cannot be used to restore the account or its content, it is not used for any other purpose.

Apple, Google and other independent controllers may retain store transaction or account records under their own legal obligations and policies.

We review these periods and delete or anonymise information when it is no longer needed.

12. Account deletion

You can request deletion in Profile → Delete account. The workflow deletes the Firebase account and associated Firestore profile, flights and derived data. If no paid entitlement remains active, it also requests permanent deletion of the corresponding RevenueCat customer. RevenueCat processes deletion asynchronously.

If a paid entitlement is still active, we retain only the pseudonymous RevenueCat customer identifier and subscription-status information required to administer that entitlement and complete deletion. We recheck its status and request RevenueCat deletion after RevenueCat confirms that no active entitlement remains, normally within 24 hours. Deleting EFB Logbook does not cancel an Apple App Store or Google Play subscription; you must manage or cancel it through the relevant store.

The limited display-name reservation described above remains. Deleting EFB Logbook does not delete independent Apple, Google, SimBrief or app-store accounts or records.

If you cannot access the app, email privacy@aeroline.digital. We may request proportionate information to verify that you control the account.

13. Children

EFB Logbook is not intended for children under 13. Users must confirm that they are at least 13. If you believe a child under 13 has created an account, contact us so we can investigate and delete it where appropriate.

Because people aged 13–17 may use the Service, their best interests are a primary consideration in our design and data practices. We apply high-privacy defaults to everybody: Analytics is off, public profiles are off, flights are private, advertising identifiers and ad-personalisation signals are disabled, and optional choices do not restrict access. We do not knowingly profile children for advertising or use nudge techniques to make privacy settings less protective. We aim to explain choices in clear language suitable for younger users.

14. Security

We use access controls, authenticated services, server-owned sensitive fields, encryption in transit, provider security controls and testing intended to prevent unauthorised access or alteration. No internet service can guarantee absolute security. Please secure your sign-in method and contact us if you suspect unauthorised account use.

15. Your rights

Subject to the law and any applicable exceptions, you may have the right to:

• be informed about processing;
• access your personal data;
• correct inaccurate or incomplete data;
• request erasure;
• restrict processing;
• receive certain data in a portable format;
• object to processing based on legitimate interests or direct marketing;
• withdraw consent at any time; and
• complain to a supervisory authority.

To exercise a right, email privacy@aeroline.digital. We normally respond within one month and may request proportionate identity verification. You will not usually have to pay a fee.

Right to object: where we rely on legitimate interests, you have the right to object to that processing based on your particular situation. You have an absolute right to object to direct marketing. Email privacy@aeroline.digital or use the unsubscribe method provided with marketing.

You may complain to the UK Information Commissioner’s Office at https://ico.org.uk/make-a-complaint/. We would appreciate the opportunity to address your concern first, but you do not have to contact us before approaching the ICO.

16. Automated decisions

EFB Logbook uses automated checks for matters such as entitlement status, limits, achievements and prohibited public display names. We do not use personal data to make solely automated decisions that produce legal or similarly significant effects.

17. Changes to this policy

We may update this policy when the Service, providers or law changes. We will publish the effective date and version. Where a change is material, we will provide prominent notice and, where appropriate, require acknowledgement or obtain fresh consent for optional processing.

18. Contact

Thomas Ledger trading as AeroLine Digital
AeroLine Digital, 49 Station Road, Polegate, East Sussex, BN26 6EA, United Kingdom
privacy@aeroline.digital