Privacy Policy

1. Who we are

This Privacy Policy describes how Liana Solutions Pty Ltd (“we”, “us”, “our”) handles information in connection with the E6B Pilot Computer iOS application (the “App”).

We are based in Australia and handle personal information in accordance with applicable privacy laws, including the Privacy Act 1988 (Cth) and the Australian Privacy Principles, and, where relevant, data protection laws such as the EU/UK General Data Protection Regulation (GDPR).

This Policy is for information only and is not legal advice.

2. No accounts

The App does not require or provide user accounts or sign-in. We never ask for your name, email address or other contact details in order to use it. There is nothing to sign up for and nothing to sign in to. The analytics profile described in §5.1 is a provider record keyed to the app-generated Support ID, not an account you create.

3. Your data stays yours

Everything you create in the App — aircraft profiles, saved loadings, calculator inputs, unit preferences — is stored on your device.

• iCloud sync. Aircraft profiles and saved loadings sync through your own private iCloud database, using Apple's CloudKit. That data is held in your Apple account, not ours. We have no access to it, cannot read it, and cannot delete it for you. Apple's own privacy terms govern it.
• Saved loadings are immutable. A saved loading freezes the aircraft figures and results as they were at the moment you saved it, so a later profile edit cannot retroactively change a record you relied on.
• PDF reports are generated on your device and written to a temporary file only for as long as it takes you to share or save them. The App deletes its own temporary report and export files, and sweeps any it finds left behind.
• Export. Settings → Export Aircraft & Loadings produces a single readable JSON file containing every saved aircraft profile and every saved loading the App holds for you. That is the scope of the file: unsaved calculator entries and your unit preferences are not part of it. It is not behind the Pro purchase.
• METAR prefill decodes text you paste, on your device. The App does not fetch weather and makes no network request to do it.

4. The Support ID

Analytics and purchases cannot work without something that distinguishes one installation from another. The App generates one random value for this, which we call your Support ID. You can see and copy it in Settings → About.

• It is a randomly generated identifier created on your device. It is not derived from your device's hardware identifiers, your Apple Account, or your phone number.
• It identifies an installation. The App never collects your name, email address or any other detail that would tell us whose installation it is.
• The same value is used with both our analytics provider and our purchase provider, so a purchase can be matched to the usage that led to it. Our purchase provider also forwards purchase and entitlement events to our analytics provider under the same Support ID (§5.2). We do not share it with anyone else.
• It is stored in your device's keychain. Deleting the App does not reliably erase it — reinstalling on the same device may reuse the same ID, and because it is included in encrypted device backups it may also follow you to a replacement device.

One honest caveat. The App itself never connects the Support ID to your identity. But if you email us quoting it — for example to ask us to delete your records — then your email address and the Support ID are connected in our support inbox while we handle your request, and for a reasonable period afterwards (§10).

5. What we receive

5.1 Usage analytics

We use PostHog, with our project hosted in the European Union, to understand which features are used so we can improve the App. We hold no name and no account to attach these analytics to: the App never sends your name, email address, support messages, or any aviation data you enter.

Analytics reach that project by two different routes, and it is worth separating them.

Events the App sends directly are a defined list maintained in its source code: a calculator was opened, a calculator computed a result, the purchase screen was shown, a purchase completed, onboarding progress, the rating prompt was shown, a METAR prefill was used, a loading was saved, and a PDF was exported.

Events forwarded by our purchase provider. Separately, RevenueCat forwards purchase and entitlement events — such as a purchase, a renewal-state change or a restore — to the same analytics project, under the same Support ID. Those events are generated by that provider's own integration rather than by the App, and their exact shape is determined by that provider, so the list above describes what the App sends and not everything the project may contain.

Events never carry your content. No aircraft or profile names, weights, arms, volumes, results, METAR text, PDF names or contents, and no free-form text you type. Where an event describes a choice, it carries a coarse category — for example “imperial” or “metric” rather than any actual figure. This is enforced by tests that fail the build if aviation content reaches an analytics call.

The properties the App sends with each of its own events are: your Support ID, the App version, your device's language/region setting, your iOS version, and the small set of category values described above. In addition, the analytics service automatically records technical information of its own with each event, including your IP address, a timestamp, the device type and operating-system family, and the version of its own software.

