← App Privacy

Food Log

Food Log helps you record food and nutrition information while keeping your diary under your control. Online food searches are optional and use a separate service, CalorieAPI.

Last updated: 7 November 2026

Information stored by Food Log

Food Log allows you to record food and nutrition information. Depending on the features you use, this may include food names, meals, dates and times, quantities consumed, calories, fat and other nutrient values, saved food definitions, favourites and other food information you choose to enter.

The app also maintains a local catalogue of previously saved food information, which may include nutrition information obtained from an online lookup. Your diary entries and saved food definitions are separate: deleting a saved food definition does not automatically delete historical diary entries.

Storage on your device

Food Log stores diary entries and saved food definitions in its app data on your device. The existing food catalogue and certain preferences are stored locally in the app's preferences. The optional CalorieAPI key you enter is stored in the app's local preferences.

Food Log does not operate a developer-controlled server that receives your food diary or saved food library.

iCloud and CloudKit synchronisation

When iCloud is available for Food Log, diary entries and saved food definitions may synchronise between your devices through Apple's CloudKit service, using the private database associated with your Apple Account. The app does not offer public sharing of these records or sharing them with other Food Log users.

CloudKit synchronisation is managed by Apple and may take time to complete. Your local legacy food catalogue and certain app preferences are not part of Food Log's CloudKit-backed diary and saved-food synchronisation. Apple's privacy terms apply to iCloud processing.

Optional CalorieAPI food searches

Food Log can work without CalorieAPI. If you choose to search for a food online, the app sends the food search text you entered and the CalorieAPI API key you supplied to CalorieAPI using an encrypted HTTPS connection. The request also includes ordinary technical parameters required to return search results.

Food Log does not intentionally include your diary entries, meal history, quantities consumed, diary identifiers, Apple Account identifier or backup files in these search requests.

Search results are processed in the app. When you choose to save a result, its food name, nutrition information and available source identifier may be retained locally in your saved foods or existing food catalogue. SavedFood records may also synchronise through your private iCloud database.

Information handled by CalorieAPI

As with other online services, CalorieAPI can receive technical connection information, including your IP address. Its published privacy policy states that it may record food searches, API usage, request timestamps, authentication-key usage patterns, errors and approximate country or region derived from IP addresses. Because requests include an API key, search and usage information may be associated with a CalorieAPI account.

CalorieAPI states that request logs may be retained for up to 12 months and that information may be used to operate, secure, analyse and improve its service. These are CalorieAPI's stated practices and may change independently of Food Log.

For details about its collection, retention and privacy rights, see CalorieAPI's privacy policy. You can use Food Log without performing online food searches.

Backups and export

Food Log provides a user-initiated backup export. Depending on the version of the app, an exported backup may contain your diary records, saved foods and local food catalogue. You choose where to save or share the backup file. Food Log does not automatically transmit backup files to the developer or to CalorieAPI.

Files you export are outside the app's control once saved or shared. Please protect them appropriately, particularly if they contain personal diary information.

Deleting information

You can delete diary entries and saved food definitions using the app's available controls. Deletions of synchronised records are submitted through CloudKit, but may not immediately appear on every device. Deleting a saved food definition does not erase diary entries already created from it.

Removing the app can remove its locally stored information, but records previously synchronised to iCloud and files you have exported may remain until separately removed. Data previously transmitted to CalorieAPI is subject to that service's own retention and deletion policies.

Analytics, advertising and tracking

Food Log does not include third-party advertising, advertising tracking or a third-party analytics SDK. The developer does not receive a copy of your food diary through a separate analytics or advertising service.

However, when you use optional online food search, CalorieAPI may collect search history, account-associated API-key usage information and approximate location inferred from your IP address for service operation and analytics. Food Log's App Store privacy disclosures reflect this optional third-party collection. Food Log does not request your device's GPS location for these searches.

Contact

If you have questions about Food Log or this policy, contact info@andygrant.com.

For information about CalorieAPI's handling of information it receives, please refer to CalorieAPI's privacy policy.