Legal

Privacy Policy

This policy explains exactly what BBQ Cook Log does — and does not — do with your information. The short version: the app keeps everything on your device and sends nothing to us.

Effective date: June 5, 2026 · Last updated: June 5, 2026

In plain English: BBQ Cook Log is an offline-first app. It has no user accounts, contacts no servers we operate, runs no analytics or advertising, and does not collect, transmit, sell, or share your personal information. Everything you create lives on your device until you choose to share or delete it.

01 Overview

This Privacy Policy describes how the BBQ Cook Log mobile application (the “App,” “we,” “us,” or “our”) handles information when you use it on iOS or Android. It applies to the App distributed under the package/bundle identifier net.jimlavin.bbqcooklog.

By using the App, you agree to the practices described here. If you do not agree, please do not use the App.

02 Who we are

BBQ Cook Log is developed and published by Jim Lavin (the “Developer”). For any privacy questions or requests, you can reach the Developer at bbqcooktimeline@gmail.com. This contact is also listed in Section 13.

03 Information we do not collect

The App is designed to function entirely offline. We do not collect, receive, store on our systems, or have access to any of the following:

  • Personal identifiers such as your name, email address, phone number, or account credentials — the App has no sign-up or login.
  • Location data (the App does not request or use device location).
  • Contacts, calendar, microphone recordings, or call/SMS data.
  • Advertising identifiers, cookies, or cross-app tracking data.
  • Analytics, usage telemetry, crash reporting collected by us, or behavioral profiles.
  • Any cook plans, recipes, photos, scores, or other content you create in the App.

We operate no servers that receive your data, and the App contains no analytics or advertising software development kits (SDKs) that would transmit your data to us or to third parties.

04 Information stored on your device

To do its job, the App creates and stores content locally on your device only, inside the App's private storage. This may include:

  • Templates you create: timelines, recipes, products, and checklists.
  • Cook logs you assemble, including event timing, turn-in times, and notes.
  • Competition results you enter: weights, temperatures, judge scores, placements, and fuel logs.
  • Photos you capture or attach to a meat (stored as local files/references on your device).
  • App settings, such as your role (captain or team member), team name, and theme preference.

This information is created and controlled by you, remains on your device, and is never transmitted to the Developer. We cannot read, access, or recover it.

05 Device permissions we request

The App may ask for the following operating-system permissions. Each is used solely for the on-device feature described, and only after you take an action that needs it. You can grant or deny each permission, and change it later in your device settings.

Notifications Used to deliver local timeline reminders and exact-time cook alarms (with sound and vibration). Notifications are scheduled and fired locally on your device. No notification content is sent to or through us.
Camera Used only when you choose to take a photo of a meat or turn-in box. Captured photos are stored on your device and attached to your cook log. The App does not stream, upload, or transmit camera content.
Photos / Media library Used only when you choose to attach an existing photo from your library to a meat. The selected image is referenced/stored on your device. The App does not scan or upload your library.

06 How information is shared

The App does not automatically share your information with anyone. Sharing happens only when you deliberately initiate it:

  • Exporting a cook log. You can export a cook log as a .cooklog file and send it using your device's standard share sheet (for example AirDrop, Messages, or email). When you do this, your operating system and the app or service you pick handle the file. The transfer goes directly from you to your chosen recipient; it does not pass through any server operated by the Developer.
  • Importing a cook log. If someone sends you a .cooklog file, importing it stores that plan locally on your device, just like content you created yourself.

We do not sell, rent, or trade your information, and we have no information to disclose to advertisers, data brokers, or other third parties.

07 Third-party services

The App does not integrate third-party analytics, advertising, or data-collection services. The only third parties inevitably involved are the platforms that distribute and run the App:

  • Apple App Store and Google Play may collect standard installation, purchase, and diagnostic information (such as crash logs you opt to share with the platform) under their own privacy policies. This data is handled by Apple or Google, not by the Developer. See Apple's Privacy Policy and Google's Privacy Policy.
  • If you choose to share a .cooklog file through a third-party app or service, that service's own privacy policy governs how it handles the file.

08 Data retention & deletion

Because your information is stored only on your device, you control its lifetime:

  • Delete individual items (recipes, cook logs, photos, fuel entries, etc.) from within the App at any time.
  • Uninstalling the App removes the App's local data and all content stored within it from your device.

We do not retain copies of your content because we never receive it. There is no account to close and no server-side data for us to delete. If you have questions about deleting data, contact us at bbqcooktimeline@gmail.com.

09 Security

Your content is stored in the App's private, sandboxed storage provided by your operating system and is protected by your device's own security (such as your passcode, biometrics, and disk encryption). Because nothing is transmitted to us, there is no server-side database of your information that could be breached on our side. No method of electronic storage is ever 100% secure, so we encourage you to protect your device with a passcode and keep your operating system up to date.

10 Children's privacy

The App is intended for a general, adult audience of barbecue cooks and is not directed to children. The App does not knowingly collect any personal information from anyone, including children under 13 (or the equivalent minimum age in your jurisdiction). Because the App collects no personal information at all, no such information about children is gathered.

11 International users

The App processes information locally on your device wherever you are located. Since we do not collect or transfer your personal data to our own systems, your information is not transferred internationally by us. Your use of the App is subject to the laws of your jurisdiction.

12 Changes to this policy

We may update this Privacy Policy from time to time — for example, if the App adds a new feature. When we do, we will revise the “Last updated” date above and post the new version at this URL. Material changes will be reflected here, and we encourage you to review this page periodically. Your continued use of the App after an update constitutes acceptance of the revised policy.

13 Contact us

If you have any questions, concerns, or requests regarding this Privacy Policy or your information, contact:

Jim Lavin — Developer, BBQ Cook Log
Email: bbqcooktimeline@gmail.com
App identifier: net.jimlavin.bbqcooklog

← Back to BBQ Cook Log