Approximate location. Your IP address is processed by our analytics provider and may be used to derive an approximate location, such as your country, region or city, which is stored alongside your events. The App itself never requests or accesses your device's location, and E6B Pilot Computer asks for no location permission at all.

What we have switched off, and the profile we do create. The App does not use session replay, automatically capture screens or app lifecycle events, load surveys or feature flags, or collect crash reports. Before sending product-usage events, the App identifies the Support ID with PostHog. PostHog creates an analytics person profile for that ID so usage events and purchase events forwarded by RevenueCat can be associated with the same profile. This is not an account or a public profile, and the App does not send your name, email address or aviation data to create it.

5.2 Purchases

The Pro unlock is a one-time purchase handled by Apple. We never see your payment details — Apple processes the payment and we receive no card, billing or Apple Account information.

We use RevenueCat to manage entitlements — that is, to know whether this installation has bought Pro and to restore it when you ask. RevenueCat holds a customer record against your Support ID, containing your purchase and restore history for this App, the country and platform Apple reports, and technical metadata about the transaction. It is what makes Restore Purchase work.

RevenueCat also receives Apple's identifier for vendor (IDFV) as part of its purchase-processing requests. This vendor-scoped device identifier is separate from the App-generated Support ID and from Apple's advertising identifier (IDFA). It is associated with requests made under the Support ID and is collected for purchase processing, not product-usage analytics or tracking across other companies' apps or websites.

RevenueCat also forwards purchase and entitlement events to our analytics project under the same Support ID, so that a purchase can be seen alongside the usage that led to it. This is a server-side integration between our two providers; it is not something the App sends.

5.3 Apple Ads attribution

The App requests an Apple Ads attribution token from Apple's AdServices framework and sends it to RevenueCat under the same Support ID. RevenueCat uses that token to request any attribution information Apple makes available about the App's installation, such as the campaign, ad group or keyword. We use this information to understand how people discover the App and how those installations relate to purchases. Where available, RevenueCat may include attribution information in purchase events forwarded to PostHog under the same Support ID. The App does not display ads, access the advertising identifier (IDFA), or request App Tracking Transparency permission. This integration is not used to track you across other companies' apps or websites.

5.4 If you contact us

If you email us, we receive whatever you choose to send — typically your email address, your message, and anything you attach such as a screenshot or a Support ID.

6. What we never collect

• Your name, email address or contact details, unless you email us.
• Your device's location. The App requests no location permission.
• Your contacts, photos, calendars, messages, or health data.
• Payment card information — all payments are processed by Apple.
• Your flight logs, flight plans, or any aviation figures you enter.
• The advertising identifier (IDFA), or data used to track you across other companies' apps or websites. Apple Ads acquisition attribution is described separately in §5.3.

7. Why we are allowed to do this

Where laws such as the GDPR apply, we rely on the following legal bases:

• Performance of a contract — to provide the App and its features to you, including delivering and restoring the Pro unlock you paid for.
• Legitimate interests — to understand how the App is used and how people discover it, to keep it working and secure, and to decide what to improve, provided those interests are not overridden by your rights. This is the basis for the usage analytics described in §5.1, which is why they are kept to product-usage events carrying none of the content you enter, and for the Apple Ads acquisition attribution described in §5.3.
• Legal obligations — where processing is necessary to comply with applicable law.

You can object to the analytics processing at any time by emailing us at the address in §15. We will assess and act on your objection as applicable law requires, and we will ask our analytics provider to delete the events held against your Support ID and our purchase provider to delete the Apple Ads attribution held against it. Being straight with you about the limits: the App has no in-app analytics switch, so we cannot remotely stop the copy on your device from sending events. Deleting the App stops them at source.

8. Who we share it with

We do not sell or rent your personal information, and we do not share it for advertising.

We use a small number of service providers to operate the App:

• PostHog — product analytics (§5.1).
• RevenueCat — purchase and entitlement management (§5.2), and Apple Ads attribution (§5.3).
• Apple — the App Store, payment processing, iCloud/CloudKit storage of your own data in your own Apple account, and Apple Ads attribution through its AdServices framework (§5.3).

We engage each of these providers under their standard terms for business customers, which set out how they may handle data in connection with the service they provide to us and require them to keep it secure. Those terms, and each provider's own privacy policy linked above, govern the detail — we describe our arrangements here rather than characterising every provider's role for them.

