RC Flight Logbook

RC Flight Logbook

Privacy Policy

Effective August 26, 2026

RC Flight Logbook is a local-first application from Croft Labs LLC. It is designed to work without an account and keeps ordinary logbook data on the user’s device. This policy also describes the limited data handling of the public website at rcflightlogbook.com and optional Account services. The later Pro data portal and cloud record synchronization are not currently live.

Public website

The public marketing website does not currently use advertising cookies, behavioral tracking, visitor analytics or account forms. The separate Account application uses the shared MVS authentication backend only when the user chooses signup or sign-in. If you email us, we receive the information you choose to include. Hosting infrastructure may record ordinary technical data such as IP address, browser, requested page, timestamp, and error details for security and reliable operation.

Information stored by the mobile app

The app may store information entered or selected by the user, including aircraft and equipment identifiers, battery details, pilot details, optional birthdays and aviation registration information, airfields, coordinates, images, maintenance and battery activities, flight plans, flight records, notes, weather snapshots, settings, Remote ID observations, and Link Radio telemetry.

Ordinary records remain in application-owned storage unless the user explicitly exports or backs them up, uses a feature requiring a named network provider, or the operating system performs platform-managed processing. Optional Account signup stores an email address, provider account UUID, verification/session state and the owner-managed founding-member checkbox. Signed-in clients can read only their own profile and cannot edit that checkbox. It does not upload ordinary logbook records. The app does not include cloud record synchronization, advertising, analytics, automatic or third-party crash reporting, or push-token registration.

The app keeps at most 200 sanitized JavaScript and screen-rendering errors in app-private storage. Nothing is sent automatically. The user may review recent entries, deliberately share a JSON report through the system share sheet, or clear the history in Settings. Reports are designed to exclude database records, images, coordinates, account identifiers, and credentials.

Location and recorded GPS data

Optional live location supports flight recording, nearby-airfield selection, weather, maps, and navigation. A separate setting controls whether recorded flight and streamed coordinates are retained. Purging recorded GPS data removes retained flight, telemetry, Remote ID, and active-draft coordinates plus derived distance summaries; it does not remove manually defined airfields or reusable flight-plan locations.

Notifications and companion-app synchronization

Battery reminders are local notifications and do not register a push token. Update discovery remains in-app. Compatible installed RC and Battery Logbook apps may exchange battery records only after user opt-in and private Android transport/version checks. Each app keeps its own database. Synchronized battery images are verified by hash and length before copying into the receiving app’s private storage. Permanent deletions are not currently transferred.

Network and third-party services

Device permissions

The app requests optional permissions in context for foreground location, user-chosen camera access, and user-started Bluetooth or nearby Wi-Fi radio workflows. Core logging remains available when optional permissions are denied. The app does not request background location, microphone recording, or broad settings-control permission.

Retention, deletion, and backup

Ordinary records remain local until the user edits, decommissions, or deletes them. Integrity protections may prevent deletion of resources referenced by history. Manual backup occurs only when requested and sent to a user-selected destination. Per-second telemetry and active-flight recovery drafts are excluded from the whole-app backup, while parent flight records and high-value summaries remain included.

Account profiles remain in the authentication service until account deletion. Founding status is removed when the dashboard owner unchecks the profile and cannot be self-awarded by the app. The public Account deletion page explains how to submit a request and which hosted data is removed. Hosted Account deletion does not remotely erase ordinary local records or exported backups.

Uninstalling the app, clearing its storage, or losing the device can permanently erase records that have not been backed up. Users should make regular backups and protect exported files according to their sensitivity.

Security and children’s privacy

Network-provider requests use HTTPS. No electronic transmission or storage method can be guaranteed completely secure. RC Flight Logbook is a specialist hobby utility and is not directed to children.

Changes and contact

Material changes to data handling will be reflected here, in the application’s Data & Privacy screen, and in applicable store declarations before release. Privacy and support inquiries may be sent to accounts@rcflightlogbook.com.