Privacy Policy

We respect your privacy and are committed to protecting it through our compliance with this privacy policy ("Policy"). This Policy describes the types of information we may collect from you or that you may provide ("Personal Information") on the pantrypages.art website ("Website" or "Service") and any of its related products and services (collectively, "Services"), and our practices for collecting, using, maintaining, protecting, and disclosing that Personal Information. It also describes the choices available to you regarding our use of your Personal Information and how you can access and update it.

This Policy is a legally binding agreement between you ("User", "you" or "your") and PantryPages ("we", "us" or "our"). If you are entering into this Policy on behalf of a business or other legal entity, you represent that you have the authority to bind such entity to this Policy, in which case the terms "User", "you" or "your" shall refer to such entity. If you do not have such authority, or if you do not agree with the terms of this Policy, you must not accept this Policy and may not access and use the Website and Services. By accessing and using the Website and Services, you acknowledge that you have read, understood, and agree to be bound by the terms of this Policy. This Policy does not apply to the practices of companies that we do not own or control, or to individuals that we do not employ or manage.

Version scope: The separate device choices described here are introduced in PantryPages 2.0.1. Older installed versions may send requests under their earlier feature settings without these new controls. Backend changes described below take effect with this website release; they do not erase records already retained by earlier releases.

Automatic collection of information
Collection of personal information
Privacy of children
Use and processing of collected information
Payment processing
Managing information
Disclosure of information
Retention of information
Transfer of information
Region specific notices
How to exercise your rights
Data analytics
Do not sell my personal information
Do Not Track signals
Advertisements
Email marketing
Push notifications
Links to other resources
Information security
Data breach
Changes and amendments
Acceptance of this policy
Third-Party Content Processing
Contacting us

1. Automatic Collection of Information

Website, API, recipe-page and image requests expose the requester’s IP address and ordinary request metadata to the receiving service. Hosting services can retain operational records. Some requests include URLs or search terms in the request address, which can enter access logs. We do not promise that network processing is anonymous or that a request leaves no retained records.

The native app sends a generated installation identifier with some API requests. The service hashes identifiers used for hourly abuse counters; an identifier can still associate requests from the same installation. Optional Firebase analytics is described in section 12. Local recipe history has its own device setting and is separate from analytics.

2. Collection of Personal Information

Saved recipe content includes source URLs, text, ingredients, instructions, notes, ratings, edits, cooking history and image references. Recipe records are stored in the selected local library and can synchronize through the app’s private Apple iCloud container when available. Imported image files are stored separately on the device; synchronizing a file reference does not synchronize its image bytes.

With Recipe Processing enabled, selected URLs, fetched page content, recipe text, photos of recipe cards, chat prompts and context, corrections and conversion requests can be sent to PantryPages and OpenAI. Content you include may contain personal information. Requests also include connection metadata and, for some endpoints, the installation identifier. An optional direct OpenAI configuration sends requests to OpenAI directly.

Separate choices control contributions to shared recipe results, creating public recipe links, and Firebase analytics. Website support forms can submit your name, email, subject and message. The native library does not require a PantryPages account. Apple manages the iCloud account used for private synchronization.

3. Privacy of Children

The current app does not provide a separate child account or parental-consent verification system. Parents and guardians should supervise online processing and sharing choices, and should not include a child’s personal information in recipe photos, prompts or public contributions. Please contact us about personal information concerning a child so we can assess an appropriate access or deletion request.

4. Use and Processing of Collected Information

We act as a data controller and a data processor when handling Personal Information, unless we have entered into a data processing agreement with you in which case you would be the data controller and we would be the data processor.

Our role may also differ depending on the specific situation involving Personal Information. We act in the capacity of a data controller when we ask you to submit your Personal Information that is necessary to ensure your access and use of the Website and Services. In such instances, we are a data controller because we determine the purposes and means of the processing of Personal Information.

