My Personal Pantry

Privacy Policy

Effective Date: October 5, 2026

Last Updated: October 5, 2026

Version: 1.3

Operator: Bellworth Logistics, LLC

This Privacy Policy explains how Bellworth Logistics, LLC, doing business as My Personal Pantry (“My Personal Pantry,” “we,” “us,” or “our”), collects, uses, stores, discloses, and protects personal information when you use the My Personal Pantry mobile application and related U.S. services (the “Service”).

This policy is intended to describe actual production behavior. We apply data-minimization principles to the Service and do not collect personal information merely because it may be useful in the future. Where a category of information is sensitive, we limit collection and processing to what is strictly necessary to provide or maintain a specific feature requested by the user, except where another use is required or permitted by law.

Where required, users may be asked to affirmatively acknowledge legal documents or make a specific privacy choice. We do not rely solely on continued use of the Service as acceptance of materially changed privacy practices.

1. Information We Collect

The information we collect or process depends on the features you choose to use. We limit collection to information that is adequate, relevant, and reasonably necessary for disclosed purposes.

Account Information

My Personal Pantry uses Firebase Authentication to provide account functionality.

Depending on the sign-in method you choose, account-related information may include:

Supported sign-in methods may include email/password, Google sign-in, and Sign in with Apple.

My Personal Pantry does not intentionally store user passwords in readable form. Authentication credentials are handled through Firebase Authentication and the applicable authentication provider.

We do not include raw authentication tokens, authentication secrets, administrative claims, raw Firebase claims, or provider credentials in user data exports.

Pantry Information

My Personal Pantry may collect or store information that you add to your Pantry, including:

When account synchronization is enabled, supported Pantry records associated with the authenticated account are transmitted to My Personal Pantry's backend infrastructure and stored as part of the synchronized account Pantry. The authenticated account is authoritative for ownership of synchronized Pantry records. We do not silently assign account ownership to installation-local data for which ownership cannot be safely established.

Shopping and Grocery Information

The app may store shopping-list information, including:

For the initial release, Grocery List data, checked-state information, and manually added shopping items are intended to remain local to the installation and are not part of account synchronization unless the app expressly indicates otherwise.

Recipe and Meal Information

Depending on the feature used, the app may process or store information related to:

For the initial release, Meal Plan information, imported recipe information, recipe history, and similar recipe-related user state are intended to remain local to the installation unless ownership can be safely associated with the authenticated account and the app expressly indicates that synchronization has been enabled.

Recipe-search queries may be sent to recipe providers as necessary to return requested results. We do not use recipe-search or recipe-history information to build or influence an advertising profile.

Dietary and App Preferences

If you choose to provide them, the app may store preferences relating to:

For the initial release, these preferences are intended to remain local to the installation unless ownership can be safely associated with the authenticated account and the app expressly indicates otherwise.

Dietary information can, in some circumstances, reveal or permit inferences about health conditions, allergies, religious practices, or other sensitive matters. We do not ask users to provide a medical diagnosis, and My Personal Pantry is not a medical service. Where user-provided dietary information constitutes sensitive or consumer-health information under applicable law, we treat it as sensitive information and limit processing to what is strictly necessary to provide the user-requested feature or as otherwise permitted by law.

My Personal Pantry should not be used as the sole source for allergen or medical dietary decisions.

Barcode and Product Information

When you scan a barcode, the app may process:

Barcode image recognition is intended to occur on-device. Camera imagery is not intentionally uploaded merely to decode a barcode. After decoding, the barcode value or product identifier may be transmitted to a product-data service as needed to identify the item.

Feedback and Support Information

If you contact us or deliberately submit feedback, we may process information you provide, such as your email address, the content of your message or feedback, information needed to investigate the issue, and limited technical context that you choose to provide or that is necessary to resolve the request.

Feedback and support records are retained for no more than 30 days after resolution, unless a longer period is necessary for an active security, fraud, abuse, or legal matter.

Device, Network, Advertising, and Technical Information

