Privacy Policy | FlyTimeLog

1. Data we collect

Account and authentication data

We process your email address, display name, password hash, login sessions, and the stable account identifier supplied by Apple or Google when you choose those sign-in methods. We do not store your Apple or Google password.

Pilot-provided records

FlyTimeLog stores information you create or import, including flight log entries, schedules and duties, routes, aircraft, crew and role details, OOOI times and images, imported files and rows, qualifications, credentials, currency settings, notes, reports, exports, and app preferences. If you use the People directory, we also store the colleague names, default crew roles, licence or certificate identifiers, employee identifiers, and notes that you choose to enter.

Paper logbook scans and recognition candidates

When you add paper logbook scans, FlyTimeLog processes the page images you submit by camera, JPEG, PNG, or PDF. The original PDF is discarded after bounded page images are prepared. Saved pages and recognition candidates may contain names, licence or certificate numbers, signatures, crew details, aircraft registrations, routes, times, and remarks visible on the source page.

Service and security data

We process request timestamps, IP addresses, security events, and limited diagnostic logs needed to operate and protect the service. FlyTimeLog does not use an advertising identifier, track precise device location, or read your address book. The People directory is entered manually and does not request access to device contacts.

Airline login IDs, passwords, MFA codes, and raw authenticated cookies submitted for roster import are used only to perform that connection and are not retained by the FlyTimeLog server as roster data. A supported native flow may keep the login ID and password in this device's protected storage for the next import and clears it when the signed-in owner is reset; MFA codes and raw cookies are not retained. An employee identifier is stored in the People directory only when you choose to enter it there; it is not copied from a roster import automatically.

2. How we use data

Authenticate your account and keep records scoped to you.
Store, sync, review, calculate, and export your pilot records.
Maintain the People directory and select crew for a flight.
Import planned rosters and create reviewable flight drafts.
Process OOOI images and extracted times that you submit.
When you separately choose AI recognition, read text and table structure from saved paper logbook pages and create unvalidated candidates for your review.
Protect the service, investigate failures, and provide support.
Meet legal obligations and enforce service terms.

Planned roster events are not automatically confirmed as final logbook entries. Non-flight duties may appear in the calendar but are not committed as flight records.

Selecting someone from the People directory copies their current name, selected crew role, and optional licence or certificate identifier into that flight record. Employee identifiers and People notes are not copied. Later edits or archiving in the directory do not rewrite historical logbook entries or existing report exports.

3. Sharing and service providers

We do not sell personal data. Data may be processed by infrastructure, email-delivery, authentication, content-delivery, security, and optional document-recognition providers only as needed to operate FlyTimeLog. Apple and Google process sign-in information under their own privacy terms when you select their services. We may disclose information when required by law or to protect users and the service.

Paper-logbook AI recognition is optional. After you confirm the feature-specific notice, FlyTimeLog sends the saved source page images to Microsoft Azure Document Intelligence using a resource configured in the Korea Central region of South Korea. FlyTimeLog uses the service to return detected text and table structure. The result is an unvalidated recognition candidate and is not automatically added to Import Hub or your logbook. Microsoft publishes additional Azure Document Intelligence data and privacy information.

4. Retention and deletion

Account and pilot records are retained while your account is active or as needed to provide requested exports and audit history. Pending email-verification material expires automatically. The FlyTimeLog server does not retain roster login secrets, MFA codes, or raw authenticated cookies. When a supported native flow offers protected on-device reuse, the saved login ID and password follow the user's choice and are cleared when that signed-in owner's workspace is reset; MFA codes and raw cookies are not saved for reuse.

Archiving a People entry hides it from the active crew picker but retains the row and its audit history so it can be restored. Account deletion covers both active and archived People entries. You may also make a verified request for deletion of selected directory data.

Cancelling a paper scan does not delete its saved pages or recognition candidates. After cancellation, the separate Delete pages control removes the source pixels and saved candidate text. Limited checksum, physical-page order, provider, processing, deletion, and audit metadata may remain to preserve integrity and prevent abuse. Deleting your account removes the account-scoped scan and recognition records and the private source files.

FlyTimeLog requests deletion of each Azure analyze result after a terminal response. If that request cannot be completed, Microsoft may retain the temporary analyze input and result for up to 24 hours before automatic deletion.

You may delete individual records in the app where deletion controls are available. To request deletion of your account and associated data, follow the steps on the account deletion page. We normally complete a verified request within 30 days. Limited security records or backup copies may remain temporarily when required by law, fraud-prevention needs, or backup rotation.

5. Security and international processing

FlyTimeLog uses HTTPS in transit, hashed passwords and verification codes, HttpOnly session cookies, owner-scoped API access, and access controls intended to protect pilot records. No service can guarantee absolute security. Infrastructure and sign-in providers may process data in countries where they operate, subject to their safeguards and applicable law. Optional paper-logbook recognition uses the Microsoft Azure Korea Central resource described above.

6. Your choices

You may review and update profile and flight information in FlyTimeLog, delete supported records, sign out to end the current session, and request account deletion. You may also contact us to ask about access, correction, or deletion of your data.

You can choose not to send saved paper-logbook pages to Microsoft. The AI recognition action is separate from page upload, and declining it does not create a logbook entry or send the pages to that recognition provider.

7. Children

FlyTimeLog is a professional pilot logbook and is not directed to children under 13. We do not knowingly collect personal data from children under 13.

8. Changes and contact

We may update this policy as FlyTimeLog changes. The effective date above identifies the current version. Questions and privacy requests can be sent to [email protected].

한국어 안내

FlyTimeLog은 계정 인증과 비행 기록 관리에 필요한 정보만 처리하며, 개인정보를 판매하지 않습니다. 동료 관리는 사용자가 직접 입력한 이름, 역할, 선택적인 식별자와 메모만 저장하며 기기 연락처를 읽지 않습니다. 동료를 로그북에 선택해도 사번과 메모는 비행 기록에 복사되지 않고, 이후 동료 정보 변경이 과거 로그나 내보내기 파일을 바꾸지 않습니다. 종이 로그북 AI 인식은 선택 기능이며, 사용자가 전송 안내를 확인한 경우에만 저장된 로그북 페이지를 대한민국 Korea Central 리전으로 구성된 Microsoft Azure Document Intelligence에 보내 글자와 표 구조 후보를 만듭니다. 페이지에는 이름, 자격·면허 번호, 서명, 승무원, 항공기 등록기호, 노선, 시각, 비고가 보일 수 있습니다. 결과는 자동으로 Import Hub나 로그북에 기록되지 않습니다. FlyTimeLog은 처리 완료 후 Azure 분석 결과의 삭제를 요청하며, 삭제 요청을 완료하지 못하면 임시 입력과 결과가 최대 24시간 보관될 수 있습니다. 스캔 취소만으로는 원본과 후보가 삭제되지 않으며, 취소 후 별도의 페이지 삭제를 사용하면 원본 픽셀과 후보 텍스트를 삭제할 수 있습니다. 계정 및 관련 데이터 삭제는 계정 삭제 안내에 따라 요청할 수 있습니다. 문의: [email protected]