We act in the capacity of a data processor in situations when you submit Personal Information through the Website and Services. We do not own, control, or make decisions about the submitted Personal Information, and such Personal Information is processed only in accordance with your instructions. In such instances, the User providing Personal Information acts as a data controller.

In order to make the Website and Services available to you, or to meet a legal obligation, we may need to collect and use certain Personal Information. If you do not provide the information that we request, we may not be able to provide you with the requested products or services. Any of the information we collect from you may be used for the following purposes:

Process recipe imports, chat, regeneration and measurement conversions
Provide selected public links, contributed results and abuse protection
Respond to support inquiries and privacy requests
Understand app use when analytics is enabled
Enforce applicable terms and respond to legal obligations

Processing your Personal Information depends on how you interact with the Website and Services, where you are located in the world and if one of the following applies: (a) you have given your consent for one or more specific purposes; (b) provision of information is necessary for the performance of this Policy with you and/or for any pre-contractual obligations thereof; (c) processing is necessary for compliance with a legal obligation to which you are subject; (d) processing is related to a task that is carried out in the public interest or in the exercise of official authority vested in us; (e) processing is necessary for the purposes of the legitimate interests pursued by us or by a third party. We may also combine or aggregate some of your Personal Information in order to better serve you and to improve and update our Website and Services.

Note that under some legislations we may be allowed to process information until you object to such processing by opting out, without having to rely on consent or any other of the legal bases. In any case, we will be happy to clarify the specific legal basis that applies to the processing, and in particular whether the provision of Personal Information is a statutory or contractual requirement, or a requirement necessary to enter into a contract.

5. Payment Processing

In case of Services requiring payment, you may need to provide your credit card details or other payment account information, which will be used solely for processing payments. We use third-party payment processors ("Payment Processors") to assist us in processing your payment information securely.

Payment Processors adhere to the latest security standards as managed by the PCI Security Standards Council, which is a joint effort of brands like Visa, MasterCard, American Express and Discover. Sensitive and private data exchange happens over a SSL secured communication channel and is encrypted and protected with digital signatures, and the Website and Services are also in compliance with strict vulnerability standards in order to create as secure of an environment as possible for Users. Scans for malware are performed on a regular basis for additional security and protection.

If you choose to make a purchase through the Website and Services, you may be redirected to a third-party website to complete the transaction. In such cases, the third-party website may collect certain information from you, including your credit card number, billing address, and other payment-related information, and may use cookies or other tracking technologies. We have no control over, and are not responsible for, this third-party's collection, use and disclosure of your Personal Information.

6. Managing Information

Data & Privacy in version 2.0.1 exports the open recipe library, selected display preferences and agreement status as JSON. Image references are included; image files and provider-held records are not. Recipe deletion applies to the selected SwiftData library. Private iCloud can propagate record changes when synchronization is available, but the app does not confirm removal from every other device.

Delete Local Library Data also clears selected preferences, local usage history, readable local consent files and downloadable caches. Other library files, imported photos, recovery backups, exports, separate iCloud agreement records and provider records remain. Old encrypted consent files may be unreadable because earlier releases did not preserve their encryption key.

New public links can be revoked in Manage Public Share Links using a revocation credential kept in a nonmigrating Keychain item on the device that created each link, outside recipe exports and private iCloud. If that 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 new sharing or deleting the local library does not revoke existing links. Older links without a saved revocation token require a support request. Revocation cannot remove copies already saved by recipients. There is no native account-deletion page or automatic deletion of historical server caches.

7. Disclosure of Information

Service providers include OpenAI for AI processing, Apple for private iCloud and platform services, Google Firebase for optional analytics, and Vercel/AWS for hosting and service storage. Requested recipe websites and image hosts receive requests directly or through the service. When browsing a source page, its cookies, scripts and embedded resources follow that site’s own practices. These providers have separate retention and privacy terms.

For Facebook previews and imports, the service sends the selected post URL to Meta’s oEmbed service. The service turns the returned preview caption into escaped text before displaying it. Provider scripts, frames, images and other embedded resources are not included in that preview. The separate original-post link opens Facebook when you choose it; browsing that source follows Meta’s own practices. These requests are separate from OpenAI processing and follow Meta’s own practices; we have not verified a special Meta retention agreement. The native preview request requires Recipe Processing to be enabled.

A public recipe link makes its snapshot available to anyone with the link. The snapshot can include recipe text, ingredients, instructions, source details and a web image URL. Private notes, ratings, cooking history and local imported image files are excluded from the built-in snapshot. Optional recipe improvements can submit corrected content, cover URLs and domain verdicts for shared results. Only share content you have permission to share.

We may disclose information to comply with applicable law or legal process, protect legal rights, respond to suspected abuse, or in connection with a business transfer as described by applicable law. This policy does not claim that providers retain information only for the lifetime of an individual request.

8. Retention of Information

The updated service does not create application caches of new private chat, URL/HTML imports, photo extraction, text imports, regeneration or unit/ingredient conversion results. OpenAI requests use store:false where supported; this does not disable OpenAI’s separate abuse-monitoring retention. OpenAI describes default abuse-monitoring retention of up to 30 days, subject to its documented exceptions and account controls. No special zero-retention agreement is claimed here.

Historical private cache records are not erased by this update. Their original expiry settings include up to 180 days for recipe/text/photo/conversion results, 90 days for chat, 7 days for regeneration and 3 days for HTML. DynamoDB expiry is asynchronous, so an expiry time is not a guaranteed physical-deletion deadline. Older automatic search and cover contributions are hidden from current public results and retained separately.

Correction queue records have a 180-day expiry setting from their latest write or review. Cover-index buckets have a 180-day expiry setting from their latest update; later contributions can renew older entries, so an individual contribution may remain longer. Domain verdicts and installation-associated vote records also use 180-day expiry settings. Approved community search entries remain until moderation removes them. New public links remain until revoked. Earlier links without revocation credentials need support removal.

New website support messages and supplied contact details remain until an administrator deletes them; new records omit application-captured IP and user-agent fields, but legacy records may include them. New server agreement records contain supplied agreement fields and a random record ID with a 1,095-day expiry setting; the native app currently does not send to that endpoint. Native agreement records can exist locally and in private iCloud and are not subject to a verified automatic three-year cleanup.

Hourly rate counters use hashed identifiers and a one-hour expiry. Remember Recipe on the website stores a link associated with a hash of the observed source IP for 30 minutes; previous raw-IP handoff records retain their earlier expiry. The native app asks before looking up a remembered link and previews it before import. A shared network address does not identify a particular person. Provider/hosting operational records, Apple backups, exports and recipient copies have separate retention periods.

9. Transfer of Information

Depending on your location, data transfers may involve transferring and storing your information in a country other than your own. However, this will not include countries outside the European Union and European Economic Area. If any such transfer takes place, you can find out more by checking the relevant sections of this Policy or inquire with us using the information provided in the contact section.

10. Region Specific Notices

If you are a resident of the European Economic Area (EEA), you have certain data protection rights and we aim to take reasonable steps to allow you to correct, amend, delete, or limit the use of your Personal Information. If you wish to be informed what Personal Information we hold about you and if you want it to be removed from our systems, please contact us. In certain circumstances, you have the following data protection rights:

You have the right to withdraw consent where we relied on your consent to process your Personal Information.
You have the right to object to our processing of your Personal Information.
You have the right to learn if your Personal Information is being processed by us, obtain disclosure regarding certain aspects of the processing and obtain a copy of your Personal Information undergoing processing.
You have the right to verify the accuracy of your information and ask for it to be updated or corrected.
You have the right, under certain circumstances, to restrict the processing of your Personal Information, which means that we will store your data but will not process it further.
You have the right, under certain circumstances, to obtain the erasure of your Personal Information from us.
You have the right to receive your Personal Information in a structured, commonly used and machine-readable format and, if technically feasible, to have it transmitted to another controller without any hindrance from us, provided that such transmission does not adversely affect the rights and freedoms of others.