My Personal Pantry plans to use Google AdMob for advertising in the initial production release. Ads are intended for signed-in adult users only and are intended to be configured as contextual or non-behavioral advertising, not behavioral advertising based on My Personal Pantry activity.

Subject to the final production configuration, AdMob or related advertising technology may process limited device, network, consent, advertising, and interaction information needed for contextual ad delivery, frequency capping, aggregated reporting, fraud/invalid-traffic prevention, security, and legally required privacy choices. Depending on platform configuration and user privacy choices, this may include IP-derived coarse location, device or advertising identifiers where permitted, ad interaction information, consent or opt-out signals, and related technical information.

My Personal Pantry does not permit Pantry contents, recipe history, Grocery activity, Meal Planner activity, scan history, feedback, account behavior, dietary information, or other personal in-app activity to be used to build or influence a behavioral advertising profile.

Our application, authentication providers, hosting infrastructure, and backend may also receive limited technical or operational information necessary to provide, secure, troubleshoot, and maintain the Service, such as:

We do not intentionally log privacy-sensitive content when it is not necessary for the relevant operational or security purpose.

2. Information We Do Not Intend to Collect or Use

Unless a future feature specifically requires the information, the collection is reviewed and approved, and this Privacy Policy and applicable notices are updated before or when required, My Personal Pantry does not intend to collect or use:

No Production AI Processing at Initial Release

AI functionality is disabled and inaccessible in the initial public release. My Personal Pantry does not send production user data, Pantry information, recipes, Grocery information, Meal Planner information, scans, feedback, or other user content to an AI model provider for production AI processing in the initial release.

Dormant AI-related engineering may exist in source code or development environments, but it is not an active production feature. Any future activation of AI functionality requires a new privacy, provider, data-flow, retention, security, and configuration review; updated disclosures where required; and Product Owner approval before activation.

3. Camera Access

My Personal Pantry may request access to your device's camera when you choose to use barcode-scanning functionality.

Camera access is limited to camera-dependent features such as barcode recognition. Barcode image processing is intended to occur on-device through the application's camera and barcode-recognition components. My Personal Pantry does not intentionally upload camera imagery merely to decode a barcode.

After a barcode is decoded, the resulting barcode value or product identifier may be transmitted to an external product-data service as necessary to identify the product.

The app does not continuously record through the camera and does not use camera access for unrelated purposes.

On platforms that require runtime permission, camera access is requested before the app accesses the camera, and users may change camera permission through device settings.

4. How We Use Information

We use personal information only for disclosed, specific purposes that are reasonably necessary and proportionate to the Service or feature requested by the user, including:

We do not process personal information for a new purpose that is materially incompatible with the purpose disclosed when the information was collected unless we first provide any notice and obtain any consent required by applicable law.

Sensitive information is not collected or processed merely because consent could theoretically be requested. Where applicable law imposes a stricter necessity standard, sensitive information is collected or processed only when strictly necessary to provide or maintain the specific product or feature requested by the user, or when another legal basis expressly permits the processing.

5. Pantry Synchronization and Data Ownership

My Personal Pantry provides account-based synchronization for supported Pantry records.

Synchronized Pantry data is associated with the authenticated account, and the authenticated account is authoritative for ownership of synchronized Pantry records.

For the initial release, information intended to remain installation-local includes, unless the app expressly indicates otherwise:

My Personal Pantry does not invent or infer account ownership for installation-local information when that ownership cannot be safely established.

The app should clearly indicate when a category of information is synchronized. Pantry synchronization must not silently mutate user records in a way that is inconsistent with the user's visible action or the documented synchronization rules.

If synchronization expands to additional data categories, the change must be reviewed before the applicable app release, the Privacy Policy and store disclosures must be updated where required, and affected users must receive any legally required notice or choice before materially different processing begins.

6. Local Data

Some information is stored only on the device or installation on which it was created.

Deleting the application, clearing application storage, factory-resetting the device, losing the device, or otherwise removing local application data may permanently delete information that has not been synchronized.

We cannot restore locally stored information that was never transmitted to or stored by our systems.

