Privacy Policy

DRAFT. Effective date: [TODO: DATE]. Must be checked against the app's final behavior before publishing.

Who we are

Logbook Lens is operated by Nicholas Chilcott, an individual developer. Contact: [TODO support email: [email protected] is a placeholder, not set up].

What we process

• Logbook photos. When you scan, the photo of the spread is sent from the app through our server to Google for reading. Logbook pages can contain your name, certificate numbers, aircraft, flights, and instructor names, signatures and certificate numbers.
• Purchase and page records. To keep your page balance, our server database holds only a page ledger: an anonymous device key, your free and paid page counts, an Apple App Attest key and counter, an anonymous page-account ID, the anonymous Sign in with Apple user identifier (only if you use Sign in with Apple to restore pages), and for each purchase the Apple transaction ID, product and number of pages. No logbook content is stored in this database.
• Server logs. Our server logs hold only a hashed device key, whether a scan succeeded or failed, how long it took, the reading provider used, and the number of rows read. Logs and error messages contain no photo or logbook text.
• Device integrity checks. We use Apple App Attest and DeviceCheck to prevent abuse of free pages.

Google Gemini, our processor

We use the Google Gemini API, provided by Google LLC, to read the handwriting in your photos. Google processes the image and returns the text to us. We use a paid Gemini API account (a Google Cloud project with active billing). Under Google's terms for paid services:

• Google does not use your photos, our instructions, or the results to improve its products, and processes them under Google's Data Processing Addendum for Products Where Google is a Data Processor.
• Google logs prompts and responses for a limited period, solely to detect and prevent violations of its Prohibited Use Policy and for any required legal or regulatory disclosures. Google states this period is 55 days. Content flagged by Google's safety systems may be reviewed by authorized Google employees.
• This data may be stored transiently or cached in any country where Google or its agents have facilities.

Sources (checked October 19, 2026): Gemini API Additional Terms of Service (effective March 23, 2026), "Paid Services" section; Gemini API abuse monitoring, "How We Handle Data" section. [TODO: re-check both pages before publishing]

We do not use Google's grounding features (Google Search or Maps), which have separate 30-day storage terms, or any other Gemini tools. Each request sends only the photo, our reading instructions and processing settings.

What we keep

Our server does not keep your photos or the extracted text. A photo exists only in server memory while your scan request is processed and is never written to disk. Your digital logbook, your corrections and your page photos are stored only on your iPhone and are not synced to iCloud by the app. If you use iCloud device backup, a normal backup of your iPhone can include the app's data. To let you restore purchased pages, the app stores only your anonymous page-account ID in your private iCloud (iCloud Keychain, the iCloud key-value store, and one private CloudKit record). You can delete your logbook at any time in the app's Settings.

What we don't do

• No selling of your data.
• No advertising or tracking SDKs in the app.
• No sharing with anyone except the processors named here and Apple for purchases.

Website

This website uses [TODO analytics: name the website analytics tool, or say "no analytics". Also confirm the app has no analytics or crash-reporting SDK.] and sets no tracking cookies.

Children

The app is intended for adults 18 and older and is not directed to anyone under 18. On first launch, you must confirm that you are 18 or older before using the app.

Deleting your data

Delete all data in the app's Settings, or delete the app. To remove your page balance record from our server, email us with your request.

Changes

We'll post updates here and change the effective date.