If you are a resident of California, you have the right to request that we disclose certain information to you about our collection and use of your Personal Information over the past 12 months. If we sold or disclosed your Personal Information for a business purpose, we will disclose to you the categories of Personal Information categories sold and disclosed. You have the right to request that we delete any of your Personal Information that we collected from you and retained, subject to certain exceptions. To exercise any of these rights, please contact us. We will not discriminate against you for exercising any of your CCPA rights.

11. How to Exercise Your Rights

Any requests to exercise your rights can be directed to us through the contact details provided in this document. Please note that we may ask you to verify your identity before responding to such requests. Your request must provide sufficient information that allows us to verify that you are the person you are claiming to be or that you are the authorized representative of such person. If we receive your request from an authorized representative, we may request evidence that you have provided such an authorized representative with power of attorney or that the authorized representative otherwise has valid written authority to submit requests on your behalf.

You must include sufficient details to allow us to properly understand the request and respond to it. We cannot respond to your request or provide you with Personal Information unless we first verify your identity or authority to make such a request and confirm that the Personal Information relates to you.

12. Data Analytics

Starting in 2.0.1, Firebase is initialized only after Share Usage Analytics is enabled on that device. Analytics can receive app-instance identifiers, device/OS information, SDK diagnostic user-agent metadata, approximate location derived from network information, interactions, timestamps and session duration. Custom events can include recipe titles for views, favorites and sharing. Therefore analytics is not described as excluding all recipe content.

Advertising storage, advertising user data, advertising personalization and IDFV collection are disabled in this release. Turning analytics off disables new collection and resets local Firebase analytics data; it does not delete records already received by Google. The Google Analytics property is configured to retain event data for two months and user data for fourteen months, with user retention reset on new activity. These settings do not guarantee deletion of all provider records. See Google’s data collection information.

13. Do Not Sell My Personal Information

You have the right to choose not to have your Personal Information sold or disclosed by contacting us. Upon receiving and verifying your request, we will cease the sale and disclosure of your Personal Information. Be aware, however, that opting out of data transfers to our third parties might affect our ability to provide certain Services you have signed up for. We reserve the right to reject opt-out requests in certain situations as permitted by the CCPA, such as when the sale of Personal Information is required for us to fulfill legal or contractual duties.

14. Do Not Track Signals

Some browsers incorporate a Do Not Track feature that signals to websites you visit that you do not want to have your online activity tracked. Tracking is not the same as using or collecting information in connection with a website. For these purposes, tracking refers to collecting personally identifiable information from users who use or visit a website or online service as they move across different websites over time. How browsers communicate the Do Not Track signal is not yet uniform. As a result, the Website and Services are not yet set up to interpret or respond to Do Not Track signals communicated by your browser. Even so, as described in more detail throughout this Policy, we limit our use and collection of your Personal Information.

15. Advertisements

The current native release contains no advertising display flow. Firebase advertising consent remains denied, independently of the analytics choice. Websites you open within the app may display their own advertisements and use their own cookies; their policies apply to those requests.

16. Email Marketing

Website support can retain contact details you provide so the developer can respond. This release does not implement a newsletter subscription flow in the app or website. Use the contact link below for questions about communications you have received.

17. Push Notifications

Apple’s private CloudKit synchronization can use platform notifications to deliver data changes. This release does not implement a developer marketing-push subscription or a third-party marketing-push provider. Local timers and system notification permissions are separate from online recipe processing.

18. Links to Other Resources

The Website and Services contain links to other resources that are not owned or controlled by us. Please be aware that we are not responsible for the privacy practices of such other resources or third parties. We encourage you to be aware when you leave the Website and Services and to read the privacy statements of each and every resource that may collect Personal Information.

19. Information Security

We secure information you provide on computer servers in a controlled, secure environment, protected from unauthorized access, use, or disclosure. We maintain reasonable administrative, technical, and physical safeguards in an effort to protect against unauthorized access, use, modification, and disclosure of Personal Information in our control and custody. However, no data transmission over the Internet or wireless network can be guaranteed.