Installation-local information that cannot safely be attributed to an authenticated account is not represented as account-owned information in a My Personal Pantry data export.

7. Third-Party Services and Processors

My Personal Pantry relies on third-party services to provide specific parts of the Service. We limit disclosures to what is reasonably necessary for the relevant service and require production configuration to remain consistent with this Privacy Policy.

Current or planned-for-initial-release providers include, as applicable:

These providers may process information under their own privacy terms as well as contracts or platform terms applicable to the service they provide to us.

Firebase is used for Authentication and related Firebase Admin authentication operations. The initial production architecture does not use Firebase Cloud Firestore, Realtime Database, Cloud Storage, Analytics, or Crashlytics. Firebase states that logged Authentication IP addresses may be kept for a few weeks and that other Authentication information is retained until deletion is initiated. After deletion is initiated, Firebase states that Authentication data is removed from live and backup systems within 180 days.

Resend may process recipient email addresses, message content, attachments, and related delivery metadata when used for account, privacy, support, or service communications. Resend states that active-account email and log data is retained for 30 days on Free, Pro, and Scale plans, backups persist for seven days, and remaining customer data is deleted within 90 days after account termination. Enterprise retention may be configurable. A request for early removal of a specific message may be made by contacting Resend. Suppression entries, including entries created for hard bounces or spam complaints, can be viewed and removed through Resend's dashboard or API; we have not verified an automatic expiry period for suppression entries and do not assign them the 30-day email/log period.

Google Sign-In may provide the user's name, email address, and profile picture, but not the user's Google Account password. A user may disconnect the app through Google Account controls. Disconnecting prevents continued provider access but does not retract information already provided to Firebase or Bellworth Logistics, LLC and does not itself delete My Personal Pantry data. We have not verified a fixed provider-side residual-retention period for this Google identity-provider context.

Sign in with Apple is used as an authentication provider where offered. Revoking Apple authorization is separate from deleting a Firebase user. The in-app account-deletion flow obtains fresh Apple authorization and requests token revocation before backend deletion proceeds. Deleting only the Firebase user does not establish that Apple authorization was revoked. The web deletion path provides instructions for manually removing My Personal Pantry through Apple Account controls when an in-app token is unavailable. We have not verified a fixed Apple provider-side residual-retention period for this use case.

My Personal Pantry does not currently plan to use a separate production analytics SDK unless one is deliberately introduced, reviewed, and disclosed before production use.

No production AI provider is used for initial-release user processing because AI functionality is disabled and inaccessible.

8. Recipe and Product Providers

My Personal Pantry may retrieve information from external recipe, food, barcode, manufacturer, or product-data services.

Information sent to these services is limited to what is reasonably necessary to perform the function requested by the user. For example, a product identifier or barcode value may be sent to a product-data provider to identify an item, and a recipe search query may be sent to a recipe provider to return requested recipe results.

Imported third-party recipe content remains subject to applicable third-party rights and restrictions. A My Personal Pantry user-data export does not include full third-party recipe ingredients or instructions merely because a user imported or viewed the recipe.

Third-party services operate under their own privacy practices and policies.

9. Retailer Integrations

Retailer integrations are not part of the initial released synchronization scope.

If a future version introduces functionality that sends shopping, product, account, or other personal information to a retailer, the feature must undergo privacy and security review before activation, and this Privacy Policy, store disclosures, and any required user notices or choices must be updated before or when required.

The app will not transmit shopping-list or product information to a retailer unless the user invokes a feature that requires the transmission and the required disclosures and controls are in place.

10. Advertising, Consent, Analytics, Diagnostics, and Operational Logs

Advertising Model

My Personal Pantry intends to use Google AdMob for advertising in the initial production release.

Advertising is limited to signed-in adult users. The intended advertising model is contextual or non-behavioral. My Personal Pantry does not authorize Pantry contents, recipe history, Grocery activity, Meal Planner activity, scan history, feedback, account behavior, dietary information, or other personal in-app activity to be used to create, enrich, or influence a behavioral advertising profile.

We may use practical AdMob category controls to bias or restrict ad categories toward food, grocery, cooking, kitchen, household food brands, and related categories where technically available. We do not guarantee that only food-related ads will be delivered.

Even non-personalized advertising may involve limited processing for contextual selection, coarse location, frequency capping, aggregated reporting, security, and fraud/invalid-traffic prevention. The exact data processed depends on the production SDK and privacy configuration.

Before requesting ads, My Personal Pantry will implement the privacy and consent behavior required by applicable law, Google AdMob/UMP requirements, and the relevant platform configuration.

Where applicable, users will be given access to a privacy-options mechanism that allows them to review or change advertising privacy choices. When a legally recognized universal opt-out or opt-out preference signal is technically received and applies to processing performed by My Personal Pantry or its advertising configuration, the Service will honor the signal as required by applicable law.

For an iOS version of My Personal Pantry, the app will not engage in tracking as defined by Apple's App Tracking Transparency framework without first obtaining the required permission. If the production configuration does not engage in such tracking, the app will not request tracking permission merely as a precaution.

Analytics

My Personal Pantry does not plan to use a separate production analytics SDK in the initial release. If analytics are later introduced, the provider, purposes, data flows, retention, consent requirements, store disclosures, and this Privacy Policy must be reviewed before production activation.

Operational and Security Logs

The Service may generate limited operational, security, authentication, advertising, and diagnostic information necessary to operate the Service, deliver permitted advertising, troubleshoot problems, protect accounts and infrastructure, investigate abuse or fraud, prevent invalid ad traffic, and maintain reliability.

Security and operational logs are retained for up to 60 days, unless a longer period is reasonably necessary for an active security, fraud, abuse, or legal investigation. Information retained for an active matter is deleted or de-identified when the extended need ends, subject to applicable law.

Final AdMob, UMP, privacy-options, consent, and store-disclosure behavior remains subject to completion and verification through the production advertising and Data Safety work before production advertising is enabled.

11. How We Disclose Information

We disclose personal information only for specific purposes consistent with this Privacy Policy or as otherwise permitted or required by law.

Service Providers and Processors

We may disclose information to companies that process information on our behalf to provide hosting, authentication, email delivery, product lookup, recipe services, advertising operations, security, or other necessary infrastructure.

User-Requested Interactions

We may disclose information when a user deliberately invokes a feature that requires interaction with an external service, such as a recipe or product-data provider.

We may disclose information when reasonably necessary to comply with applicable law, lawful legal process, court orders, or valid governmental requests.

Security and Protection

We may disclose information when reasonably necessary to detect, investigate, prevent, or respond to fraud, abuse, invalid advertising traffic, security threats, or activity that may harm users, My Personal Pantry, or others.

Business Transfers

If Bellworth Logistics, LLC, My Personal Pantry, or relevant assets are involved in a merger, acquisition, reorganization, bankruptcy, financing, or asset transfer, information may be transferred as part of that transaction subject to applicable law and any required notice or protections.

We do not disclose personal information to third parties merely because it may be commercially useful to them.

12. Sale, Sharing, Targeted Advertising, and Sensitive Data

My Personal Pantry does not sell personal information for monetary compensation.

My Personal Pantry does not sell sensitive personal information.

Our intended initial-release advertising model is contextual or non-behavioral. We do not authorize personal My Personal Pantry activity to be used for targeted or cross-context behavioral advertising, and we do not authorize Pantry contents, recipe history, Grocery activity, Meal Planner activity, scan history, feedback, account behavior, or dietary information to be used to build or influence an advertising profile.

Because state privacy laws define terms such as “sale,” “sharing,” and “targeted advertising” differently, the final AdMob configuration must be audited before production advertising is enabled to determine whether any technical advertising disclosure or transfer falls within a regulated definition even though My Personal Pantry does not intend behavioral targeting.

Where a legally regulated sale, sharing, or targeted-advertising activity applies, My Personal Pantry will provide and honor the required opt-out rights, authorized-agent mechanisms, universal opt-out signals, and other controls before or when the activity occurs.

