Introduction

This Privacy Policy describes how Block-Time ("the Application"), developed and maintained by Block-Time ("we", "us", "our"), handles information in connection with your use of the Application. We are committed to protecting your privacy and being transparent about data practices.

By using Block-Time, you acknowledge and agree to the practices described in this policy.

Summary

Your logbook stays on your devices and in your own iCloud account. We cannot see it. The only data we hold is for the optional Roster Sync subscription, and only once you connect it. You can delete that data at any time from inside the Application.

The Application contains no analytics frameworks, advertising SDKs, crash reporting services or tracking of any kind, and we never sell or share your data for advertising.

Your Logbook, iCloud and CloudKit

Block-Time uses Apple CloudKit to synchronise your logbook records and application settings across your personal devices. This synchronisation occurs exclusively within your own iCloud account. We do not have access to, process, or store any data held in your iCloud account.

All CloudKit data is subject to Apple's data handling practices. For details, see the Apple Privacy Policy.

Roster Sync (optional subscription)

Roster Sync turns your emailed roster into a calendar feed and offers roster changes to your logbook. It runs on our server, so when you connect it we collect and store:

  • Roster contents: your name, staff number, base, category and bid periods, and the duties, flights, times and pattern codes in each roster you send to your Block-Time roster address. We also keep the text of your three most recent rosters for each bid period. The roster email itself is not kept.
  • Account details: your Block-Time roster address, your calendar feed link, your calendar display settings, and a cryptographic fingerprint (hash) of a random key that identifies your device. The key itself never leaves your devices and your iCloud account.
  • Forwarding addresses: any email addresses you ask us to forward your roster to, and when each forward was last sent.
  • Email identifiers: the message ID of each roster email, so the same email is not processed twice.
  • Subscription status: your App Store transaction ID, the product you subscribe to, and its status and expiry, which we confirm directly with Apple.

We use this data only to provide Roster Sync: to build your calendar feed, to show roster changes in the Application, to forward your roster where you have asked us to, and to investigate and correct errors in how rosters are read.

Your calendar feed link works like a password. Anyone who has it can see your roster, so share it only with calendar services you trust. You can replace it at any time in the Application, which stops the old link working.

Forwarding sends a copy of your roster to the addresses you list. Once delivered, those copies are handled by the services that receive them under their own privacy policies.

webCIS

Block-Time can open Qantas webCIS inside the Application to fetch crew information or ask webCIS to email your roster. You sign in on the Qantas and Microsoft sign-in pages directly; Block-Time never sees or stores your password. Information fetched from webCIS is stored only on your devices and in your iCloud account. When you use Fetch webCIS Roster Now, webCIS emails your roster to your Block-Time roster address, where it is handled as described under Roster Sync.

Flight Data Providers

When you look up a flight, Block-Time sends the flight number, date and airports to a flight data provider to retrieve schedule and timing details. No name, account or other personal identifier is sent with these requests.

Service Providers

We use the following providers to run Roster Sync. They process data on our behalf and only as needed to provide the service:

  • Cloudflare hosts our server, database and roster email handling, and sends forwarded emails. Cloudflare keeps request logs, including IP address and approximate location, for 7 days. Calendar feed links are hidden in these logs.
  • Apple processes subscription purchases. We ask Apple's App Store Server API whether your subscription is active, and Apple tells us when it renews, lapses or is refunded.

Data Sharing and Disclosure

We do not sell, rent or share your data with anyone for advertising or marketing. Your data is disclosed only to the service providers listed above, to the forwarding addresses you choose, or where required by law.

Data Retention and Deletion

Your logbook and settings remain in your iCloud account under your control, and can be removed by deleting the Application or through your device's iCloud settings.

Roster Sync data is kept for as long as your Roster Sync account exists, including after a subscription ends, so that resubscribing picks up where you left off. Each saved roster text is deleted automatically 60 days after its bid period ends. You can delete it at any time in the Application: open Settings, Roster & Calendar Sync, and tap Delete Roster Sync Account. This permanently deletes everything listed under Roster Sync from our server, for all your devices; your calendar link and roster address stop working immediately. Flights already in your logbook are not affected. Cloudflare request logs expire within 7 days.

Deleting your account does not cancel your subscription. Cancel it in your Apple ID subscription settings.

You can also ask us to delete your data, or to tell you what we hold, by emailing support@block-time.app.

Children's Privacy

Block-Time is intended for pilots and is not directed at children under the age of 13. We do not knowingly collect data from children.

Your Rights

You can see your Roster Sync data in the Application and your calendar feed, and delete it as described above. For any request about your data, including access, correction or deletion, contact us at support@block-time.app. If you are in Australia, you may also contact the Office of the Australian Information Commissioner.

Changes to This Policy

Block-Time reserves the right to update this Privacy Policy from time to time. Any changes will be reflected at this URL with a revised effective date. Continued use of the Application following any such update constitutes your acceptance of the revised policy.

Contact

If you have any questions or concerns regarding this Privacy Policy, please contact: