App Privacy Label
This page documents the data-collection answers Pantry submits in App Store Connect → App Privacy. Use it as the source of truth when preparing the App Store listing — it should match what the “Privacy Nutrition Label” displays on the product page.
For full background, see the Privacy Policy.
Summary
Data the developer collects: Data Not Collected.
Pantry collects nothing. All user content lives in:
- Apple’s CloudKit (the user’s own private database under their Apple ID), OR
- The user’s device local storage.
Two outbound requests exist, both described under “Outbound requests” below:
- Open Food Facts on barcode scan: sends only the barcode digits and the request’s IP address, no user identifier.
- The legacy Pantry Manager import: the user signs in on a MJLyco web page in a secure browser window and the app receives only that user’s own legacy items. Entirely opt-in and skippable.
App Privacy Form Answers
Does your app collect any data?
No. Answer Data Not Collected.
Why: Apple defines collect as transmitting data off the device and storing it in a readable form for longer than it takes to service the request. The optional legacy import happens on MJLyco’s own web page in a secure browser window: the app never handles the email or password, and our server uses them only during the sign-in request and never stores them. Failed-attempt records (account ID and time) exist only to block password guessing and are deleted within minutes, and one-time codes are stored as a hash and deleted once they expire. The app receives only the user’s own legacy items.
Scope: users who never used Pantry Manager, or who never open the import screen, transmit nothing; the app makes no request to this server otherwise. Everything else in the app stays on the device, and in the user’s own iCloud if they sign in (iCloud is optional).
If reviewers ask about CloudKit: Apple defines collect as transmitting data off the device in a way that lets the developer or its third-party partners access it for longer than needed to service the request. Data in the user’s private CloudKit database isn’t accessible to us, so it is not developer-collected data. (Same reasoning as iCloud Drive, Photos, Notes, etc. — Apple is the data custodian, not the app developer.) That reasoning covers the pantry itself.
Data the user stores (for reference; not part of the label)
For transparency with reviewers, this is what the app stores on the user’s behalf:
| Category | What | Where | Linked to identity? | Used for tracking? |
|---|---|---|---|---|
| User Content — Photos | Item thumbnails the user takes or imports | Local SQLite + user’s iCloud (if signed in) | No (private CloudKit) | No |
| User Content — Other | Item titles, quantities, expiration dates, notes, household names, tag names, UPC barcodes | Local SQLite + user’s iCloud (if signed in) | No (private CloudKit) | No |
| Other — Age check | Whether an age check is required here, the App version and age rating last used, and whether the App is currently unavailable (so widgets and Siri and Shortcuts actions stay locked). The age range itself is used once and not kept | Device UserDefaults (the unavailable setting is in the app group shared with widgets) |
No | No |
| User Content — Other | Saved meals (recipe text the user saved) | Local SQLite + user’s iCloud (if signed in) | No (private CloudKit) | No |
| User Content — Other | Receipt matches (a receipt product’s name in lowercase words, and which item it was added as). Receipt images and text are not stored | Local SQLite + user’s iCloud (if signed in) | No (private CloudKit) | No |
| User Content — Other | Shopping-list copy on the paired Apple Watch (titles, quantities, units, expiration dates), sent iPhone ↔ watch over WatchConnectivity | Watch app-group file | No | No |
| Diagnostics | None | n/a | n/a | n/a |
| Usage Data | None | n/a | n/a | n/a |
| Identifiers | None collected. The app keeps the app-scoped CloudKit user record ID on the device only, to detect iCloud account switches | Device UserDefaults |
n/a | No |
None of the above leaves Apple’s ecosystem (the user’s devices + iCloud) under our control.
Outbound requests
Besides Apple’s own services (CloudKit, StoreKit, APNs, WatchConnectivity), the app makes two kinds of outbound request: the Open Food Facts barcode lookup (and its product-image download from Open Food Facts’ image host, over HTTPS) and the optional legacy-import call.
Open Food Facts
A UPC barcode lookup against the Open Food Facts public API when the user scans a barcode that isn’t already in their local cache.
| Field | Value |
|---|---|
| Third party | Open Food Facts (non-profit, France) |
| Endpoint | https://world.openfoodfacts.org/api/v2/product/{barcode}.json |
| Data sent | Barcode digits, request IP, app User-Agent string |
| User identifier sent | None |
| Authentication | None (anonymous, no API key) |
| Frequency | One request per user-initiated scan (cached on success) |
| Third-party retention | See their privacy policy |
A matching product’s image may also be downloaded (capped at 10 MB, normally re-encoded to a 512x512 HEIC thumbnail). If it becomes an item’s photo it syncs to the user’s own iCloud and remains subject to Open Food Facts’ CC-BY-SA licensing — see the Attribution page.
This is disclosed in the in-app Privacy Policy and the Open Food Facts attribution page (Settings → Open Food Facts Attribution in the app).
The Open Food Facts request carries a product barcode, which identifies a product rather than a person and is not one of App Store Connect’s user-data types, plus the IP address every HTTPS request carries. We never receive either, and neither is linked to the user’s identity or used for tracking.
Pantry Manager legacy import (MJLyco-operated)
| Field | Value |
|---|---|
| Operator | MJLyco LLC (us) |
| Endpoints | https://api.mjlyco.com/prod300/importSignIn (web page), https://api.mjlyco.com/prod300/importExchange |
| Data sent by the app | A one-time code and PKCE verifier, request IP. The user’s email and password are entered on the web page and never reach the app |
| Trigger | Explicit: user opens Settings > Import, taps Sign In to Pantry Manager |
| Direction | Returns the account’s items/tags/photo URLs |
| Frequency | On demand (the import is idempotent and safe to repeat) |
This is disclosed in Privacy Policy §5.3.
Support email
Settings › Contact Support opens the user’s own Mail app with a pre-filled draft. The app doesn’t send anything; the user writes and sends the message from Mail, so the app doesn’t collect it. Privacy Policy §6 describes what we receive.
Legacy import sign-in
The user types their Pantry Manager email and password on our sign-in page, opened in a secure browser window; the app never receives them. Our server uses the email only to find the account during the request and doesn’t store it. If a sign-in fails, the server keeps the account ID and time to limit repeated guesses, and the server deletes those records once they’re more than 15 minutes old, checking every five minutes (Privacy Policy §5.3). None of this is used for tracking or advertising.
Crash data shared by Apple
Apple’s App Privacy details state: “You are not responsible for disclosing data collected by Apple.” They also state: “If you collect data about your app from Apple frameworks or services, you should indicate what data you collect and how you use it.” The page does not address crash reports that Apple shares through a user’s opt-in “Share With App Developers” setting.
Answer: Data Not Collected. Crash reports and usage data that Apple shares when a user turns on “Share With App Developers” are collected by Apple, under the user’s choice in iOS Settings. We view them only in Xcode Organizer and App Store Connect and don’t export or keep them in our own systems, so this falls under “data collected by Apple”. If we ever export or store them elsewhere, declare Diagnostics › Crash Data (not linked, not used for tracking, App Functionality).
Pantry Plus purchases (StoreKit)
Pantry Plus is sold as in-app purchases. Apple processes the payment, and the app checks entitlement on the device through StoreKit. The app makes no request of its own to us or to any server we control for purchases, and we receive no payment details, purchase history, or transaction data. Because Apple handles purchases as the payment processor and nothing reaches us, the answer stays “Data Not Collected”. Per Apple’s app privacy details, payment information entered outside the app and never accessible to the developer is not collected, and data collected by Apple’s own services is Apple’s responsibility.
Tracking
NSPrivacyTracking in PrivacyInfo.xcprivacy is false. The app does not:
- Link user data with third-party data for advertising or measurement.
- Share device identifiers with data brokers.
- Track users across other apps or websites owned by other companies.
SDK declarations (for App Store Connect → SDK list)
Pantry resolves these open-source packages (those it uses are linked statically into the app or extension binaries). None of them collect telemetry on the developer’s behalf:
| SDK / Package | Purpose | Privacy manifest |
|---|---|---|
combine-schedulers |
Scheduler utilities used by the architecture libraries | No data collection |
grdb.swift |
SQLite engine | No data collection |
sqlite-data |
Local SQLite and CloudKit sync | No data collection |
swift-case-paths |
Enum key paths | No data collection |
swift-clocks |
Testable clocks | No data collection |
swift-collections |
Data structures | No data collection |
swift-composable-architecture |
App architecture | No data collection |
swift-concurrency-extras |
Concurrency helpers | No data collection |
swift-custom-dump |
Value dumping and diffing; linked into the app through the Composable Architecture | No data collection |
swift-dependencies |
Dependency injection | No data collection |
swift-identified-collections |
Identified collections | No data collection |
swift-issue-reporting |
Issue reporting | No data collection |
swift-navigation |
State-driven navigation | No data collection |
swift-perception |
Observation back-port | No data collection |
swift-sharing |
Shared state and persistence | No data collection |
swift-snapshot-testing |
Snapshot testing (resolved with the package) | No data collection |
swift-structured-queries |
Type-safe SQL | No data collection |
swift-syntax |
Macro support | No data collection |
When the answers might change
The answer is “Data Not Collected”. It would change if we ever add:
- A general backend Pantry operates for its own data (analytics, error reporting, or an account system beyond the legacy migration)
- A third-party SDK that collects data (e.g., crash reporting, advertising, A/B testing)
- An API call that sends user content — item titles, photos, notes — to a service we control. The legacy import pulls content from our legacy server; it does not push the user’s new pantry to it.
- A third-party AI backend for meal suggestions or receipt scanning. Today they use Apple Intelligence through Apple’s Foundation Models framework; Apple processes requests (on device) and we never receive the prompt or response.
- An in-app support form, or support data stored outside email.
- Server-side receipt validation, or purchase analytics, that sends transaction or purchase data to a server we control (Purchase History would then need to be declared)
- Sending the age range, or anything from the age check or a parent’s approval, off the device.
None of those exist today.