Sensitive personal information is subject to stricter minimization. Where applicable law treats a category as sensitive, My Personal Pantry will not collect, process, or disclose that information beyond what is strictly necessary to provide or maintain the specific user-requested feature unless another use is expressly permitted by law.

13. Data Retention

We retain personal information only for as long as reasonably necessary and proportionate to the purpose for which it was collected, subject to the specific limits below and lawful security, fraud, abuse, dispute, and legal requirements.

Our current retention rules are:

We do not use deletion tombstones, suppression records, or other deletion-control records as a substitute for active user content or for unrelated purposes.

If information must be retained beyond the ordinary limit for an active security, fraud, abuse, dispute, or legal matter, access and use are limited to that purpose, and the information is deleted or de-identified when the extended need ends, subject to law.

14. Account and Data Deletion

My Personal Pantry provides an in-app path for signed-in users to request deletion of their account and associated account data. A public web-based account-deletion mechanism is also provided for external initiation, and users may contact privacy@mypersonalpantry.app for privacy assistance or as a deletion fallback.

The existing delete-account experience is intended to remain straightforward and is not subject to an added grace period beyond the confirmation and authentication safeguards built into the approved production flow.

Account deletion is intended to delete or cause deletion, as applicable, of:

When Sign in with Apple is linked, the in-app deletion flow obtains fresh Apple authorization and requests revocation of the Apple token before backend deletion proceeds. Deleting a Firebase user alone does not establish that Apple authorization was revoked. The external web flow cannot obtain that fresh token and therefore provides instructions for manually removing My Personal Pantry through Apple Account controls. Google disconnection likewise does not retract information already received by Firebase or Bellworth Logistics, LLC and is not a substitute for deleting My Personal Pantry data.

Some limited information may remain temporarily or for a longer period only when reasonably necessary and permitted for a documented legal, security, fraud, abuse, dispute, safety, integrity, or backup-expiration purpose. Ordinary Bellworth-controlled deleted-account operational remnants are limited to a maximum of 30 days where immediate removal is technically impossible. Firebase states that provider-controlled Authentication data is removed from live and backup systems within 180 days after deletion is initiated. Minimized suppression, fence, tombstone, and mutation/idempotency records may remain where necessary to prevent account or data resurrection, replay, duplicate processing, or synchronization corruption; they are not active user-content substitutes.

Temporary account deactivation or freezing is not a substitute for account deletion.

Account deletion may permanently remove synchronized Pantry information and other account-associated data. Installation-local information may also be lost depending on the deletion flow and device state.

15. Data Security

We use reasonable administrative, technical, and organizational safeguards designed to protect the confidentiality, integrity, and availability of personal information appropriate to the nature and volume of information processed.

Safeguards may include:

Privacy-sensitive information should not be placed in logs unless reasonably necessary for the operational or security purpose.

No electronic system, network, transmission method, or storage system can be guaranteed to be completely secure. These safeguards are protections, not guarantees.

Users are responsible for protecting their account credentials and devices.

16. U.S. Privacy Rights and Requests

My Personal Pantry's initial release is limited to the United States. To provide a consistent privacy model, we intend to make the core rights described in this section available to U.S. users generally, even where a particular state law would not independently require every right, subject to identity verification, technical feasibility, lawful exceptions, and protection of other users' rights.

A user may request, as applicable:

We do not discriminate against a user for exercising a privacy right protected by applicable law.

How to Submit a Request

Requests may be submitted through privacy@mypersonalpantry.app or through an in-app or public privacy mechanism when one is provided for the applicable right.

Correction should be self-service where reasonably possible, with privacy email as a fallback. Account deletion is primarily in-app, with privacy email as a fallback and an external web mechanism where required by platform rules.

Verification

We may verify a request using the signed-in account, registered email address, recent authentication, or other information reasonably necessary to establish that the requester is the account holder or an authorized agent. Stronger verification may be required when reasonably necessary for the sensitivity or risk of the request.

We do not require unnecessary government identification merely to process an ordinary privacy request.