We may also disclose information if we believe in good faith that it is reasonably necessary to comply with law or a lawful request, to enforce our Terms of Use, to detect or address fraud or security issues, or to protect the rights, property or safety of our users, the public or us. If we are ever involved in a merger, acquisition or sale of assets, information may be transferred as part of that transaction subject to appropriate confidentiality protections.

9. Where your information goes

We are in Australia. Our analytics provider hosts the E6B project in the European Union. Our purchase-management provider operates globally, including in the United States. Information described in this Policy may therefore be transferred to and stored in countries other than your own, whose data-protection laws may differ from your own country's.

Where the GDPR applies, we rely on the transfer mechanisms our providers make available for their services, such as standard contractual clauses, as described in their own privacy and data-processing documentation.

10. How long we keep it

• On your device and in your iCloud. For as long as you keep it. You control this entirely: delete individual aircraft and loadings in the App, or delete the App and remove its iCloud data through iOS Settings.
• Analytics events. Kept by our analytics provider under its own data retention policy, for the period that applies to our project on its platform. We delete the events associated with your Support ID sooner if you ask.
• Purchase records. Kept by our purchase provider for as long as the entitlement needs to be restorable, so that Restore Purchase keeps working. We delete a customer record on request, with the consequence noted in §11. Apple's identifier for vendor and any Apple Ads attribution sit in that same customer record and are deleted with it.
• Support correspondence. Kept while we handle your request and for a reasonable period afterwards, then deleted — except where we need to keep it longer to meet a legal obligation.

11. Your rights and choices

11.1 What you can do yourself

• See the identifier we generate: Settings → About shows your Support ID. Our purchase provider also holds Apple's identifier for vendor (IDFV) and any Apple Ads attribution against it (§5.2, §5.3) — those are not visible in the App, and you can ask us for them under §11.2.
• Export your data: Settings → Export Aircraft & Loadings writes every aircraft profile and saved loading to a single JSON file you can keep or move elsewhere.
• Delete your data: delete aircraft and saved loadings in the App at any time, with or without Pro. Delete the App to remove its local data, and remove its iCloud data through iOS Settings.

11.2 What to ask us for

Depending on where you live, you may have the right to request access to, correction of, or deletion of personal information we hold; to object to or restrict certain processing; and to data portability. To exercise any of these, email us at the address in §15 quoting your Support ID from Settings → About — without it we have no way to find your records, because we do not know who you are. We assess each request and handle it as applicable law requires.

When you ask us to delete your records, this is what we do:

• We ask our analytics provider to delete the events held against your Support ID, including any purchase or attribution events forwarded under it, using the deletion tools it provides.
• We delete the purchase record held against your Support ID. This includes Apple's identifier for vendor and any Apple Ads attribution held in that record. Be aware this can affect Restore Purchase — after deletion, restoring your Pro unlock relies on Apple's own record of your purchase rather than ours. Tell us if you would rather we did not delete the purchase record.
• We delete our correspondence with you on the schedule in §10.
• Where a provider must keep certain records to meet its own legal or accounting obligations — a record of a transaction, for instance — that data stays until those obligations expire. We tell you if that applies to your request rather than implying an erasure we cannot deliver.
• We cannot delete your iCloud data, because it is in your Apple account and not ours. You remove it yourself through iOS Settings; we will tell you how.

We can only act on possession of a Support ID — we have no way to verify that the person quoting it is you, because we hold nothing that would let us. We say this plainly rather than implying an identity check we cannot perform.

If you are located in a country with a data-protection authority, you may have the right to lodge a complaint with it. We would appreciate the chance to address your concerns first.

12. Children

The App is a flight-training tool intended for pilots and student pilots, and is not directed to children under 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will delete it.

13. Security

We use reasonable technical and organisational measures to protect information against unauthorised access, loss, misuse or alteration: encrypted network connections, access controls on the systems that process data, and a deliberately small amount of collected data in the first place — the most reliable protection is not holding something. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

14. Changes to this Policy

We may update this Policy from time to time. When we do, we will update the effective date at the top of this page. If a change materially affects how we handle your information, we will provide additional notice in the App or by other appropriate means.

15. Contact us

Questions about this Policy, or a privacy request or complaint:

• Email: contact@runwaybrief.app — please put “E6B” in the subject line.
• Support: e6b.runwaybrief.app/support

Liana Solutions Pty Ltd, Australia.