Prepared for version 1.0.0. Last updated: 27 September 2026.
Application ID: com.freshshelf.pantry
Responsible publisher: Dev with Rehman
Privacy contact: alimehdisiddiqui99@gmail.com
Scope and local operation
This Privacy Policy explains how FreshShelf handles information when you use the Android application to manage food inventory, expiry dates, shopping lists and food-use history. The app operates on your device. It does not send your app records, usage activity or identifiers to the developer, and it has no developer-operated account, server or synchronisation service. The installed app does not request Android's INTERNET permission. Information you choose to hand to another app or file provider is described separately below.
Information processed on your device
Food names, quantities and units, storage locations and categories, saved dates and opened dates, notes, selected food photos, shopping entries and their status, stock adjustments and use/disposal history are stored locally. The app also stores appearance, onboarding, reminder and haptic preferences, local record identifiers and the scheduling information needed to deliver reminders. These local record identifiers organise your records; they are not advertising identifiers.
These records are used to provide the functions you request, show your own history and summaries, preserve preferences and schedule local operations. They are stored in the app's private Android storage. The developer cannot remotely view, retrieve or delete them. The app does not transmit analytics events, advertising identifiers or crash reports to the developer or an embedded advertising, analytics or remote crash-reporting provider.
Photos, audio and device access
FreshShelf accesses only images you explicitly choose through the Android photo picker. It does not request access to your entire photo library or use your camera, microphone, contacts or location. Selected photos are copied into app-private storage, oriented and resized, then saved as new JPEG images. The normal photo-import process does not copy the original EXIF metadata. Images restored from a valid backup are handled as backup files and may retain metadata present in that backup. The visible content of a selected photo may itself contain personal information. A photo provider you select may retrieve an image from its own cloud service under its own terms.
Optional reminders are calculated locally from your food dates and shopping information. The content may be displayed in Android notifications or on your lock screen, depending on your system settings. Reminders are optional, respect the applicable Android permission and notification-channel settings, and can be disabled. Android may defer scheduled work. Background-work components may use Android wake, boot, foreground-service and connectivity-state permissions to support local reminder scheduling; connectivity-state access does not grant Internet transport. Haptic feedback uses local Android controls and the app's saved preference.
Backups, restore and information you choose to share
An explicitly requested backup includes food and shopping records, preferences, retained history, retained deleted food records and referenced photos in a ZIP file. A restore reads the backup you select, validates it and shows a preview before you confirm replacement of your local records. Shopping-list sharing sends the previewed names and quantities of items still to buy to the receiving app you select through Android; it does not include pantry contents or shopping notes.
Backup files are created through Android's document picker, and you select the destination or source. A selected document or photo provider may be local storage or a cloud-backed service. A receiving app or provider can store, transmit or otherwise process the information you deliberately pass to it under its own privacy terms. FreshShelf does not control those independent services or recall copies already exported or shared. The app does not automatically upload a backup to a developer server.
Exported backups are not password-protected or encrypted by the app. Integrity checks help identify damaged or invalid backup content; they do not make a backup confidential. Store exported files in a location you trust and restrict access to them if they contain private notes, names, photos or other sensitive content. The app is configured to exclude its private data from Android automatic cloud backup and device transfer. Operating-system and device-manufacturer behaviour is outside the app's direct control, and manual exports remain separate from that configuration.
Retention and deletion
Deleting an individual food entry can retain the entry, related history and photo for undo and history, including in a full backup. Marking food as used or discarded preserves history. Individual shopping deletion removes that shopping row, although associated internal history may remain. For a complete reset of food, shopping, history and private photos, use Settings, Data & backup, Delete all data and confirm. This also cancels reminders; theme and onboarding preferences are retained. Restoring a backup replaces the current subject records and photos after confirmation.
Local records remain until you remove them, replace them through an explicitly confirmed restore, or clear the app's storage. Android's Clear storage function and uninstalling the app remove its private local data under Android's storage rules. Local deletion is not a guarantee of forensic secure erasure. Exported backups, shared shopping text and files held by another provider remain at their selected destinations and must be deleted separately. The developer holds no copy of your in-app records and cannot recover them if you lose your device or delete them without a usable backup.
Security and independent services
The app uses Android's private application storage and scoped access to files you select. It does not provide a separate app-level database encryption or password-lock feature. Device security depends in part on your Android security updates, screen lock and control of exported files. No software can promise protection against every form of unauthorised device access.
The app includes open-source Android and Kotlin libraries needed for its interface, storage and local functions. Their presence does not mean your records are sent to their authors. Technology credits and the bundled open-source licence are available in About. Android, Google Play and external apps or providers you choose may process information independently under their own terms; this policy describes FreshShelf, not those independent services. Images generated during development are supplied as static app resources and do not create a runtime connection to their creators.
Your control and enquiries
You can review and edit records in the app, manage permissions through Android, turn optional reminders off, export a copy where supported and use the deletion controls described above. Because the developer does not receive your local records, a request sent to the developer cannot remotely retrieve or erase data stored solely on your device. For a privacy question, use the privacy contact shown at the start of this policy. Do not attach a full backup, receipt photo or private note unless it is necessary to explain your question. Any handling of correspondence outside the app must be described by the publisher's actual support practices before this policy is published.
Changes to this policy
This policy should be updated if the app's handling of information changes. The date at the top identifies the current text. Any future feature that introduces new access, collection or sharing must be reflected in this policy and, where applicable, explained in the app before it is used.