Timing and Appeals

We aim to respond to an authenticated privacy-rights request within 45 days of receipt. Where applicable law permits an extension because of complexity or volume, we may extend the response period and will provide notice of the extension and reason as required by law.

If we deny a qualifying request, the response will explain the basis for the denial to the extent required and will provide a method to appeal where required by law. Appeals may be submitted to privacy@mypersonalpantry.app with enough information to identify the original request and the decision being appealed.

Download My Data

A self-service Download My Data feature is implemented and deployed for Android.

For the initial Android implementation, the feature is available to signed-in users through Settings & About and remains available through the restricted Account & Privacy surface during a required legal-reacceptance lock. Signed-out users cannot use the feature.

Self-service export requires backend-authoritative recent authentication within 15 minutes. The export is a versioned ZIP containing UTF-8 JSON data and a README.

The initial export includes, as applicable:

The export does not include:

The Android implementation saves through Android's Storage Access Framework (SAF). Share-sheet export is deferred. If unsynchronized Pantry changes exist, the user receives the approved warning and may return to synchronize or continue with the export as presented.

If an export cannot be safely or completely generated, the app will fail cleanly rather than silently truncating the export and will direct the user to privacy@mypersonalpantry.app for manual assistance.

No iOS Download My Data implementation is claimed by this policy.

17. Age Requirement and Children's Privacy

My Personal Pantry's initial public release is intended only for individuals who are 18 years of age or older.

Users must be at least 18 to create or own a My Personal Pantry account. The initial release does not support child-owned accounts and does not operate a parental-consent program for minors.

We do not knowingly offer the initial account service to children or knowingly collect personal information through a child-owned account. If we learn that an account does not satisfy the age requirement, we may take appropriate steps consistent with law and our Terms of Service.

The Privacy Policy and Terms of Service must use consistent age requirements.

18. United States-Only Initial Release

The initial public release of My Personal Pantry is intended for users in the United States.

The Service is not being offered as an international consumer service at initial release. If My Personal Pantry later expands to users outside the United States, we will conduct a jurisdiction-specific privacy review before that expansion and update this Privacy Policy and related consent, transfer, and user-rights mechanisms as required.

19. Cookies, Device Storage, Identifiers, and Similar Technologies

The mobile application does not rely on traditional browser cookies for core Pantry functionality.

The Service may use local device storage, authentication/session technologies, secure tokens, or similar mechanisms necessary to operate requested features.

Google AdMob and UMP may use or process device identifiers, advertising identifiers where permitted, IP addresses, local storage, consent signals, opt-out signals, and similar technologies for contextual or non-behavioral advertising, frequency capping, aggregated measurement, privacy-choice handling, security, and fraud/invalid-traffic prevention, depending on the final platform and privacy configuration.

For an iOS version of My Personal Pantry, access to the advertising identifier or other activity that constitutes tracking under Apple's rules will not occur without the permission required by the App Tracking Transparency framework.

Where a recognized universal opt-out signal applies to sale or targeted-advertising processing and is technically received by our website, app, or advertising configuration, it will be honored as required by applicable law.

If a public website, account-deletion page, legal-document site, or future feature introduces additional cookies, analytics, tracking, device identifiers, or similar technologies, those technologies must be reviewed and the applicable disclosures and controls updated before or when required.

20. Apple App Store and Google Play Privacy Disclosures

Before each public application release, My Personal Pantry will review the production application and all included SDKs against this Privacy Policy and the privacy disclosures required by the applicable distribution platform.

Google Play

The Google Play Data Safety declaration must accurately reflect the released Android application, including data handled by third-party SDKs. The production review must cover:

Apple App Store

If My Personal Pantry is distributed through the Apple App Store, the Apple App Privacy disclosures and privacy manifests must accurately reflect the released iOS application and applicable third-party SDK behavior. The production review must cover:

A material change to advertising, analytics, tracking, AI, data sharing, synchronization, SDKs, or permissions requires another production privacy-policy and store-disclosure review before the app release containing that change.

21. Advertising Choices and Privacy Controls

