PantryPages · Support · Privacy
PantryPages privacy policy
Updated October 1, 2026. This policy describes prepared version 2.0.1 build 5. Online features depend on the configured service being available. Developer: Nathan Fennel.
Recipes and iCloud
PantryPages saves recipes, notes, ratings, cooking history, images, and preferences on your device. App data can sync through Apple iCloud and CloudKit where enabled. Websites and image hosts are contacted when you import a recipe URL or download its images.
Recipe services and AI
In version 2.0.1, Recipe Processing, shared-result contributions, public links, and Firebase Analytics are separate choices that start off. If you enable Recipe Processing, importing, search, image analysis, and chat can send the relevant URL, recipe content, search terms, images or image URLs, and conversation text to the PantryPages service. AI features use OpenAI. Requests can include a persistent installation identifier for rate limits and usage quotas. Providers also receive normal connection information such as IP addresses. Optional contributions can send corrected recipe content, cover-image URLs, and domain verdicts for shared results.
Analytics and consent records
If you enable Analytics, Firebase records sessions and feature activity, which can include recipe titles, viewing duration, sharing method, favorites, edits, and timestamps. Advertising consent remains denied. Agreement acceptance and document versions are saved on the device and can sync through private iCloud. The current native app does not send agreement records to the separate website endpoint.
Public recipe links
If you enable Public Links and create one, PantryPages uploads a recipe snapshot that anyone with the link can retrieve. It can include the title, ingredients, instructions, source details, and a web image URL. The built-in snapshot excludes private notes, ratings, cooking history, and local imported photos. New links remain available until revoked.
A new link's revocation credential is stored in a nonmigrating Keychain item on the device that created it, outside recipe exports and private iCloud. You can revoke links saved on that device in Data & Privacy > Manage Public Share Links. If the credential cannot be saved, the app tries to revoke the new link immediately and shows a retry path while it remains open if revocation fails. Turning off Public Links, deleting a recipe, or deleting the local library does not revoke links. Earlier links without a saved credential require a support request. Revocation cannot remove copies recipients have saved.
Retention and requests
New public links have no automatic expiry and remain until revoked. Correction-queue and cover-index records have 180-day expiry settings from their latest update; later contributions can renew older records. Domain verdicts and installation-associated votes also have 180-day expiry settings. Approved community search entries remain until moderation removes them. Historical private caches have expiry settings ranging from three to 180 days. DynamoDB removes expired records asynchronously, so these settings are not guaranteed physical-deletion deadlines.
The app provides data inventory, export, and deletion controls for the selected local library. Local deletion does not guarantee removal of public links, analytics events, other libraries, imported image files, backups, exports, provider records, or recipient copies. Contact the developer for access or deletion requests concerning service data. You can also manage iCloud and backups in Apple settings.
Support and changes
If you contact the developer, the information you provide is used to respond to your request. This policy will be updated when the app's practices change.