Therefore, while we strive to protect your Personal Information, you acknowledge that (a) there are security and privacy limitations of the Internet which are beyond our control; (b) the security, integrity, and privacy of any and all information and data exchanged between you and the Website and Services cannot be guaranteed; and (c) any such information and data may be viewed or tampered with in transit by a third party, despite best efforts. As the security of Personal Information depends in part on the security of the device you use to communicate with us and the security you use to protect your credentials, please take appropriate measures to protect this information.

20. Data Breach

In the event we become aware that the security of the Website and Services has been compromised or Users' Personal Information has been disclosed to unrelated third parties as a result of external activity, including, but not limited to, security attacks or fraud, we reserve the right to take reasonably appropriate measures, including, but not limited to, investigation and reporting, as well as notification to and cooperation with law enforcement authorities.

In the event of a data breach, we will make reasonable efforts to notify affected individuals if we believe that there is a reasonable risk of harm to the User as a result of the breach or if notice is otherwise required by law. When we do, we will send you an email. In jurisdictions where required, we may also report the breach to relevant authorities in accordance with applicable data protection regulations.

21. Changes and Amendments

We reserve the right to modify this Policy or its terms related to the Website and Services at any time at our discretion. When we do, we will revise the updated date at the bottom of this page. We may also provide notice to you in other ways at our discretion, such as through the contact information you have provided.

An updated version of this Policy will be effective immediately upon the posting of the revised Policy unless otherwise specified. Your continued use of the Website and Services after the effective date of the revised Policy (or such other act specified at that time) will constitute your consent to those changes. However, we will not, without your consent, use your Personal Information in a manner materially different than what was stated at the time your Personal Information was collected.

22. Acceptance of This Policy

This policy describes data handling; using or installing the app is not a substitute for the separate online choices in version 2.0.1. Recipe Processing, Recipe Improvements, Public Share Links and Usage Analytics start off on each device. You can turn them off in Data & Privacy. Revocation stops new covered requests, and pending recipe-processing results are rejected after revocation; it cannot recall a request already received or erase provider-held records. Saved recipes remain available.

23. Data Accuracy and Reliability Disclaimer

IMPORTANT DISCLAIMER: PantryPages makes no representations or warranties regarding the accuracy, completeness, reliability, or suitability of any processed recipe data. All recipe content is processed from third-party sources and transformed using AI technology, which may introduce errors, omissions, or inaccuracies.

You acknowledge and agree that:

Recipe data may contain errors in ingredients, measurements, cooking times, or instructions
Nutritional information, if provided, is estimated and may be inaccurate
Allergen information may be incomplete or incorrect
You are solely responsible for verifying all recipe information before use
You use all processed recipe data at your own risk
PantryPages shall not be liable for any consequences of using inaccurate recipe data

HEALTH AND SAFETY WARNING: Always verify recipe ingredients and instructions, especially regarding allergens, cooking temperatures, and food safety. Consult qualified professionals for dietary or health concerns.

24. Third-Party Content Processing

PantryPages processes recipe content from third-party websites that you choose to share with us. This section explains how we handle this content and your rights regarding it.

Voluntary Content Sharing and Processing

BY PROVIDING A RECIPE URL, YOU VOLUNTARILY CHOOSE TO SHARE CONTENT WITH PANTRYPAGES. When you provide a recipe URL, our app downloads and processes the content from that website to create a standardized, organized recipe format. With Recipe Processing enabled, imports and related retries, reprocessing, cover lookups and conversion requests can contact the service; not every retry has a separate prompt.

This voluntary content processing includes:

Extracting recipe text, ingredients, and instructions at your request
Downloading and displaying recipe images you choose to process
Standardizing formatting and measurements (which may introduce errors)
Organizing content for better readability (results not guaranteed)