My Personal Pantry's intended initial advertising model is contextual or non-behavioral advertising through Google AdMob for signed-in adult users.

Before production advertising is enabled, My Personal Pantry will implement and test Google UMP/privacy messaging and any other control required by applicable U.S. state law, Google Play policy, Apple rules, or the final AdMob configuration.

Where required or applicable, the Service will provide a reasonably accessible privacy-options entry point through which users can review or change supported advertising privacy choices.

My Personal Pantry will not condition ordinary Pantry functionality on consenting to behavioral advertising that the Service does not need to provide that functionality.

If a user declines or opts out of a regulated advertising use and contextual/non-behavioral or restricted advertising remains legally and technically available, the Service may continue to display that permitted form of advertising.

If a legally recognized opt-out preference signal such as Global Privacy Control applies to processing performed by our public web properties or advertising configuration and is technically received, it will be honored as required by applicable law.

The final AdMob/UMP configuration, privacy-options and withdrawal behavior, applicable messaging, platform disclosures, and production data-flow behavior will be completed and reconciled before advertising is enabled for the application's public release.

22. Device Permissions

My Personal Pantry requests only device permissions reasonably necessary for features the user chooses to use.

Expected permissions or platform capabilities include:

Permission requests are made through the applicable platform mechanism on Android and, for an iOS version, on iOS. Denying an optional permission may prevent the related feature from working but should not prevent unrelated features from operating unless technically necessary.

Before the applicable app release, Android manifest permissions, iOS usage-description keys/entitlements for an iOS version, SDK permissions, and actual runtime behavior must be audited and reconciled with this Privacy Policy and store disclosures.

23. Changes to This Privacy Policy

We may update this Privacy Policy when:

When the policy changes, the Last Updated date and policy version will be updated, and we will maintain version/change-history records.

For a material change, affected users will receive additional notice where required. When a material change would prospectively subject previously collected information to materially different collection, processing, or transfer, we will provide any legally required notice and a reasonable opportunity to withdraw consent or otherwise exercise applicable rights before the materially different processing is applied.

We do not rely solely on continued use of the Service as acceptance of materially changed privacy practices when affirmative acknowledgment or consent is required.

Where renewed legal acknowledgment is required, the main application may remain locked until acknowledgment is completed. The restricted Account & Privacy surface is intended to remain available for:

Locally stored Pantry information should remain accessible to the extent allowed by the approved legal-reacceptance design, unless a different restriction is required for security, law, or technical integrity.

24. Policy Version and Acceptance Records

My Personal Pantry maintains or intends to maintain internal records connecting, as applicable:

For published legal versions, My Personal Pantry should retain a stable public reference or immutable copy/hash sufficient to identify the exact document applicable to a release or affirmatively acknowledged by a user.

Privacy Policy, Terms of Service, and Food Safety Disclaimer are maintained as separate legal documents with independently identifiable versions or acceptance records as appropriate.

25. Availability and Accessibility of This Policy

The current Privacy Policy should be reasonably accessible and available:

The policy should be presented in a manner reasonably accessible to users with disabilities. If My Personal Pantry offers a covered product or service in additional languages, the privacy notice should be made available in those languages when required by applicable law.

26. Relationship to Other Legal Documents

This Privacy Policy should be read together with:

The Privacy Policy addresses information collection, use, disclosure, retention, security, and privacy rights.

The Terms of Service establish rules governing use of the Service, including the 18+ account requirement.

The Food Safety Disclaimer addresses food, recipe, allergen, product-information, and related safety limitations.

If these documents address the same factual product behavior, they should be reviewed for consistency before publication.

27. Contact Us

Questions, requests, appeals, or concerns regarding privacy may be directed to:

My Personal Pantry Operated by Bellworth Logistics, LLC

Privacy Contact: privacy@mypersonalpantry.app

Support Contact: support@mypersonalpantry.app

Mailing Address: 524 Old Friar Road, Aiken, South Carolina 29801, United States

Public Website / Privacy Policy URL: https://mypersonalpantry.app/privacy