PantryWeave

Delete or keep your data

Choose what to remove and understand which copies remain separate.

developer@blackandblue.co.in

Publisher: Black and Blue · com.blackandblue.pantryweave
Policy host: pantryweave.blackandblue.co.in

Remove local kitchen records

To keep a copy, first export a kitchen backup in Settings and confirm it exists. The JSON file is readable and must be kept private. Settings → Delete local kitchen data asks for confirmation, removes personal recipes, favourites, meal plans, pantry, shopping and templates, then restores starter recipes. It attempts to cancel the timer and remove local reviewer access. Read the result and retry any reported cleanup failure.

That kitchen reset leaves privacy/preferences, SDK caches and pending reports, purchases and provider-held records separate. Android Clear storage or uninstall removes app-private storage; it does not remove exported files, copies held by other destinations or remote records. PantryWeave has no kitchen sign-in account to delete.

Optional reporting records

If Analytics is enabled, turning it off requests an on-device reset. To request a reset when it is already off, use Settings → Reset Analytics identifier. This can initialize Firebase processing and does not erase provider-held records. To manage an available local crash batch, open Manage pending crash reports and choose Delete rather than Send. The app requests SDK deletion without a completion receipt. Earlier uploads and already queued sends cannot be recalled by those controls; local capture can continue after initialization until restart.

Request provider-record review

Email developer@blackandblue.co.in with PantryWeave and the minimum request details. If billing is configured, Copy purchase support ID in Settings provides the anonymous app-user identifier. Do not send a backup, reviewer code, password or payment-card data. Provider records must be matched to this app and checked for shared-project aliases before any authorized deletion. A deletion request is not a confirmation that all provider-held copies have been removed; no fixed provider purge period or completion deadline is promised. Google Play transaction/legal records remain separate from RevenueCat customer deletion.

See retention details before assuming all copies were removed. Contact support if you need help identifying which records and copies remain separate.