Choice: Version 2.0.1 requires the separate Recipe Processing choice before covered content uploads. Providing a URL or accepting the EULA does not itself enable that choice. Older versions may use earlier feature settings.

Data Sources and Ownership

PantryPages does not own, claim ownership of, or assert any rights over the recipe content you choose to process. All recipe content remains the property of its original creators and publishers. Content comes from third-party recipe websites that you voluntarily choose to share with us. Sources can include URLs you add, shared or community recipes you import, related pages fetched during extraction and images loaded for those recipes. A source link or attribution does not grant permission to republish protected material.

You acknowledge that:

You are voluntarily sharing third-party content with PantryPages
You are responsible for ensuring you have the right to access and process such content
PantryPages makes no claims of ownership over any recipe content
All intellectual property rights remain with the original content creators

AI Processing and Accuracy Limitations

AI processing is optional and requires the Recipe Processing choice in version 2.0.1. To attempt to standardize and improve recipe formatting, we send recipe content that you voluntarily provide to OpenAI's servers for AI-powered processing. This processing attempts to:

Extract structured recipe data (accuracy not guaranteed)
Standardize ingredient measurements and units (may introduce errors)
Organize instructions in a readable format (completeness not guaranteed)
Improve recipe presentation (results may vary)

CRITICAL DISCLAIMER: AI processing is inherently imperfect and may produce inaccurate, incomplete, or misleading results. OpenAI processes this data according to their privacy policy. Recipe content, selected photos, prompts and context can contain personal information; avoid sending details that are unnecessary for your request.

YOU ACKNOWLEDGE THAT: You are voluntarily sharing content for AI processing, understanding that such processing may alter, misinterpret, or corrupt the original information. You use AI-processed results entirely at your own risk.

Image Handling

Recipe and image hosts receive network requests when web images are downloaded or pages are opened. Downloaded images can be cached locally. Selected recipe-card photos are sent for online extraction when enabled. Public links and cover contributions can include web image URLs; they exclude local imported photo files. Local imported photos remain separate from recipe-record deletion.

Data Retention and Storage

The recipe library uses local storage and private iCloud when available. Online processing, public links, explicit contributions and historical caches have the separate storage and retention scopes described in section 8. Device backups, recovery copies, exports and separately stored images can remain after deleting recipe records or uninstalling the app.

DATA LOSS DISCLAIMER: PantryPages makes no guarantees regarding data preservation, backup, or recovery. You are solely responsible for backing up any important recipe data. Data may be lost due to device issues, software updates, or other factors beyond our control.

User Control

You can delete recipe records, export the open library, clear selected local data, revoke saved public links and change online choices. These actions have the specific scopes described in section 6; they are not a promise of erasure from every device, backup or provider.

25. Additional Disclaimers and Limitations

SERVICE AVAILABILITY: PantryPages makes no guarantees regarding service availability, uptime, or continuous operation. The service may be interrupted, suspended, or terminated at any time without notice.

THIRD-PARTY DEPENDENCIES: Our service relies on third-party websites, AI services, and internet connectivity. We have no control over these external factors and disclaim all responsibility for their availability or performance.

CONTENT ACCURACY: PantryPages does not verify, validate, or guarantee the accuracy of any recipe content, nutritional information, allergen data, or cooking instructions. Users must independently verify all information.

VOLUNTARY USE: Your use of PantryPages is entirely voluntary. Online processing and public sharing have separate choices. Review results and verify source rights before using or sharing them.

The app-specific policy is also available at nathanfennel.com/pantrypages/privacy.html.

26. Contacting Us

If you have any questions, concerns, or complaints regarding this Policy, we encourage you to contact us using the details below:

Contact Nathan Fennel

We will attempt to resolve complaints and disputes and make every reasonable effort to honor your wish to exercise your rights as quickly as possible and in any event, within the timescales provided by applicable data protection laws.

If you believe your concerns have not been adequately addressed, you may escalate the matter to the appropriate data protection authority in your region, in accordance with applicable privacy laws.

This document was last updated on September 28, 2026