The short version

What data Cooklore collects

Cooklore does not upload your record database to a Trueframe account. Exports, sharing, diagnostics and store transactions have the separate data flows described in this policy.

Crash diagnostics (default ON, opt out in Settings → Diagnostics → Crash diagnostics). To find and fix crashes and slow screens, Cooklore sends diagnostic reports. Two services receive them:

• Trueframe’s crash-reporting endpoint receives crash reports: app/build, platform/OS, error kind, timestamp, error text and a code stack trace. The report schema has no device, installation or user identifier, and the receiving service discards the request IP at ingestion.
• Sentry (EU region) receives errors and crashes, app-start and screen timings (named by screen, never by what is on it), session health, technical log lines and counters, the layout of the app’s widgets at a crash, the app version and build, device and operating-system information, and sampled performance profiles on Apple devices. Screenshots and session replay are turned off, and Sentry’s default personal-information fields are turned off. Sentry may attach a random installation ID, used to count how many installs a problem affects. It is made fresh for each installation and is not linked to you or your account.

Neither report is an upload of your record database. Error text and stack traces can incidentally include context such as a file path. Like any internet request, each report carries your device’s IP address. Turning the switch off stops new reports: crash reports, errors, timings and log lines are no longer sent. If you turn it off while the app is open, Sentry may still receive short notes that a session started or ended, until the app is fully closed and opened again. A crash or freeze in that same session may also still be reported. This is technical diagnostics, not advertising or behavioural tracking.

Everything you enter (recipes, ingredients, steps, photos, meal plans, shopping lists, pantry inventory, made-it history, ratings, notes, reminders, and any other record) is stored only on your device in a local SQLite database.

What data Cooklore stores on your device

Cooklore creates a local database in your device's app storage area:

• Android: /data/data/com.trueframe.cooklore/files/cooklore.db
• iOS / iPadOS: Documents/cooklore.db inside the app container
• macOS: ~/Library/Containers/com.trueframe.cooklore/Data/Documents/cooklore.db
• Windows: %APPDATA%\com.trueframe.cooklore\cooklore.db

This database contains the recipes, photos, plans, lists, and other information you enter. It is not encrypted at rest by default. The local OS sandboxes the app's storage from other apps.

What permissions Cooklore requests

• Photos / Camera (optional): needed to attach recipe photos, scan cookbook pages, or scan barcodes for the pantry inventory. Photos stay on your device.
• Microphone (optional): used for live voice commands during cooking. This path uses the operating system’s speech recognizer and does not force local-only recognition; processing can depend on the platform service and settings. Imported-video transcription is a separate path described below.
• Notifications (optional): used for the app’s locally scheduled reminders. Cooklore does not use a server push-notification service.
• Storage / Documents (optional, only when you use Export & Backup or Import): needed to read importer files and write export / backup files to a folder you choose.

Cooklore does not request:

• Location.
• Contacts.
• Phone state.
• Any tracking-related permission.

Video and recipe imports

Cooklore imports video files you select or share to it. It does not download a TikTok/Reel/Short from a pasted video URL. On supported Apple systems, imported speech is processed by Apple’s on-device speech engine; the local whisper path serves the supported fallback platforms after a model download you approve. A deterministic parser turns the transcript into a review draft. There is no language-model structuring step or BYO cloud-AI setting in the current app.

A recipe-webpage URL import requests the page from its host; that host receives normal request metadata. A Pinterest link loads the pin and then the recipe page it points to. A TikTok link sends one request, with the post’s address, to TikTok’s public embed service; if no recipe comes back, the app asks you to paste the caption. Instagram, Facebook and YouTube links are not fetched: the app asks you to paste the caption instead. Downloading a speech model also contacts its download host. Review the draft before saving. Your recipe database is not uploaded to a Trueframe recipe service.

Sharing and network requests

Exports and the system share sheet send only the file you choose to the destination you choose. Recipe-link requests (web pages, Pinterest pins and TikTok’s embed service), approved model downloads, platform speech services, opt-out crash and performance diagnostics, external links, purchase and restore processing by the store and RevenueCat and, on Android, Google ML Kit's technical information are the app’s network uses. The diagnostic services are described above. On Android, when you scan a cookbook page, Google ML Kit reads the text on your device; the photo and its text are not uploaded. Google ML Kit sends Google technical information about how the text reader performs (such as the app's name and version, an installation identifier and timings), never the photo or its text, as described in Google's ML Kit terms.

Cooklore Pro is a one-time purchase. On iPhone, iPad, Mac and Android the purchase is made through the App Store or Google Play and processed by RevenueCat, our purchase-processing provider. RevenueCat receives the purchase and store transaction details, a customer identifier the app generates (not your name or email), and app and platform information so it can confirm and restore your purchase. Like any internet request, each one carries your device’s IP address. It does not receive your recipes or any other record you keep in Cooklore. The app also keeps a local copy of your purchase state so Pro works offline. Payment itself is handled by Apple or Google under their own policies; Trueframe Digital never sees or stores your payment details.

Who else handles this data, and for how long

Sentry and RevenueCat work for us as service providers. Their terms let them use this data to run and improve their service for us, and require them to keep it secure, so it has the same protection this policy describes. Sentry may also use parts of it that cannot identify anyone for its own business, such as statistics and new products. Trueframe’s crash-reporting service runs on Cloudflare, which stores its reports for us. When a fatal crash arrives, the service also posts a short alert to our developer’s Discord channel: the app and its version, the platform and operating-system version, the kind of error and its first line.

Sentry keeps timings, logs, counters and profiles for 30 days and everything else, such as errors and crash layouts, for 90 days, then deletes them; its backups are deleted 90 days after they are made. Reports in Trueframe’s own crash service, and its Discord alerts, carry no identifier and stay until we delete them. RevenueCat keeps your purchase record while we use its service.

Backups you make

Cooklore makes a backup only when you ask for one, in Settings → Backup & Restore. A backup is the file you save or send; Cooklore keeps no hidden copy on your device. Backups are not encrypted by Cooklore. A copy you save to iCloud Drive is handled by Apple under your account. We have no access to it. You can restore a backup any time in the same place.

Backups and exports

You can also export your data manually at any time via Settings → Backup & Restore:

• .cooklore file: your whole library with its photos and attachments, in one file you can restore.
• CSV export: spreadsheet-friendly copy of your recipes.
• Family cookbook PDF: styled multi-recipe cookbook for printing, sharing, or archival.

From a recipe's Share menu you can also send that one recipe as text or as a .cooklore file.

These exports go only where you save or send them. Cooklore does not upload exports anywhere.

Use the app’s record-deletion controls to remove records. Separately saved backups remain until you delete them. Desktop application data may survive uninstall.

Children's privacy

Cooklore is not directed at children under 13. It does not knowingly collect personal data from anyone, and contains no advertising, social, or messaging features.

Changes to this policy

If this policy changes, the updated version will ship with a new app version. The changelog will indicate the change. The "Last updated" date at the top of this file always reflects the current version.

Contact

For questions: [email protected].

Source-of-truth contact: https://trueframedigital.app.

---

Cooklore stores what you enter. It is not a nutrition or medical service. Always consult a licensed professional for medical decisions about your diet.