This policy covers the app sFTL – Flight Time Limitations for Android (Google Play, package org.looping.sftl), owned and published by the company FEEL.AERO and developed for it by Philippe LE GALL, the developer named on Google Play. sFTL is the Android version of the flight time limitations module of sQRH.

What we collect

Nothing. sFTL has no account, no sign-in, no analytics, no advertising and no tracking, and we have no servers. The flight time limitation rules and the airport database are built into the app, and all calculations run on the device. sFTL does not request internet access.

We do not collect, receive, sell or share any personal data, and no third-party code in the app does either.

What stays on your device

To pick up where you left off, the app saves the following locally, on your device only:

  • your current duty: report time, sectors (airport codes, OUT and IN times), crew type and number of pilots, acclimatisation state and hours since last landing, delayed reporting and split duty;
  • crew rest: the cruise start time, the sector that carries the rest and the planned rest alerts;
  • your settings: briefing time, rest buffers, rest alert time and UTC or local display;
  • the result of the last update check (below).

This information never leaves the device through sFTL unless you send it with Nearby Share (below), and deleting the app deletes it. It is excluded from cloud backup and device transfer.

Nearby Share

Nearby Share sends your current duty to other devices nearby that have sFTL (Android) or sQRH (iPhone and iPad) open, directly over Bluetooth. Nothing goes through the internet or through us, and there is no pairing or account.

  • While sFTL is open on screen, it makes itself visible to nearby devices running sFTL or sQRH and publishes a short record: a random identifier that changes every time the app starts, the device name, the platform and the app version. This lets nearby devices list it as a recipient.
  • Only when you tap the share button, sFTL sends your duty (report time, sectors, crew, acclimatisation, delayed reporting, split duty and the crew rest start time) and your device name to the nearby devices.
  • A receiving device always shows a summary first; nothing changes on it unless its user accepts. A declined share is discarded.

Bluetooth stops when sFTL leaves the screen. Received shares are not stored beyond the duty the user accepts. To keep your device name from being shown, rename the device in its settings, or deny sFTL the "Nearby devices" permission (Nearby Share then stays off; the rest of the app works normally).

Update check

When you open the settings, sFTL asks the Google Play app on your device, at most once an hour and only when the device is online, whether a newer version of sFTL is available, to show an update banner. This request is handled by Google Play; sFTL sends nothing to us.

Permissions

  • Notifications — for the crew rest alerts and the ongoing crew rest notification on the lock screen.
  • Alarms & reminders — so the crew rest alerts fire on time, even with the app closed.
  • Run at startup — to set the crew rest alerts again after the device restarts.
  • Nearby devices (Bluetooth) — for Nearby Share only.
  • Location (Android 11 and earlier only) — Android requires it to scan for Bluetooth devices. sFTL never reads your location.
  • Network state — to run the update check only when the device is online.

sFTL does not access your location, contacts, calendar, photos, camera, microphone or files.

Google Play

sFTL is distributed by Google, which processes data related to your download and, if you have agreed to it in your device settings, anonymous crash and diagnostic reports. That processing is governed by Google's own privacy policy. When such anonymous reports are made available to us, we use them only to fix bugs.

Children

sFTL is a professional aviation tool and is not directed at children. It collects no data from anyone.

Changes

If this policy changes, the new version will be published on this page with a new date.

Contact

FEEL.AERO, developer Philippe LE GALL. Questions about this policy: contact@feel.aero or the contact page.