Your kitchen records
PantryWeave stores personal recipes, recipe favourites, meal plans, pantry quantities and expiry dates, shopping lists and plan templates in its app-private database on your device. Ingredient exclusions and privacy choices are separate local preferences. WorkManager schedules cooking timers. The app does not provide a kitchen cloud account or cloud sharing.
PantryWeave disables Android cloud backup and device transfer of app data. An exported kitchen backup is readable JSON, not encrypted by PantryWeave. You choose its destination; that destination or recipient can retain a copy. The backup includes recipes, plans, pantry, shopping and templates, but not purchases, review access or privacy choices. Restoring a validated backup replaces kitchen records. Local records are not recoverable from us after device loss without your own backup.
Ingredient exclusions are text filters. They do not establish allergy safety, detect synonyms, traces or cross-contact, or provide medical or nutritional advice.
Optional usage and diagnostic reporting
PantryWeave starts its usage Analytics and local crash-capture choices off in every process. Saved positive preferences do not reopen them automatically; you choose again for the current session. Firebase auto-init is removed and collection defaults are off in the manifest. A failed privacy change closes the app’s session gates and asks you to retry; SDK work already started may continue until restart.
If enabled, our Analytics events describe onboarding, meal planning, shopping-list creation, viewing Pro and restoration. A shopping event includes a bounded item count. Our event code does not attach entered recipe or pantry text, an identity-based user ID or advertising ID. Firebase may add automatic events, installation/app identifiers and device/app/operating-system information. Advertising storage and personalization are disabled.
Local crash capture and report sending are separate. An initialized Crashlytics handler may keep capturing locally until process death even after the switch is off. Opening report controls or requesting an Analytics reset can initialize SDK processing. Reports can contain stack traces and technical app/device state, including earlier sessions. The app cannot preview their number or contents. Manage pending crash reports offers an explicit Send, Delete or Not now choice for the available batch. Send and Delete request SDK actions without a completion receipt; a queued send cannot be recalled. Neither switch removes provider-held data. Turning enabled Analytics off requests an on-device reset. Settings → Reset Analytics identifier also requests a reset when Analytics is already off and can initialize Firebase processing. Neither action is a remote erasure confirmation.
SDK initialization and previously saved SDK settings can affect diagnostic processing. Privacy switches do not retract requests already started or confirm that provider-held data was removed.
Store purchases
When a RevenueCat key is configured, PantryWeave initializes its billing SDK at app startup independently of optional telemetry choices. It uses an anonymous app-user identifier, purchase/restoration information and entitlement status with RevenueCat and Google Play. Entitlement refresh reads cached status and requests current status; network failures can leave the last verified decision. Store availability depends on the Google Play catalog and account. An unavailable offer or failed check is not a completed purchase or restoration. We do not collect payment-card numbers in the app.
The app-scoped billing contract is pantryweave_pro with pantryweave_default. A local reviewer receipt is separate from a purchase and is not proof of ownership. Deleting kitchen data does not delete a store transaction or provider customer history.
Retention and deletion
Kitchen records remain until removed in the app or app-private storage is cleared. Settings → Delete local kitchen data resets the kitchen database and restores starter recipes. It attempts timer cancellation and local review-access removal, with retry messages if cleanup fails. It leaves preferences, optional-reporting controls, SDK caches/pending reports and store/provider records separate. Exported files must be removed at their destinations. See deletion choices.
The separately linked PantryWeave Analytics property 556247108 was recorded on 1 October 2026 with event retention 2 months, user retention 14 months and activity reset on. These settings concern identifier-associated event/user data; most aggregate reports are unaffected. New activity refreshes the user-identifier period and expired data is removed monthly. They are not proof of traffic or erasure of all Analytics records. See Google’s retention explanation.
Firebase says Crashlytics retains traces and associated identifiers for 90 days before removal from live and backup systems starts. That is a provider rule, not a verified completion date for this app’s reports. See Firebase privacy.
To request review or deletion of RevenueCat-held billing records, contact support with the app’s purchase support ID. Requests require matching the real billing identifier and checking shared-project aliases without affecting unrelated apps. No fixed app-customer RevenueCat retention period is promised. RevenueCat customer deletion does not cancel or erase Google Play transactions. See RevenueCat customer deletion.
Providers and security
Configured billing uses Google Play and RevenueCat; optional usage/diagnostics use Google/Firebase. Provider processing can occur outside your country. See the linked provider policies for their processing and transfer information. The app-private database is not a promise of an encrypted kitchen vault. Keep exported JSON private; no security measure protects against every compromised device or copied file.
This static site’s source contains no scripts, forms, tracking pixels, remote fonts or cookies. Its hosting provider can process network/security metadata. External links use their own providers’ policies: Google privacy, Firebase privacy, RevenueCat privacy.
Contact, rights and changes
Black and Blue publishes PantryWeave. Contact developer@blackandblue.co.in for support, privacy and deletion requests. Include PantryWeave and the minimum information needed; use the purchase support ID from Settings for billing-record requests if available. Do not send recipe backups, passwords, payment-card data, reviewer codes or credentials. Sending a request does not by itself confirm that provider-held records have been removed.
Depending on your location, access, correction, deletion, restriction and withdrawal rights may apply. A proportionate identity check and provider/legal limits may affect a request; no unverified response deadline is promised here. PantryWeave is intended for people aged 13 and older and is not directed to children under 13. The app does not implement an age-verification or parental-consent flow. Contact us about suspected child information. This policy is effective 2 October 2026; material changes will be reflected here.